interior design jobs johannesburg

[HonoluluKn]

Кабринский Эдуард - Puppet devops - Kabrinskiy Eduard


<h1>Puppet devops</h1>
<p>[youtube]</p>
Puppet devops <a href="http://remmont.com">News update</a> Puppet devops
<h1>Puppet Cheat Sheet</h1>
<p>This DevOps tutorial will now provide you with the Puppet cheat sheet. In this Puppet cheat sheet module, you can learn end-to-end Puppet in a compact way. Also, while going through this module, you can take note of some important ..Read More Puppet terminology.</p>
<h2>Puppet User Handbook</h2>
<p>Are you a programmer looking for a powerful tool to manage your servers? If yes, then you must take Puppet into consideration.</p>
<p>This Puppet cheat sheet is designed for those who have started their journey with Puppet and need a handy reference to implement what they have learned in real-time.</p>
<p style="clear: both"><img src="https://intellipaat.com/mediaFiles/2019/03/Puppet-Cheat-Sheet.jpg" /></p>
<p>In the early days of software development, everything was done manually such as inspecting, operating, and delivering applications. Later on, different phases of SDLC started getting automated, and it is there Puppet came into the picture.</p>
<p>Puppet is an open-source configuration framework. It is a tool that gives an automatic way of inspecting, delivering, and operating applications faster. It helps in discovering content in cloud, containers, and on-premises systems and what software runs on them.</p>
<p><strong><em>Go through these Top DevOps Interview Questions and Answers and crack any DevOps interview!</em></strong></p>
<h3>Watch this Puppet Tutorial for Beginners:</h3>
<p><iframe src="https://www.youtube.com/embed/kHD4KQKKP5Y?rel=0"></iframe></p>
<p style="clear: both"><img src="https://intellipaat.com/blog/wp-content/uploads/2020/09/Youtube-subscribe-CTA.jpg" /></p>
<h2>What is Puppet?</h2>
<p>It is an open-source system management tool used for automating configuration management, a detailed recording and updating of information that describes the enterprise software and hardware.</p>
<p>This configuration framework is useful:</p>
<p><ul>
<li>When we have a lot of machines needed to be configured in a similar way</li>
<li>When we have an infrastructure that requires dynamic scaling up/down with pre-determined config</li>
<li>To have control over all the config machines so that a centralized change gets propagated</li>
</ul>
</p>
<p style="clear: both"><img src="https://intellipaat.com/blog/wp-content/uploads/2020/09/Certification-in-Cloud-Devops-IITG-1.jpg" /></p>
<h2>Puppet Architecture</h2>
<p>Further, in this tutorial, we will look into the architecture of Puppet. The below image shows the components and workflow of Puppet:</p>
<p style="clear: both"><img src="https://intellipaat.com/mediaFiles/2019/03/Puppet-Architecture.png" /></p>
<p><ul>
<li><strong>Node</strong>: It consists of a block of Puppet code.</li>
<li><strong>Puppet Master</strong>: It is the master node that controls the flow and has the authority.</li>
<li><strong>Catalog</strong>: It is a document describing the state of resources on a node, which is managed by Puppet.</li>
<li><strong>Report</strong>: It is a record of the actions and infrastructure applied by a catalog during a Puppet run</li>
</ul>
</p>
<h3>Files</h3>
<p>In Puppet, all programs, written in any programming language, are stored in a file that is used to manage directories and symlinks.</p>
<p><strong><em>Go through the Best DevOps Course in New York to learn DevOps from scratch!</em></strong></p>
<p><strong>Attributes:</strong></p>
<p><ul>
<li>Ensure if the file exists or not and what it should be. Allowed: <ul>
<li>File</li>
<li>Directory</li>
<li>Link</li>
<li>Present</li>
<li>Absent</li>
</ul>
</li>
<li>Normal files: <ul>
<li>Source: The source of a file</li>
<li>Content: The desired content as a string</li>
</ul>
</li>
<li>Directories: <ul>
<li>Source: The source of a file</li>
<li>Recurse: Whether to recursively manage the files in the directory</li>
<li>Purge: Whether the unmanaged files in the directory should be deleted</li>
</ul>
</li>
<li>Symlinks: <ul>
<li>Target: The symlink target</li>
</ul>
</li>
<li>Others: backup, checksum, force, ignore, links, and replace</li>
</ul>
</p>
<h3>Package</h3>
<p>It is used to manage software packages.</p>
<p><strong>Attributes:</strong></p>
<p><ul>
<li><ul>
<li><ul>
<li>Name: The name of the package</li>
<li>Ensure if it should be installed or not</li>
<li>Present</li>
<li>Latest</li>
<li>Absent</li>
<li>Purged</li>
<li>Source: Where to obtain the package</li>
<li>Provider: Which packaging system to use</li>
</ul>
</li>
</ul>
</li>
</ul>
</p>
<p><strong><em>Want more? Learn about DevOps in-depth from this</em> <em>DevOps Training in Sydney</em><em>!</em></strong></p>
<h3>Service</h3>
<p>It is used to perform routine maintenance.</p>
<p><strong>Attributes:</strong></p>
<p><ul>
<li><ul>
<li>Name: The name of the service to run</li>
<li>Ensure the status whether it is running or stopped</li>
<li>Enable: If it should start on boot</li>
<li>Hasrestart: Whether to use the init script restart command instead of stop+start</li>
<li>Hasstatus: Whether to use the init script status command</li>
</ul>
</li>
</ul>
</p>
<p style="clear: both"><img src="https://intellipaat.com/blog/wp-content/uploads/2020/09/Become-a-Cloud-and-DevOps-Architect-IBM-MS-1.jpg" /></p>
<p><strong><em>Master DevOps by taking up this online DevOps Training in London!</em></strong></p>
<h3>Classes and Modules</h3>
<p><strong>Classes:</strong></p>
<p>Defining classes makes the class available by its name but not by the code inside. Declaring a class evaluates the code inside too.</p>
<p><strong>Modules:</strong></p>
<p>By stowing the implementation of a feature in a module, our main manifest can become much smaller, more readable, and policy-focused.</p>
<p><strong>Module structure:</strong></p>
<p><ul>
<li><ul>
<li>A module is a directory.</li>
<li>Module and directory names have to be the same.</li>
<li>A module contains the manifest directory (contains .pp files).</li>
<li>It should contain the init.pp file.</li>
</ul>
</li>
</ul>
</p>
<p><em><strong>Don’t you dream of becoming a DevOps expert? Sign up for the DevOps Course in Toronto today!</strong></em></p>
<h3>Puppet CLI</h3>
<p>Puppet CLI consists of a single Puppet command with multiple sub-commands.</p>
<p><ul>
<li>Bootstrap client: Tasks that bootstrap or install Puppet on the agent node</li>
</ul>
<ul>
<li>Displaying facts:</li>
</ul>
<ul>
<li>Injecting facts:</li>
</ul>
<ul>
<li>Finding out effective classes on a node:</li>
</ul>
<ul>
<li>Finding out the file modification date:</li>
</ul>
<ul>
<li>Disabling and enabling Puppet agent:</li>
</ul>
<ul>
<li>Managing certificates:</li>
</ul>
<ul>
<li>Managing nodes:</li>
</ul>
<ul>
<li>Managing modules:</li>
</ul>
</p>
<h3>Watch this interesting video on Puppet Installation:</h3>
<p><iframe src="https://www.youtube.com/embed/7cPc3yGcrcY?rel=0"></iframe></p>
<p style="clear: both"><img src="https://intellipaat.com/blog/wp-content/uploads/2020/09/Youtube-subscribe-CTA.jpg" /></p>
<ul>
<li>Inspecting resources and types:</li>
</ul>
<ul>
<li>Debugging and deploying:</li>
</ul>
<ul>
<li>Other commands:</li>
</ul>
<table ><tbody><tr><td style="text-align: center"><strong>Function</strong></td><td style="text-align: center"><strong>Command</strong></td></tr><tr><td>To check the version</td><td>Puppet –version</td></tr><tr><td>File content manifest – site.pp</td><td>file < ‘/tmp/dafile’:<br />content => “datext\n”, <br />></td></tr><tr><td>File content manifest – multiple nodes</td><td>node ‘danodename’ <<br />file < ‘/tmp/dafile’:<br />content => “datext\n”, <br />><br />></td></tr><tr><td>To remove packages</td><td>package < ‘apache2.0-common’:<br />ensure => absent, <br />></td></tr><tr><td>To update packages</td><td>package < ‘puppet’:<br />ensure => latest, <br />></td></tr><tr><td>To start service at the boot time</td><td>service < ‘nginx’:<br />ensure => running, <br />enable => true, #false disables auto-startup <br />></td></tr><tr><td>To set to a specific version</td><td>package < ‘nginx’:<br />ensure => ‘1.1.18-1ubuntu0.1’, <br />></td></tr></tbody></table>
<p><em><strong>Interested in getting an industry-recognized certification in DevOps? Enroll in Intellipaat’s DevOps Course in Bangalore!</strong></em></p>
<h2>Advantages of Puppet</h2>
<ul>
<li>Infrastructure as code(IAC): Puppet enables us to define IAC by easily coding a few scripts. It consists of version control, peer review, automated testing, and delivery.</li>
<li>Reduced downtime</li>
<li>Faster deployment time</li>
<li>Easy automation of repetitive tasks</li>
<li>Supports a lot of platforms like Windows, Debian, BSD, etc.</li>
</ul>
<p><em><strong>DevOps Engineers are among the highest paid professionals in the technology domain? Join DevOps Training in Hyderabad now!</strong></em></p>
<p>In this Puppet cheat sheet, we covered almost all Puppet topics that you should know to start working with it. If you want more, Intellipaat has resources that would satisfy your quest.</p>
<p><em><strong>If you are planning to learn DevOps in-depth, then enroll in Intellipaat’s DevOps Certification Training today!</strong></em></p>
<p>We at Intellipaat will never leave you disappointed as our approach is not just theoretical; the course we offer will provide you step-by-step guidance and support to implement what you have learned about DevOps.</p>
<p>In the course, all the important DevOps concepts are included such as Docker, Chef, Git/GitHub, Ansible, Jenkins, Kubernetes, Selenium, Nagios, etc., along with Puppet. Sign up with us today and follow the right learning path toward DevOps!</p>
<h2>Puppet devops</h2>

