Putting the DOT in .NET - Dev/Ops/Test

Editor's Notes

• #6: What is driving DevOps? The agile methodologies are accelerating the construction process and creating a significant pressure to Operations teams to update their existing practices to make enable faster cadence, in other words changing and adopting existing process to not only be reliable but also support and agile cadence. In our internal teams and with some of our enterprise customers we noticed that once a team is able to accelerate the construction phase consistently. The next evolution process is to ensure such applications remind available and performing as expected. And when they aren’t having access to information and tools that allow both Operations and development teams to diagnostic and fix issues quickly. Then these teams become more sophisticated and mature and then they want to have access to customer usage information to use quantitative and qualitative data to help them determine the next set of investments and enable continuous learning.
• #7: What is driving DevOps? The agile methodologies are accelerating the construction process and creating a significant pressure to Operations teams to update their existing practices to make enable faster cadence, in other words changing and adopting existing process to not only be reliable but also support and agile cadence. In our internal teams and with some of our enterprise customers we noticed that once a team is able to accelerate the construction phase consistently. The next evolution process is to ensure such applications remind available and performing as expected. And when they aren’t having access to information and tools that allow both Operations and development teams to diagnostic and fix issues quickly. Then these teams become more sophisticated and mature and then they want to have access to customer usage information to use quantitative and qualitative data to help them determine the next set of investments and enable continuous learning.
• #10: People = Culture Fundamental attributes of successful cultures: Shared mission and incentives: infrastructure as code, apps as services, DevOps/all as teams You need to consider your hardware as a commodity, (don't give your servers names) , servers are like farm animals, it is just harder if you let theids name them Build deep instrumentation into services, push complexity up the stack Rally around agile, shared metrics, CI, service owners on call, etc. Changing the culture: any change takes time, changing culture is no exception and you can't do it alone, exploit compelling events to change culture: downtimes, cloud adoption, devops buzz PROCESSDefinition and design, compliance, and continuous improvement PEOPLEResponsibilities, management, skills development, and discipline ProductsTools and infrastructure
• #12: What is driving DevOps? The agile methodologies are accelerating the construction process and creating a significant pressure to Operations teams to update their existing practices to make enable faster cadence, in other words changing and adopting existing process to not only be reliable but also support and agile cadence. In our internal teams and with some of our enterprise customers we noticed that once a team is able to accelerate the construction phase consistently. The next evolution process is to ensure such applications remind available and performing as expected. And when they aren’t having access to information and tools that allow both Operations and development teams to diagnostic and fix issues quickly. Then these teams become more sophisticated and mature and then they want to have access to customer usage information to use quantitative and qualitative data to help them determine the next set of investments and enable continuous learning.
• #17: Virtual Machines + Puppet/chef Ops Dashboard
• #40: mfbclients://awesomedemo.visualstudio.com/DefaultCollection/p:grumpylevel?rid=38%2C39
• #44: InRelease does 4 main things: One- It automates deployments directly from TFS to all the environments, including production. Part of the deployment procedure may include things like taking back-ups, generating test data, provisioning Servers on Azure or executing your automated tests. Basically everything you need to start working on a given stage. InRelease ensures that all deployments are done the same way from the same binaries so that by the time you deploy your application to production, your deployment procedure has been tested over and over - removing a lot of those release related risks & headaches Two - InRelease automates the approval workflow through all the environments reducing delays and coordination issues to a minimum. Along the way, InRelease will provide tracking of each attempted release and provide complete traceability for diagnostic and audit purposes. You can actually set simple to complex deployment procedure in InRelease….
• #45: Infrastructure Lab Manager InRelease – actions to trigger provisioning VMs Applications MS Tools – default behavior to publish to single environment, requires work to publish beyond that TfsDeployer – can leverage Build Quality in TFS to trigger moving parts to other environments, still requires custom scripts InRelease – can deploy applications using different approaches using built-in actions and tools Tests Microsoft Test Manager / Coded UI – helps define and execute automation of tests InRelease – can leverage existing tests for execution and can trigger test data creation via built-in actions and tools Approval InRelease – can manage governance, controls when and if deployments go into environments, notifies recipients of actions throughout the release process