2. DevOps
• DevOps is a mindset, a culture, and a set of
technical practices. It provides
communication, integration, automation, and
close cooperation among all the people
needed to plan, develop, test, deploy, release,
and maintain a Solution.
3. The Goal of DevOps
• From planning through delivery, the goal of
DevOps is to improve collaboration between
Development and IT Operations by developing
and automating a continuous delivery pipeline. In
doing so, DevOps: Increases the frequency and
quality of deployments Improves innovation and
risk taking by making it safer to experiment
Realizes faster time to market Improves solution
quality and shortens the lead time for fixes
Reduces the severity and frequency of release
failures Improves the Mean Time to Recovery
(MTTR)
4. Shared Responsibility
• Collaboration and organization – DevOps relies on the ability of Agile
Teams and IT Operations teams to collaborate effectively in an ongoing
manner, ensuring that solutions are developed and delivered faster and
more reliably. This is implemented, in part, by including operations
personnel and capabilities on every ART.
• Risk tolerance – DevOps requires a tolerance for failure and rapid
recovery, and rewards risk taking.
• Self-service infrastructures – Infrastructure empowers development and
operations to act independently without blocking each other.
• Knowledge sharing – Sharing discoveries, practices, tools, and learning
across silos is encouraged.
• “Automate everything” mindset – DevOps relies heavily on automation to
provide speed, consistency, and repeatable processes and environment
creation, as we describe below.
5.
6. Continuous Delivery Pipe line
• Application Lifecycle Management – Application and Agile Lifecycle Management tools (ALM)
create a standardized environment for communication and collaboration between software
development teams and related groups. (CA Agile Central, Version One, Agile Craft, tools for Model-
Based Systems Engineering)
• Artifact Management Repository – These tools provide a software repository for storing and
versioning binary files and their associated metadata (Artifactory, Archiva and JFrog).
• Build – Build automation is used to script or automate the process of compiling computer source
code into binary code (ANT, Maven, Bamboo, Jenkins).
• Testing – Automated testing tools include unit and acceptance testing, performance testing, load
testing, and many more (JUnit, NUnit, Maven, Cucumber, FitNesse).
• Continuous Integration (CI) – CI tools automate the process of compiling code into a build after
developers have checked their code into a central repository. After the CI server builds the system,
it runs unit and integration tests, reports results, and typically releases a labeled version of
deployable artifacts (Cruisecontrol, Jenkins, Continuum).
• Continuous Deployment – Deployment tools automate application deployments through to the
various environments. They facilitate rapid feedback and Continuous Delivery while providing the
required audit trails, versioning, and approval tracking (Capistrano, UrbanCode, Ansible, Puppet).
• Additional tools – There are numerous other important DevOps support tools: configuration,
logging, management and monitoring, provisioning, source code control, security, code review, and
collaboration.