<h3>Puppet devops</h3>
<p>[youtube]</p>
Puppet devops <a href="http://remmont.com">Current news in english</a> Puppet devops
<h4>Puppet devops</h4>
Get the ultimate Puppet Cheat Sheet to learn Puppet, its commands, architecture, modules, etc. Download the Puppet Commands Cheat Sheet PDF now.
<h5>Puppet devops</h5>
Puppet devops <a href="http://remmont.com">Puppet devops</a> Puppet devops
SOURCE: <h6>Puppet devops</h6> <a href="https://dev-ops.engineer/">Puppet devops</a> Puppet devops
#tags#[replace: -,-Puppet devops] Puppet devops#tags#
Эдуард Кабринский
news today

[HonoluluKn]

Кабринский Эдуард - Deployment groups azure devops - Кабринский Эдуард


<h1>Deployment groups azure devops</h1>
<p>[youtube]</p>
Deployment groups azure devops <a href="http://remmont.com">Today's big news</a> Deployment groups azure devops
<h1>Getting started with Azure DevOps -create a deployment group</h1>
<p style="clear: both"><img src="https://skdevops.files.wordpress.com/2020/02/buildagent-image1.png" /></p>
<p style="clear: both"> <strong>What is a deployment group?</strong> <br />In simple terms, a deployment group is a collection of machines (e.g. servers) that form a logical unit and can be expected to display identical traits -such as to form an environment. E.g. say you have a product that gets deployed to the following environments -Dev, Test, Stage, and Production. Then these 4 environments can be referred to as 4 deployment groups. Machines in a deployment group are mutually exclusive -one machine can only be in one deployment group. <br /> <br />In a usual setup (think tool agnostic), you’d have a continuous-integration (CI) build definition that creates a package ready to be deployed. A release script or orchestrator can be configured such as to deploy the artifacts of the CI build to an environment (aka list of machines). You can create an orchestration technique via a deployment script that pushes the packages to (say e.g.) 2 machines in the Dev environment. Now, say our product has undergone some change and instead of 2, we now have to deploy our package to 10 machines. The deployment script then has to be updated to accommodate the change. <br />Now, say you have not 1 but 40 release definitions to manage for various other components of the product. The deployment processes to deploy to 10 machines (belonging to the Dev environment) has to be updated in 40 release definitions. And then the same change would be required for the remaining environments -Test, Stage, and Production. Let me throw in some more variables -Imagine an environment that is dynamic where machines get added and removed to align with the changing needs of the products. In such a situation it becomes cumbersome and stressful to be able to allocate and manage resources without error. In Azure DevOps, we circumvent this issue via the usage of Deployment groups. <br />Typically a release definition executes a set of instructions (aka jobs) on the following -agent, agentless, or a deployment group; where an agent is a machine that triggers the job/s and a deployment group is where the jobs are executed. For now, let’s keep agentless out of the scope of our discussion. <br /> <strong>How do you create a deployment group?</strong> <br />Inside your Azure DevOps project -> Pipelines -> Deployment groups <br /><img style="float: left; margin: 0 10px 5px 0;" src="https://skdevops.files.wordpress.com/2019/12/ad-gettingstarted-deploymentgroup-image1.png" /> <br />Give it a name that makes sense and will be easy to identify (considering you will have multiple deployment groups). I like to name them based on the purpose they will be fulfilling.. in this case acting as an environment, so I name the deployment group with the environment they will be serving. Hence names like “Dev”, “Test”, “Stage” and “Prod”. <br />Click on Add a deployment group and name it as “Dev” and create. <br />On successful creation, you get to choose what kind of machines will be part of the deployment group -Linux or Windows and the Registration script will be made available accordingly. <br /><img style="float: left; margin: 0 10px 5px 0;" src="https://skdevops.files.wordpress.com/2019/12/ad-gettingstarted-deploymentgroup-image2.png" /> <br />This image above is a registration script for a machine running Windows OS. <br />Copy and paste this registration script on an elevated Powershell command prompt on the target machine -the one that is going to be part of this deployment group. You will be prompted for credentials and tags that you would want to associate with the deployment group. Below is an image of a set of prompts when I added a machine to a deployment group at work (Not this example) <br /><img style="float: left; margin: 0 10px 5px 0;" src="https://skdevops.files.wordpress.com/2019/12/ad-gettingstarted-deploymentgroup-image3.png" /> <br />Once a machine is registered (in Window) you will see a new windows service running by the name VSTS Agent. <br /><img style="float: left; margin: 0 10px 5px 0;" src="https://skdevops.files.wordpress.com/2019/12/ad-gettingstarted-deploymentgroup-image4.png" /> <br />…and on the Deployment group -> Target, you will see this machine is listed. <br /><img style="float: left; margin: 0 10px 5px 0;" src="https://skdevops.files.wordpress.com/2019/12/ad-gettingstarted-deploymentgroup-image5.png" /> <br />Since I am demoing how to create a deployment group, I named the group as <em><strong>DoNotUse</strong></em> (and not as Dev as we had mentioned earlier) just so that no one from the development team starts using this deployment group. In an ideal world, if this was a development environment, I’d name this deployment group as <strong>Dev</strong>. <br /> <strong>Now that we have a deployment group created, how do you link a release definition to a deployment group?</strong> <br />To create a new release definition -> go to Tasks and next to Environment 1 you will see ellipsis which lists three options. We select the <em>add deployment group phase</em> here. <br /><img style="float: left; margin: 0 10px 5px 0;" src="https://skdevops.files.wordpress.com/2019/12/ad-gettingstarted-deploymentgroup-image6.png" /></p>
<p> <strong>What are the benefits of deployment groups?</strong> <br />According to me, these are the benefits: <br />-easy to manage environments like adding and removing machines on scale warrants no change to the deployment process <br />-increases productivity <br />-high trace-ability -what release definition was applied to what deployment group can be identified with a few clicks on the portal</p>
<p> <em>PS: I will cover adding a deployment group to a release definition and tags in a later note. For now, I am discussing the idea of a deployment group from an Azure DevOps standpoint.</em> </p>
<h2>Deployment groups azure devops</h2>

