#ATAGTR2019 Presentation "Role of QA in world of DevOps" By Prashant Beniwal

Editor's Notes

• #17: TODO Hands on example of using any one tool. Eg Chef. Write a recipe to read a war file from FS and then copy it to another server Another recipe to run the war file
• #18: What is Continuous Delivery? Continuous Delivery is the ability to get changes of all types—including new features, configuration changes, bug fixes and experiments—into production, or into the hands of users, safely and quickly in a sustainable way. Our goal is to make deployments—whether of a large-scale distributed system, a complex production environment, an embedded system, or an app—predictable, routine affairs that can be performed on demand. We achieve all this by ensuring our code is always in a deployable state, even in the face of teams of thousands of developers making changes on a daily basis. We thus completely eliminate the integration, testing and hardening phases that traditionally followed “dev complete”, as well as code freezes. Why continuous delivery? It is often assumed that if we want to deploy software more frequently, we must accept lower levels of stability and reliability in our systems. In fact, peer-reviewed research shows that this is not the case—high performance teams consistently deliver services faster and more reliably than their low performing competition. This is true even in highly regulated domains such as financial services and government. This capability provides an incredible competitive advantage for organizations that are willing to invest the effort to pursue it. The practices at the heart of continuous delivery help us achieve several important benefits: Low risk releases. The primary goal of continuous delivery is to make software deployments painless, low-risk events that can be performed at any time, on demand. By applying patterns such asblue-green deployments it is relatively straightforward to achieve zero-downtime deployments that are undetectable to users. Faster time to market. It’s not uncommon for the integration and test/fix phase of the traditional phased software delivery lifecycle to consume weeks or even months. When teams work together to automate the build and deployment, environment provisioning, and regression testing processes, developers can incorporate integration and regression testing into their daily work and completely remove these phases. We also avoid the large amounts of re-work that plague the phased approach. Higher quality. When developers have automated tools that discover regressions within minutes, teams are freed to focus their effort on user research and higher level testing activities such as exploratory testing, usability testing, and performance and security testing. By building a deployment pipeline, these activities can be performed continuously throughout the delivery process, ensuring quality is built in to products and services from the beginning. Lower costs. Any successful software product or service will evolve significantly over the course of its lifetime. By investing in build, test, deployment and environment automation, we substantially reduce the cost of making and delivering incremental changes to software by eliminating many of the fixed costs associated with the release process. Better products. Continuous delivery makes it economic to work in small batches. This means we can get feedback from users throughout the delivery lifecycle based on working software. Techniques such as A/B testing enable us to take a hypothesis-driven approach to product development whereby we can test ideas with users before building out whole features. This means we can avoid the 2/3 of features we build that deliver zero or negative value to our businesses. Happier teams. Peer-reviewed research has shown continuous delivery makes releases less painful and reduces team burnout. Furthermore, when we release more frequently, software delivery teams can engage more actively with users, learn which ideas work and which don’t, and see first-hand the outcomes of the work they have done. By removing the low-value painful activities associated with software delivery, we can focus on what we care about most—continuously delighting our users.
• #20: The industry standard today is to use Virtual Machines (VMs) to run software applications. VMs run applications inside a guest Operating System, which runs on virtual hardware powered by the server’s host OS. VMs are great at providing full process isolation for applications: there are very few ways a problem in the host operating system can affect the software running in the guest operating system, and vice-versa. But this isolation comes at great cost — the computational overhead spent virtualizing hardware for a guest OS to use is substantial. Containers take a different approach: by leveraging the low-level mechanics of the host operating system, containers provide most of the isolation of virtual machines at a fraction of the computing power. VIDEO FOR CLASS -- https://www.youtube.com/watch?v=RyxXe5mbzlU https://www.youtube.com/watch?v=IEGPzmxyIpo First 3 minutes approx. of this video https://www.youtube.com/watch?v=YFl2mCHdv24 -- for docker introduction
• #22: Devops is useful for startups as well as bigger companies and teams Devops is not replacing Agile but extending and complementing Agile ITIL, formally an acronym for Information Technology Infrastructure Library, is a set of detailed practices for IT service management (ITSM) that focuses on aligning IT services with the needs of business. DevOps in fact strengthens IT practices DevOps is extending practices related to Information security and needed compliance DevOps does not mean that we do not need Ops team/guys ----- https://devops.com/noops-devops-disaster-waiting-happen/ Infrastructure as Code (IAC) is a type of ITinfrastructure that operations teams can automatically manage and provision through code, rather than using a manual process. DevOps is not just writing code to provision your environments – it is much bigger – longer pipeline and a chain of events tying everyone together DevOps uses variety of tools – may be open source or paid / may have multiple flavours / context and uses as per your need you need to find the best fits