<h3>Deployment groups azure devops</h3>
<p>[youtube]</p>
Deployment groups azure devops <a href="http://remmont.com">Important news today</a> Deployment groups azure devops
<h4>Deployment groups azure devops</h4>
This is part 7 of a multipart series on getting started with Azure DevOps. Please refer to the below links to access other notes in this series. Part 1: Getting started with Azure DevOps Part 2: Getting started with Azure DevOps -work items Part 3: Getting started with Azure DevOps -add a repo Part 4:&hellip;
<h5>Deployment groups azure devops</h5>
Deployment groups azure devops <a href="http://remmont.com">Deployment groups azure devops</a> Deployment groups azure devops
SOURCE: <h6>Deployment groups azure devops</h6> <a href="https://dev-ops.engineer/">Deployment groups azure devops</a> Deployment groups azure devops
#tags#[replace: -,-Deployment groups azure devops] Deployment groups azure devops#tags#
Кабринский Эдуард
news

[HonoluluKn]

Kabrinskiy Eduard - Azure devops client - Eduard Kabrinskiy


<h1>Azure devops client</h1>
<p>[youtube]</p>
Azure devops client <a href="http://remmont.com">National news headlines</a> Azure devops client
<h1>Inspec-Azure in Azure DevOps Pipeline</h1>
<p style="clear: both"><img src="https://tamops.files.wordpress.com/2020/08/image-9.png" /></p>
<p>I am going to show how you can run Inspec-Azure tests in an Azure DevOps Pipeline to test and validate your Azure Resources. In a previous blog post, I blogged <strong>Using Inspec-Azure to test your Azure Resources</strong> . In that blog post I detail how to configure and run Inspec-Azure locally.</p>
<p>In this post I will detail how you can run this in an Azure DevOps Pipeline.</p>
<h3><strong>What is Inspec-Azure?</strong></h3>
<p>Inspec-Azure is a resource pack provided by Chef that uses the Azure REST API, to allow you to write tests for resources that you have deployed in Microsoft Azure. These tests can be used to validate the Azures resources that were deployed via code using Terraform or Azure RM templates. Inspec is an open source framework that is used for testing and auditing your infrastructure, in this blog post I will show how you can create tests against your Azure resources using Inspec-Azure.</p>
<h3><strong>Why run Inspec-Azure in a Pipeline?</strong></h3>
<p>Begin the compliance of your Azure resources right at the source ? the Azure Pipeline that you are deploying Azure resources from!</p>
<p>Having Inspec-Azure run within your Pipeline integration can flag issues straight away and notify relevant parties that the current pipeline release has a validation testing issue. Great!</p>
<p>The deployment may deploy OK and look fine but the deployment has not been validated as what is expected to be deployed and the actual state the specific resources are in.</p>
<h3><strong>Time to Azure DevOps</strong></h3>
<p>In this blog post, I am going to detail how to create an Azure DevOps Pipeline to run Inspec-Azure testing, it will be a single stage Pipeline to outline how to run Inspec-Azure only. You can use this to implement into your required pipelines.</p>
<p>As my example will be ran on an Azure DevOps managed agent, you will need to install ruby and then install inspec-bin via gem install, this is done below:-</p>
<p>The next task, runs a bash script which calls ?inspec exec? , notice within the script block you will need to input the required parameters:-<br /></p>
<p> <table> <tbody> <tr> <td>AZURE_SUBSCRIPTION_ID</td> <td>Subscription ID of your Azure Subscription</td> </tr> <tr> <td>AZURE_CLIENT_ID</td> <td>Client ID of Azure AD Application that has required access to the subscription</td> </tr> <tr> <td>AZURE_CLIENT_SECRET</td> <td>Client Secret of above Azure AD Application</td> </tr> <tr> <td>AZURE_TENANT_ID</td> <td>The Azure Active Directory tenant(directory) ID.</td> </tr> </tbody> </table> </p>
<p>Notice the last line of the above, ?reporter? This will output the test results in JUnit XML file. This will be used with the PublishTestResults@2 to display these results within Azure DevOps Portal ? I will show this later</p>
<p>Finally, to publish test results above to Azure DevOps portal, we will use the PublishTestResults@2 task</p>
<p>Awesome, lets look at how running this pipeline looks within Azure DevOps; I am testing against resources deployed in Azure Portal via Terraform , these resources are found here.</p>
<p>Azure Inspec testing found here ? these tests will test for:-</p>
<p><ul>
<li>Resource Group: <strong>tamops</strong> exists</li>
<li>Virtual Network: <strong>tamops-vnet</strong> exists in Resource Group: <strong>tamops</strong></li>
<li>Virtual Network: <strong>tamops-vnet</strong> has address space: 192.168.0.0/16</li>
<li>Virtual Network: <strong>tamops-vnet</strong> has subnet: <strong>subnet</strong></li>
</ul>
</p>
<p><em><strong>Note:-</strong> In the latest version of Inspec-Azure there is only a certain amount of resources that are available to be tested against, in previous versions of Inspec-Azure you can use azure_generic_resource but it is deprecated in newer versions. In a later blog I will show how this can be referenced and used within a Docker container.</em></p>
<p>Full pipeline to run my Inspec Azure testing:-<br />Pipeline found here on Github</p>
<p>Output of successful run of the pipeline:-</p>
<p style="clear: both"> <img src="https://tamops.files.wordpress.com/2020/08/image-7.png" /></p>
<p>Review ?<strong>Run inspec tests</strong>? to view the inspec-azure tests within the Pipeline job</p>
<p style="clear: both"> <img src="https://tamops.files.wordpress.com/2020/08/image-10.png" /></p>
<p>Now review the tests section of that Pipeline run, easy to read tests results!</p>
<p style="clear: both"> <img src="https://tamops.files.wordpress.com/2020/08/image-9.png" /></p>
<p>Awesome, a nice-readable test result format! Hopefully this blog will assist you to begin implementing Inspec-Azure into your Azure DevOps Pipelines!</p>
<h2>Azure devops client</h2>

<h3>Azure devops client</h3>
<p>[youtube]</p>
Azure devops client <a href="http://remmont.com">Latest world news</a> Azure devops client
<h4>Azure devops client</h4>
I am going to show how you can run Inspec-Azure tests in an Azure DevOps Pipeline to test and validate your Azure Resources. In a previous blog post, I blogged Using Inspec-Azure to test your Azure&nbsp;Resources . In that blog post I detail how to configure and run Inspec-Azure locally. In this post I will&hellip;
<h5>Azure devops client</h5>
Azure devops client <a href="http://remmont.com">Azure devops client</a> Azure devops client
SOURCE: <h6>Azure devops client</h6> <a href="https://dev-ops.engineer/">Azure devops client</a> Azure devops client
#tags#[replace: -,-Azure devops client] Azure devops client#tags#
Kabrinskiy Eduard
latest news today

[HonoluluKn]

Kabrinskiy Eduard - Vsts client - Эдуард Кабринский


<h1>Vsts client</h1>
<p>[youtube]</p>
Vsts client <a href="http://remmont.com">Latest national news headlines</a> Vsts client
<h1>Vsts client</h1>
<p style="clear: both"><img src="https://msdn.microsoft.com/uxresources/Areas/Centers/Themes/StandardDevCenter/Content/HeaderFooterSprite.png" /></p>
<p style="clear: both"><img src="https://msdn.microsoft.com/uxresources/Areas/Centers/Themes/StandardDevCenter/Content/HeaderFooterSprite.png" /></p>
<h3><img src="https://i1.social.s-msft.com/globalresources/Images/trans.gif" /> </h3>
<h3>Asked by:</h3>
<p style="clear: both"><img src="https://i1.social.s-msft.com/globalresources/Images/trans.gif" /></p>
<h3>Question</h3>
<p style="clear: both"><img src="https://i1.social.s-msft.com/globalresources/Images/trans.gif" /></p>
<p style="clear: both"><img src="https://i1.social.s-msft.com/globalresources/Images/trans.gif" /></p>
<h3>All replies</h3>
<p style="clear: both"><img src="https://i1.social.s-msft.com/globalresources/Images/trans.gif" /></p>
<p style="clear: both"><img src="https://i1.social.s-msft.com/globalresources/Images/trans.gif" /></p>
<p>Which version of VS are you using?</p>
<p>VS2010 ultimate RTM contains Team explorer as part of its Installation.</p>
<p>If you have above version, then VS2010 --> other tools should be fine.</p>
<p>Please remember to mark the replies as answers if they help.</p>
<p style="clear: both"><img src="https://i1.social.s-msft.com/globalresources/Images/trans.gif" /></p>
<p style="clear: both"><img src="https://i1.social.s-msft.com/globalresources/Images/trans.gif" /></p>
<p>ohk gr8 help from you.</p>
<p>wl go with vs 2010 on one machine and vs 2008 on one machine.</p>
<p>for vs 2008-->VS SP -->have to install TE separately after Service pack.</p>
<p>ohk. for vs 2010.now no problem. what abt SP for VS 2010?</p>
<p style="clear: both"><img src="https://i1.social.s-msft.com/globalresources/Images/trans.gif" /></p>
<p style="clear: both"><img src="https://i1.social.s-msft.com/globalresources/Images/trans.gif" /></p>
<p>There is no Service Pack(SP) is currently available for VS2010.</p>
<p>Please remember to mark the replies as answers if they help.</p>
<p style="clear: both"><img src="https://i1.social.s-msft.com/globalresources/Images/trans.gif" /></p>
<p style="clear: both"><img src="https://i1.social.s-msft.com/globalresources/Images/trans.gif" /></p>
<p style="clear: both"><img src="https://i1.social.s-msft.com/globalresources/Images/trans.gif" /></p>
<p style="clear: both"><img src="https://i1.social.s-msft.com/globalresources/Images/trans.gif" /></p>
<p>You should not install TFS2008 and TFS2010 on one machine as there are some compatible issues.</p>
<p>In addtion, Team Foundation Server - Setup Forum would be a better place for this kind of issue. If you have got any issues about the setup, you can post there.</p>
<p>Please remember to mark the replies as answers if they help and unmark them if they provide no help. <br />Send us any feedback you have about the help from MSFT at fbmsdn@microsoft.com.</p>
<p style="clear: both"><img src="https://i1.social.s-msft.com/globalresources/Images/trans.gif" /></p>
<p style="clear: both"><img src="https://i1.social.s-msft.com/globalresources/Images/trans.gif" /></p>
<p>I am not talking about TFS 2008 or TFS 2010 installtion on one machine.It was reagrding VS 2008/VS2010 Client installtion.</p>
<p>I have installed VS2008,VS 2008 SP1,TE 2008,Power tools 2008..and on same machine I have installed VS2010.Shall I even install Power tools 2010 here?</p>
<p style="clear: both"><img src="https://i1.social.s-msft.com/globalresources/Images/trans.gif" /></p>
<p style="clear: both"><img src="https://i1.social.s-msft.com/globalresources/Images/trans.gif" /></p>
<p>You can install the any VS client versions side-by-side without any issues.</p>
<p>Please remember to mark the replies as answers and vote as helpful if it provides the solution.</p>
<p style="clear: both"><img src="https://i1.social.s-msft.com/globalresources/Images/trans.gif" /></p>
<p style="clear: both"><img src="https://i1.social.s-msft.com/globalresources/Images/trans.gif" /></p>
<p>Yeah Thanks for ur reply.</p>
<p>I have another query which i have already posted separately but no one replied to it.</p>
<p>my query is as below:</p>
<p>Do i need to install Power tools,TFS Sidekicks,TFS Web access,TFS Admin tool on both machines(on TFS APP tier and Client).</p>
<p>I guess TFS Web access,TFS Admin tool have to install on both?Any idea?</p>
<p>Thanks in advance.</p>
<p style="clear: both"><img src="https://i1.social.s-msft.com/globalresources/Images/trans.gif" /></p>
<p style="clear: both"><img src="https://i1.social.s-msft.com/globalresources/Images/trans.gif" /></p>
<p>When ever you install the team client in the machine, Team web access and team administration tool is default facility when installed the team client in the machine.</p>
<p>Here Team web access only access if you have TFS cal in the company. or If you do not has the CAL, you can only manage the work items only using WIWA.</p>
<p>If you are using team explorer for normal usage like source control, manging work items, reporting no need of installing power tools. If you want to customize the work items or customize the project templates or editing the project folder or exploring the source folders in windows explorer you need the power tools installation.</p>
<p><strong>[[KINDLY MARK AS ANSWER IF IT HELPS TO RESOLVE YOUR QUERY]]</strong> </p>
<p>Regards Bhargava Vangapally, Architect, Software Architectural Group.</p>
<p><strong>[[KINDLY MARK AS ANSWER IF IT HELPS TO RESOLVE YOUR QUERY]]</strong></p>
<h2>Vsts client</h2>

<h3>Vsts client</h3>
<p>[youtube]</p>
Vsts client <a href="http://remmont.com">World news online</a> Vsts client
<h4>Vsts client</h4>
Vsts client Asked by: Question All replies Which version of VS are you using? VS2010 ultimate RTM contains Team explorer as part of its
<h5>Vsts client</h5>
Vsts client <a href="http://remmont.com">Vsts client</a> Vsts client
SOURCE: <h6>Vsts client</h6> <a href="https://dev-ops.engineer/">Vsts client</a> Vsts client
#tags#[replace: -,-Vsts client] Vsts client#tags#
Кабринский Эдуард
breaking news

[HonoluluKn]

Eduard Kabrinskiy - Tfs git pull request - Eduard Kabrinskiy


<h1>Tfs git pull request</h1>
<p>[youtube]</p>
Tfs git pull request <a href="http://remmont.com">Live news</a> Tfs git pull request
<h1>Git, TFS Pull Request Workflow</h1>
<p>Here is the workflow I've been attempting, after watching a this Git/TFS video.</p>
<p>So I create a branch from my development branch</p>
<p>Then I make a change, stage, commit, and push the changes up to the TFS server.</p>
<p>Now when I go to the TFS web interface, I have a "my-feature-branch" on the server.</p>
<p>I click "New Pull Request" and create a PR into development, and Accept this PR. This process deletes the "my-feature-branch" on the TFS server, but it remains on my local machine.</p>
<p>Everything is great at this point.</p>
<p>Back to my local machine, switch out of the feature branch:</p>
<p>Delete the local branch</p>
<p>Sometimes, and I may be doing the pull prior to the delete, the delete Fails and I have to Force Delete it.</p>
<p>Is my workflow wrong? Should I be doing some kind of merge prior to deletion? Why doesn't git know the feature branch has been merged in as a Pull Request after the pull and let me delete without error?</p>
<h2>1 Answer 1</h2>
<blockquote><p>Why doesn't git know the feature branch has been merged in as a Pull Request after the pull and let me delete without error?</p></blockquote>
<p>It?s hard to know from the information you?ve supplied, but here are two guesses:</p>
<p>Are you sure you?re pulling before deleting the local feature branch? If you?re not, then of course the main branch won?t have the new commits.</p>
<p>How are you merging the feature branch in? With a regular merge or a squash merge? A regular merge incorporates the feature branch commits into the main branch, so that Git knows it?s all there. A squash merge, OTOH, incorporates all the <em>content</em> from the feature branch, but does so by creating a new commit, and Git does not track the fact that the new squashed commit was generated from the feature branch commits, so it doesn?t think that the feature branch was merged in.</p>
<p>(I strongly recommend <em>not</em> using squash merges. Keeping the original commits, as a standard merge does, helps make Git work better.)</p>
<h2>Tfs git pull request</h2>

<h3>Tfs git pull request</h3>
<p>[youtube]</p>
Tfs git pull request <a href="http://remmont.com">Main news today</a> Tfs git pull request
<h4>Tfs git pull request</h4>
Git, TFS Pull Request Workflow Here is the workflow I've been attempting, after watching a this Git/TFS video. So I create a branch from my development branch Then I make a change, stage,
<h5>Tfs git pull request</h5>
Tfs git pull request <a href="http://remmont.com">Tfs git pull request</a> Tfs git pull request
SOURCE: <h6>Tfs git pull request</h6> <a href="https://dev-ops.engineer/">Tfs git pull request</a> Tfs git pull request
#tags#[replace: -,-Tfs git pull request] Tfs git pull request#tags#
Эдуард Кабринский
world news

[FriscoSige]

Eduard Kabrinskiy - Ios devops - Kabrinskiy Eduard


<h1>Ios devops</h1>
<p>[youtube]</p>
Ios devops <a href="http://remmont.com">Latest news update</a> Ios devops
<h1>Release Xamarin iOS app with Azure DevOps</h1>
<p>Releasing an iOS App means that you have already created the executable file and is correctly signed. So it is ready to be deployed to the App Store.</p>
<p>If you are not sure how to preform that you can follow these two links:</p>
<h2>Create release</h2>
<h4>Initial creation</h4>
<ul>
<li>From the Pipelines in the menu choose Releases, on the plus button click New and New release pipeline</li>
<li>Select start with an empty job and add name to the stage e.g. Deploy app to Test Flight and close the dialog the updated name will be auto saved</li>
<li>On the + Add an artifact from the build source choose the definition that builds your app and contains the ipa file in the artifacts</li>
<li>All other fields will be preselected, if you want to make more additional changes change the available options.</li>
<li>Click add</li>
</ul>
<h4>Create Task that builds your app</h4>
<ul>
<li>On stages select the stage that deploys your app and in the tasks click on the plus button</li>
<li>From the Tasks search for ?Apple app Store release? and choose the task named like that</li>
</ul>
<blockquote><p>Note: In the Agent Job > Agent specification you should choose Mac OS or choose your Mac as self hosted agent</p> </blockquote>
<h4>Lets get back to the task</h4>
<h4>? Authentication method</h4>
<p>There are two options to authenticate with App Store. The Service connection and Username and Password. The main difference between these two is that Service connection can be used between other pipelines (if access granted).</p>
<p><strong>User Name and Password</strong></p>
<p><ul>
<li>In the email field enter your email and in the password enter the password from your Apple Store account, if you are using two steps verification check the field and type those credentials as well.</li>
</ul>
</p>
<p><strong>Service connection</strong> </p>
<p><ul>
<li>Click on manage and you will be navigated to Service connections in Settings</li>
<li>Click on new service connection and choose Apple App Store than Next <ul>
<li>In App Store email add your email address form App Store</li>
<li>In Password your personal password from App Store</li>
<li>In the Service connection name add meaningful name for your connection</li>
</ul>
</li>
</ul>
</p>
<p>Since other fields are optional you can just click save and the connection will be created for you</p>
<p><ul>
<li>Navigate back to the release task and click on the refresh button next to the Service connection field and the connection will appear.</li>
</ul>
</p>
<h4>? Bundle ID</h4>
<p>In the Bundle ID enter your unique identifier. That can be find in the info.plist from your Xamarin.iOS project the string form CFBundleIdentifier key.</p>
<h4>? Binary Path</h4>
<p>In the Binary Path choose the .ipa file from the drop, that file is the one from the artifacts that was created from the previous successful build definition.</p>
<h2>Ios devops</h2>

<h3>Ios devops</h3>
<p>[youtube]</p>
Ios devops <a href="http://remmont.com">Latest national news</a> Ios devops
<h4>Ios devops</h4>
Releasing an iOS App means that you have already created the executable file and is correctly signed. So it is ready to be deployed to the App Store. If you are not sure how to preform that you can follow these two links:&nbsp; Create distribution certificates and provisioning profiles from you Apple accountBuild Xamarin iOS&hellip;
<h5>Ios devops</h5>
Ios devops <a href="http://remmont.com">Ios devops</a> Ios devops
SOURCE: <h6>Ios devops</h6> <a href="https://dev-ops.engineer/">Ios devops</a> Ios devops
#tags#[replace: -,-Ios devops] Ios devops#tags#
Эдуард Кабринский
headline news

[FriscoSige]

Devops advocate - Kabrinskiy Eduard


<h1>Devops advocate</h1>
<p>[youtube]</p>
Devops advocate <a href="http://remmont.com">Newspaper headlines</a> Devops advocate
<h1>DevOps</h1>
<p style="clear: both"><img src="https://software.af.mil/oahotcha/2019/08/devops-loop.svg" /></p>
<p><strong>DevOps</strong>is a software engineering culture and practice that aims at unifying software development (Dev) and software operation (Ops). The main characteristic of the DevOps movement is to strongly advocate automation and monitoring at all steps of software construction, from integration, testing, releasing to deployment and <u>i</u>nfrastructure management. DevOps aims at shorter development cycles, increased deployment frequency, and more dependable releases, in close alignment with business objectives.</p>
<p><strong>DevOps is NOT ENOUGH!</strong> Dev<u>Sec</u>Ops is what must be implemented with the cybersecurity stack built-in into the DevOps pipeline.</p>
<h2>Benefits of DevOps</h2>
<ul>
<li>Implementing DevOps allows organizations to get more done. DevOps promotes teamwork by eliminating silos and encouraging collaboration. Teams that adopt the DevOps model are able to increase lead time, create new features at a faster pace, all while driving innovation and increasing employee engagement and communication. In turn, they are making applications more secure and stable.</li>
<li>When leveraging DevOps and implementing continuous integration and continuous delivery (CI/CD), organizations can see a tremendous improvement in deployment frequency, lead time, detection of cybersecurity vulnerabilities and flaws, mean time to repair and mean time to recovery. <br />Learn more : <u>https://www.forbes.com/sites/forbestechcouncil/2018/07/19/the-two-biggest-disruptions-to-cybersecurity-since-the-invention-of-the-firewall/</u></li>
<li>Allows for rapid experimentation and uncertainty while focusing on mission end goals.</li>
<li>Enable rapid prototyping and A/B testing or canary releases.</li>
<li>New services and innovations are made available</li>
<li>Frequency of deployments is increased</li>
<li>Collaboration between various department is increased</li>
<li>Time spent maintaining applications and fixing is greatly reduced</li>
<li>Number of end users who are using organizations? services is increased</li>
<li>Performance and quality of applications is improved</li>
<li>Time-to-market is reduced</li>
<li>Time needed for testing, development and operations is reduced.</li>
<li>Avoids shadow IT by enabling all directorates/divisions/services to reuse the DevSecOps pipeline instead of reinventing the wheel and building their own pipeline without supervision</li>
<li>Avoids technical debt by continuously fixing bugs and security issues thanks to automated tests and real-time scans.</li>
</ul>
<h2>DevOps Metrics</h2>
<ul>
<li><strong>Mean-time to recovery (MTTR):</strong> shows how long it would take applications in the production stage to recover from failure</li>
<li><strong>Mean-time to production</strong>: show how long it takes when new code is committed into code repository</li>
<li><strong>Average lead-time</strong>: shows how long it would take for a new requirement to be delivered and deployed</li>
<li><strong>Deployment speed</strong>: shows how fast you can deploy a new version of the application between staging, test and production</li>
<li><strong>Deployment frequency</strong>: shows how often you can deploy a new release into production environment and testing / QA.</li>
<li><strong>Production failure rate</strong>: shows how often software fails during production</li>
</ul>
<h3>DevSecOps Metrics</h3>
<ul>
<li>Ability to detect and prevent security flaws and injections.</li>
<li>Ability to perform fuzzing and static/dynamic source code analysis.</li>
<li>Ability to monitor container security including container base images and libraries.</li>
</ul>
<h2>DevOps Challenges</h2>
<ol>
<li>Culture <br /></strong>Solution: Organizations should focus on building a collaborative culture with shared goals. This also includes finding employees who are DevOps champions in the organization.</li>
</ol>
<ol>
<li><strong>Test automation <br /></strong>Solution: Many organizations neglect test automation while focusing on CI/CD deployments. Continuous testing is key for DevOps success, and security must be considered from the outset.</li>
</ol>
<ol>
<li><strong>Legacy systems <br /></strong>Solution: Include modeling for legacy infrastructure and applications in your DevOps plans. Installing new hardware or software to coexist with older systems is always difficult.</li>
</ol>
<ol>
<li><strong>App complexity <br /></strong>Solution: Consider application architecture changes based on on-premises, cloud, and containers early on in the process.</li>
</ol>
<ol>
<li><strong>No DevOps plan <br /></strong>Solution: Create a clear plan that includes milestones, project owners, and well-defined deliverables.</li>
</ol>
<ol>
<li><strong>Managing environments <br /></strong>Solution: Your organization can standardize and automate complex DevOps environments with cloud sandboxes and other tools.</li>
</ol>
<ol>
<li><strong>Skillset <br /></strong>Solution: Teams need training on DevOps. Organizations should standardize processes and establish common operational procedures.</li>
</ol>
<ol>
<li><strong>Budget <br /></strong>Solution: Remember that <strong>open source does not mean free</strong>, and factor in integration and operational complexity in your costs.</li>
</ol>
<ol>
<li><strong>Tools <br /></strong>Solution: Avoid fragmented toolset adoption, which can add to your costs.</li>
</ol>
<ol>
<li><strong>Leadership support <br /></strong>Solution: Educate leadership about the benefits of DevOps, in order to gain resource and budget support.</li>
</ol>
<h2>Containers</h2>
<h3>Benefits</h3>
<ul>
<li>Platform independence: Build it once, run it anywhere</li>
<li>Resource efficiency and density</li>
<li>Effective isolation and resource sharing</li>
<li>Speed: Start, create, replicate or destroy containers in seconds</li>
<li>Immense and smooth scaling</li>
<li>Operational simplicity</li>
<li>Improved developer productivity and development pipeline (thanks to DevOps)</li>
</ul>
<p>Continuous Integration (CI) and Continuous Delivery (CD) are key parts of the DevOps pipeline.</p>
<p><ul>
<li><strong>Continuous integration (CI)</strong> is the practice of consolidating all new source code into a shared version control server such as GitHub, several times a day.</li>
<li><strong>Continuous delivery (CD)</strong> is used to deliver (release) software in short cycles, ensuring that the software can be reliably released at any time. It aims at building, testing, and releasing software with complete automation. The approach helps reduce the cost, time, and risk of delivering changes by allowing for more incremental updates to applications in production. A straightforward and repeatable deployment process is important for continuous delivery.</li>
<li><u>Extreme programming</u>(XP) adopted the concept of CI and did advocate integrating more than once per day ? perhaps as many as tens of times per day.</li>
</ul>
</p>
<h2>Agile vs DevSecOps</h2>
<p>DevSecOps is the next evolution of agile and builds on the agile principles by adding the following:</p>
<p><ul>
<li>Leverages Containers and Microservices concepts.</li>
<li>Leverages Cloud deployment for scalability and prototyping.</li>
<li>Continuous Integration/Continuous Delivery to rapidly prototype, test and deploy.</li>
<li>Leverage A/B testing and canary deployment for rapid feedback loops.</li>
<li>Embed security in the pipeline instead of an afterthought.</li>
</ul>
</p>
<h2>Automated Testing</h2>
<p>Automated testing is a key part of DevSecOps. It is enabled by multiple tools that measure both test code coverage and test results. They are fully automated and do not require human action.</p>
<p>It also enables new concepts like pair programming and peer code review.</p>
<p>Agile brings several new models for creating the right tests:</p>
<p><strong>Test-driven development (TDD)</strong> is a <u>software development process</u> that relies on very short development cycles: requirements are turned into very specific <u>test cases</u> first, then the software is built to pass the tests.</p>
<p><strong>Acceptance test?driven development (ATDD)</strong> is a <u>development</u> methodology based on communication between the business customers, the developers, and the testers. ATDD encompasses many of the same practices as <u>specification by example</u>, <u>behavior-driven</u> <u>development</u> (BDD), example-driven development (EDD), and support-driven development also called story test?driven development (SDD). All these processes aid developers and testers in understanding the customer?s needs prior to implementation and allow customers to be able to converse in their own domain language.</p>
<h2>Extreme DevOps Risk Management Example ? Chaos Monkey (Netflix)</h2>
<p>Chaos Monkey is a tool invented in 2011 by <u>Netflix</u> to test the <u>resilience</u> of its IT infrastructure. It works by intentionally disabling computers in <u>Netflix</u>?s production network to test how remaining systems respond to the outage. Chaos Monkey is now part of a larger suite of tools called the Simian Army designed to simulate and test responses to various system failures and edge cases.</p>
<p>As part of the DevOps movement, special attention is paid to the safe operation of computer systems, thus providing a sufficient level of confidence despite frequent releases. By contributing to the DevOps Tool Chain, Chaos Monkey meets the need for continuous testing.</p>
<p>They are part of the pattern ?Design for failure?, ?designed to support failure?: a computer application must be able to support the failure of any underlying software or hardware component.</p>
<h2>Devops advocate</h2>

<h3>Devops advocate</h3>
<p>[youtube]</p>
Devops advocate <a href="http://remmont.com">Current news</a> Devops advocate
<h4>Devops advocate</h4>
DevOps DevOps is a software engineering culture and practice that aims at unifying software development (Dev) and software operation (Ops). The main characteristic of the DevOps movement is
<h5>Devops advocate</h5>
Devops advocate <a href="http://remmont.com">Devops advocate</a> Devops advocate
SOURCE: <h6>Devops advocate</h6> <a href="https://dev-ops.engineer/">Devops advocate</a> Devops advocate
#tags#[replace: -,-Devops advocate] Devops advocate#tags#
https://ssylki.info/?who=hyde-park-apar ... emmont.com https://ssylki.info/?who=remmont.com/ja ... ton-swat-8 https://ssylki.info/?who=remmont.com/i- ... sale-video https://ssylki.info/?who=remmont.com/da ... pe-parts-2 https://ssylki.info/?who=remmont.com/police-k9-4

[HonoluluKn]

Agile and devops - Кабринский Эдуард


<h1>Agile and devops</h1>
<p>[youtube]</p>
Agile and devops <a href="http://remmont.com">Top news</a> Agile and devops
<h1>Agile and devops</h1>
<p style="clear: both"><img src="https://www.techarcis.com/wp-content/uploads/2017/11/DevOps2-1024x642-1.png" /></p>
<ul>
By: admin Category: Agile Testing & DevOps
</ul>
<p>Agile methodology is widely adopted in almost all the enterprises, its advantages and the agility it brings to software and product development process is widely recognized. Organizations are now on the path to adopt DevOps, which is a step in the direction of continuous development, Integration and Deployment (CI/CD).</p>
<p>Agile development is kind of an incremental model, where software can be developed in incremental rapid cycles. We can now create small incremental software releases with every release based on the previous functionality. And each release is methodically tested to ascertain the software quality. Extreme Programming (XP) is one of the methods used in agile development lifecycle model.</p>
<p>Test-driven development, requirements-based testing, constant delivery came to the focus and with these, DevOps matured into a legitimate enterprise practice. At present, DevOps, a method that encompasses agile principles fits very well with integrated software development, testing, operations & maintenance.</p>
<p>The main question now seems to be how software development lifecycle management tools will be able to integrate DevOps functionality. This convergence could result in next-generation ALM platforms either merging Continuous Integration & Delivery features into their existing functionality or tightly integrating with DevOps tools. This will help enterprises enhance organizational Agility by providing a single platform to manage the entire development lifecycle from planning to deployment.</p>
<h5> <strong>Download Whitepaper: ROLE OF TESTING IN DIGITAL TRANSFORMATION </strong></h5>
<p><strong>Key advantages of leveraging Agile and DevOps:</strong></p>
<p><ul>
<li>Customer satisfaction by quick delivery of software to market. (Speed to Market)</li>
<li>Interactions amongst Developers, Testers and Ops teams are a priority (in addition to implementing process and tools)</li>
<li>Effective software is delivered regularly (weeks rather than months).</li>
<li>Agile enables close, daily cooperation between business teams, developers and testers.</li>
<li>Unhindered attention to technical features and good design.</li>
<li>Even advanced changes in requirements can be accommodated in Agile.</li>
</ul>
</p>
<h3>Hear the Industry expert?s opinion on implementing DevOps (Sunil Sehgal, Managing Director @ TechArcis):</h3>
<p><iframe src="https://www.youtube.com/embed/MDGqwZy0NdE"></iframe></p>
<p><strong>Now let?s focus on the multifaceted advantages of software testing in an agile environment:</strong></p>
<p>Speed to Market and Better teamwork: Collaboration and teamwork amongst Developers, BA?s. PM?s, Testers result in speed and swift building of the product.</p>
<p><strong>Cost effective:</strong> Integrating software testing tools and testers optimize the process of testing in an agile environment with better resource utilization and optimized delivery. This process focuses on the quality of the software. The bug fixing at the initiation of each step of development reduces the overall spend of a project and speeds up the product release process.</p>
<p><strong>Tighter Alignment of the teams:</strong> One of the prime advantages of agile is fixing bugs immediately. And this happens because the group of testers and developers work in a collaborative environment that helps them to communicate the problem for the instant feedback, which in order simplifies fixing of bug and errors while the coding is done.</p>
<p><strong>Enhanced Quality:</strong> Agile testing provides identifiable and measurable results in smaller cycles. Besides, it restricts an application or product encountering severe defects and helps enterprises to optimize quality and performance.</p>
<h5> <strong>Download Whitepaper: Importance of automation and testing ? Why DevOps? </strong></h5>
<p>DevOps is also gaining traction for the mainstream software development, it is expected that Year 2018 will see an increased adoption of DevOps.</p>
<h2>Agile and devops</h2>

<h3>Agile and devops</h3>
<p>[youtube]</p>
Agile and devops <a href="http://remmont.com">News update</a> Agile and devops
<h4>Agile and devops</h4>
Agile and devops By: admin Category: Agile Testing & DevOps Agile methodology is widely adopted in almost all the enterprises, its advantages and the agility it brings to software
<h5>Agile and devops</h5>
Agile and devops <a href="http://remmont.com">Agile and devops</a> Agile and devops
SOURCE: <h6>Agile and devops</h6> <a href="https://dev-ops.engineer/">Agile and devops</a> Agile and devops
#tags#[replace: -,-Agile and devops] Agile and devops#tags#
https://ssylki.info/?who=used-cars-for- ... emmont.com https://ssylki.info/?who=instant-payday ... emmont.com https://ssylki.info/?who=apartment-finder.remmont.com https://ssylki.info/?who=compare-health ... emmont.com https://ssylki.info/?who=carsdirect.remmont.com

[FriscoSige]

Vsts docker - Kabrinskiy Eduard


<h1>Vsts docker</h1>
<p>[youtube]</p>
Vsts docker <a href="http://remmont.com">Latest news headlines today</a> Vsts docker
<h1>Vsts docker</h1>
<p><i>In this blog series on</i> <i>Continuous Delivery with Containers</i> <i>I'm documenting what I've learned about Docker and containers (both the Linux and Windows variety) in the context of continuous delivery with Visual Studio Team Services. It's a new journey for me so do let me know in the comments if there is a better way of doing things!</i></p>
<p>In the previous post in this series I explained how to use VSTS and Docker to build and deploy an ASP.NET Core application to a Linux VM running in Azure. It's a good enough starting point but one of the first objections anyone working in a private organisation is likely to have is publishing Docker images to the public Docker Hub. One answer is to pay for a private repository in the Docker Hub but for anyone using Azure a more appealing option might be the Azure Container Registry. This is a new offering from Microsoft -- it's still in preview and some of the supporting tooling is only partially baked. The core product is perfectly functional though so in this post I'm going to be amending the pipeline I built in the previous post with Azure Container Registry to find out how it differs from Docker Hub. If you want to follow along with this post you'll need to make sure you have a working pipeline as I describe in my previous post.</p>
<h4>Create an Azure Container Registry</h4>
<p>At the time of writing there is no PowerShell experience for ACR so unless you want to use the CLI 2.0 it's a case of using the portal. I quite like the CLI but to keep things simple I'm using the portal. For some reason ACR is a marketplace offering so you'll need to add it from <strong>New</strong> > <strong>Marketplace</strong> > <strong>Containers</strong> > <strong>Container Registry (preview)</strong>. Then follow these steps:</p>
<p style="clear: both"><ol>
<li>Create a new resource group that will contain all the ACR resources -- I called mine <strong>PrmAcrResourceGroup</strong>.</li>
<li>Create a new standard storage account for the ACR -- I called mine <strong>prmacrstorageaccount</strong>. Note that at the time of writing ACR is only available in a few regions in the US and the storage account needs to be in the same region. I chose <strong>West US</strong>.</li>
<li>Create a new container registry using the resource group and storage account just created -- I called mine <strong>PrmContainerRegistry.</strong> As above, the registry and storage account need to be in the same location. You will also need to enable the <strong>Admin user</strong>: <br /><img style="float: left; margin: 0 10px 5px 0;" src="https://i1.wp.com/pleasereleaseme.net/wp-content/uploads/2016/11/azure-portal-create-container-registry.png" /></li>
</ol>
</p>
<h4>Add a New Docker Registry Connection</h4>
<p>This registry connection will be used to replace the connection made in the previous post to Docker Hub. The configuration details you need can be found in the <strong>Access key</strong> blade of the newly created container registry:</p>
<p style="clear: both"><img src="https://i0.wp.com/pleasereleaseme.net/wp-content/uploads/2016/12/azure-portal-container-registry-access-key-blade.png" /></p>
<p>Use these settings to create a new <strong>Docker Registry</strong> connection in the VSTS team project:</p>
<p style="clear: both"><img src="https://i1.wp.com/pleasereleaseme.net/wp-content/uploads/2016/12/vsts-services-endpoints-azure-container-registry.png" /></p>
<h4>Amend the Build</h4>
<p>Each of the three Docker tasks that form part of the build need amending as follows:</p>
<p><ul>
<li>Docker Registry Connection =</li>
<li>Image Name = <strong>aspnetcorelinux:$(Build.BuildNumber)</strong></li>
<li>Qualify Image Name = <strong>checked</strong></li>
</ul>
</p>
<p>One of the most crucial amendments turned out to be the <strong>Qualify Image Name</strong> setting. The purpose of this setting is to prefix the image name with the registry hostname, but if left unchecked it seems to default to Docker Hub. This causes an error during the push as the task tries to push to Docker Hub which of course fails because the registry connection has authenticated to ACR rather than Docker Hub:</p>
<p style="clear: both"><img src="https://i2.wp.com/pleasereleaseme.net/wp-content/uploads/2016/12/vsts-docker-push-error.png" /></p>
<p>It was obvious once I'd twigged what was going on but it had me scratching my head for a little while!</p>
<h4>Final Push</h4>
<p>With the amendments made you can now trigger a new build, which should work exactly as before except now the docker image is pushed to -- and run from -- your ACR instance rather than Docker Hub.</p>
<p>Your next question is probably going to be how can I get a list of the repositories I've created in ACR? Don't bother looking in the portal since -- at the time of writing at least -- there is no functionality there to list repositories. Instead one of the guys at Microsoft has created a separate website which, once authenticated, shows you this information:</p>
<p style="clear: both"><img src="https://i2.wp.com/pleasereleaseme.net/wp-content/uploads/2016/12/acr-portal.png" /></p>
<p>If you want to do a bit more you can use the CLI 2.0. The syntax to list repositories for example is <strong>az acr repository list -n .</p>
<p>It's early days yet however the ACR is looking like a great option for anyone needing a private container registry and for whom an Azure option makes sense. Do have a look at the documentation and also at Steve Lasker's Connect(); video here.</p>
<h2>Vsts docker</h2>

<h3>Vsts docker</h3>
<p>[youtube]</p>
Vsts docker <a href="http://remmont.com">Newspaper headlines</a> Vsts docker
<h4>Vsts docker</h4>
In this post I explain how to amend a VSTS / Docker deployment pipeline with Azure Container Registry.
<h5>Vsts docker</h5>
Vsts docker <a href="http://remmont.com">Vsts docker</a> Vsts docker
SOURCE: <h6>Vsts docker</h6> <a href="https://dev-ops.engineer/">Vsts docker</a> Vsts docker
#tags#[replace: -,-Vsts docker] Vsts docker#tags#
https://ssylki.info/?who=car-insurance- ... emmont.com https://ssylki.info/?who=remmont.com/fr ... stercard-2 https://ssylki.info/?who=motor-car.remmont.com https://ssylki.info/?who=renters-insurance.remmont.com https://ssylki.info/?who=online-kredit.remmont.com

[HonoluluKn]

Docker and devops - Кабринский Эдуард


<h1>Docker and devops</h1>
<p>[youtube]</p>
Docker and devops <a href="http://remmont.com">Today's news headlines in english</a> Docker and devops
<h1>Software Engineering Institute</h1>
<h4>Blogs</h4>
<h2>DevOps and Docker</h2>
<p style="clear: both"><img src="https://insights.sei.cmu.edu/mt-static/support/assets_c/userpics/userpic-139-180x180.png" /></p>
<h6>January 15, 2015 ? DevOps Blog</h6>
<h5>Joe Yankel </h5>
<p>Docker is quite the buzz in the DevOps community these days, and for good reason. Docker containers provide the tools to develop and deploy software applications in a controlled, isolated, flexible, highly portable infrastructure. Docker offers substantial benefits to scalability, resource efficiency, and resiliency, as we'll demonstrate in this posting and upcoming postings in the DevOps blog.</p>
<p>Linux container technology (LXC), which provides the foundation that Docker is built upon, is not a new idea. LXC has been in the linux kernel since version 2.6.24, when Control Groups (or cgroups) were officially integrated. Cgroups were actually being used by Google as early as 2006, since Google has always been looking for ways to isolate resources running on shared hardware. In fact, Google acknowledges firing up over 2 billion containers a week and has released its own version of LXC containers called lmctfy, or "Let Me Contain That For You."</p>
<p>Unfortunately, none of this technology has been easy to adopt until Docker came along and simplified container technology, making it easier to utilize. Before Docker, developers had a hard time accessing, implementing, or even understanding LXC let alone its advantages over hypervisors. DotCloud founder and current Docker chief technology officer Solomon Hykes was on to something really big when he began the Docker project and released it to the world as open source in March 2013. Docker's ease of use is due to its high-level API and documentation, which enabled the DevOps community to dive in full force and create tutorials, official containerized applications, and many additional technologies. By lowering the barrier to entry for container technology, Docker has changed the way developers share, test, and deploy applications.</p>
<p>How can Docker help us in DevOps? Well, developers can now package up all the runtimes and libraries necessary to develop, test, and execute an application in an efficient, standardized way and be assured that it will deploy successfully in any environment that supports Docker.</p>
<p>Initial reactions to container technology often compare containers to small virtual machines. However, the advantages of containers over VMs becomes apparent with regards to performance. In particular, a Dockerized application starts quickly, without the need to perform all of the steps associated with starting a full operating system. These containers share the operating system kernel, and other binaries and libraries where appropriate. Below is an image from the Docker website that highlights the differences. In particular, note how containers incur much less time and space overhead than virtual machines.</p>
<p style="clear: both"><img src="https://insights.sei.cmu.edu/assets/content/VM-Diagram.png" /></p>
<h5>Docker vs Virtual Machine</h5>
<p>Another great feature is the built-in versioning that Docker provides. This "git-like" versioning system can track changes made to a container, and both public and private repositories (if your organization desires or requires) can be used to store the versioned containers.</p>
<p>Docker had a big impact in 2014, and in 2015 you can expect even greater adoption by both small and large companies. This uptake is evident since Docker support has quickly been adopted by major cloud services, such as Amazon Web Services and Microsoft Azure.</p>
<p>We expect Docker to play a key role in future conversations that focus on designing, building, and deploying applications, especially with the guarantee that an application will run in a production, or customer environment, just as it did during development and testing. A few weaknesses become evident when it comes to communication between Docker containers running on different servers, but this will only improve with time. You can also expect some competition around the corner in 2015. If you haven't tried Docker yet, definitely give it a try. This technology is really just beginning to fire on all cylinders and so much more is to come.</p>
<p>Every two weeks, the SEI will publish a new blog post that will offer guidelines and practical advice to organizations seeking to adopt DevOps in practice. We welcome your feedback on this series, as well as suggestions for future content. Please leave feedback in the comments section below.</p>
<p><strong>Additional Resources</strong></p>
<p>To listen to the podcast,<em> DevOps--Transform Development and Operations for Fast, Secure Deployments</em>, featuring Gene Kim and Julia Allen, please visit http://url.sei.cmu.edu/js.
<p>To read all the installments in our weekly DevOps series, please click here.</p>
<h2>Docker and devops</h2>

<h3>Docker and devops</h3>
<p>[youtube]</p>
Docker and devops <a href="http://remmont.com">World news</a> Docker and devops
<h4>Docker and devops</h4>
Software Engineering Institute Blogs DevOps and Docker January 15, 2015 ? DevOps Blog Joe Yankel Docker is quite the buzz in the DevOps community these days, and for good
<h5>Docker and devops</h5>
Docker and devops <a href="http://remmont.com">Docker and devops</a> Docker and devops
SOURCE: <h6>Docker and devops</h6> <a href="https://dev-ops.engineer/">Docker and devops</a> Docker and devops
#tags#[replace: -,-Docker and devops] Docker and devops#tags#
https://ssylki.info/?who=carquest-auto- ... emmont.com https://ssylki.info/?who=remmont.com/ch ... partment-4 https://ssylki.info/?who=apt-for-rent.remmont.com https://ssylki.info/?who=vacation-rentals.remmont.com https://ssylki.info/?who=remmont.com/ea ... l-mugshots