Ansible

Venkat Gurumoorthi
 Agenda – Day 1
• Introduction
• Waterfall vs Agile
• Introduction to DevOps
• Agile mindset
 Agenda – Day 2
• Introduction to Ansible
• Setting up the Ansible Environment
 Agenda – Day 3
• Ad hoc commads
• Playbooks
 Agenda – Day 4
• Roles and includes
• Inventories
 Agenda – Day 5
• Provisioning
• Deployment
 Introduction
• Name: Venkateswaran Gurumoorthi
• Qualification: MBA
• Technology: WebLogic, WebSpehere Admin
and DevOps Engineer
• Years of experience in DXC: 12
• Total years of experience: 15
• Reach me out: 753891 /
vgurumoorthi@csc.com
 Lean
• https://www.youtube.com/watch?v=RRy_73iv
cms
• https://www.youtube.com/watch?v=lmqtsU_
5_Lg
Waterfall
Triple constraints
Service / Operations
Agile
Benefits of Agile
Agile Values and Principles
Agile Principles
What does it mean to be Agile?

Principles behind the Agile

Manifesto
1. Our highest priority is to satisfy the customer through early and continuous delivery
of valuable software.

2. Welcome changing requirements, even late in development. Agile processes harness

change for the customer's competitive advantage.

3. Deliver working software frequently, from a couple of weeks to a couple of months,

with a preference to the shorter timescale.

4. Business people and developers must work together daily throughout the project.

5. Build projects around motivated individuals. Give them the environment and support
they need, and trust them to get the job done.

6. The most efficient and effective method of conveying information to and within a
development team is face-to-face conversation.
What does it mean to be Agile?

Principles behind the Agile

Manifesto (continued)
7. Working software is the primary measure of progress.
8. Agile processes promote sustainable development. The sponsors,
developers, and users should be able to maintain a constant pace
indefinitely.
9. Continuous attention to technical excellence and good design enhances
agility.
10. Simplicity--the art of maximizing the amount of work not done--is essential.
11. The best architectures, requirements, and designs emerge from self-
organizing teams.
12. At regular intervals, the team reflects on how to become more effective,
then tunes and adjusts its behavior accordingly.
Waterfall vs Agile
Planned Process Control
Empirical Process Control
Agile Umbrella
 DevOps
• Introduction to DevOps

• DevOps capabilities

• Adopting DevOps
 Introduction to DevOps
• Understanding the business need for DevOps
– Systems of Record
– Systems of Engagement

• Recognizing the business value of DevOps

– Enhanced customer experience
– Increased capacity to Innovate
– Faster Time to Value

• How DevOps works

– Develop and test against product like systems
– Deploy with repeatable, reliable processes
– Monitor and validate operational quality
– Amplify feedback loops
Develop and test against production
like systems
DevOps capabilities
 What is DevOps?
▪ DevOps is an enterprise capability for Continuous Software Delivery
▪ DevOps is an integrated coupling of Process, Infrastructure, and Product
▪ DevOps is the productive intersection of Cross Team Cooperation

DEVOPS emphasizes:
• Flexibility
• Agility
• Automation
• Collaboration
• Communication
• Cross-team cooperation
• Ownership

The walls separating development, QA, and production are barriers to agility. DevOps
breaks down these walls. DevOps is a new culture and process where Development,
QA, and Operations work together to expedite development and problem resolution.
CSC Proprietary and Confidential 27
CSC Proprietary and Confidential 28
Agile Accelerating Development

Scope of Agile Methods

CSC Proprietary and Confidential 29

Agile Fixes Only Part of the Story

Still a problem

CSC Proprietary and Confidential 30

Our Value Chain Is Long and Full of Friction

CSC Proprietary and Confidential 31

Why DevOps?
Drivers
• Reduced deployment and operational
outage times
• Reduction of human-in-the-loop errors
• Pressure to deliver higher quality
applications faster
CSC Proprietary and Confidential
Benefits
• Expedited deployment process using
increased automation (i.e. deployment,
configuration, testing (less time, less
manual effort))
• Increased collaboration among
departments (i.e. Dev, QA, Operations)
• Improvement in quality of applications
deployed, time-to-market speed
• Reduction in spend on deployment
operations caused by human-in-the-
loop
• Reduced IT cycle time
32
DevOps

Continuous Delivery

Continuous Continuous Continuous

DEV Integration Testing Deployment OPS

Continuous Provisioning

Renewal of the relationship, processes and governance models between development (Dev) and IT
Operations (Ops) stressing communication, collaboration, transparency and automation with a view
to more rapidly deploying high quality application releases

CSC Proprietary and Confidential 33

 How DevOps works
• Develop and test against production like
systems
• Deploy with repeatable, reliable processes
• Monitor and validate operational quality
• Amplify feedback loops
DevOps Capabilities
 Paths to DevOps adoption
• Develop and test
– Collaborative development
– Continuous testing

• Release and Deploy

• Monitor and optimize

– Continuous monitoring
– Continuous customer feedback and optimization
 Plan and measure
• Continuous business planning
– To be agile and react quickly to customer
feedback
– Lean thinking techniques
• Starting small
• Eliminate waste
 Develop and test
• Collaborative Development
• Continuous testing
 Monitor and Optimize
• Continuous Monitoring
• Continuous customer feedback and
optimization
Continuous Delivery
 Adopting DevOps
• People
– Culture
• Identifying business objectives
• Environment of sharing
• DevOps teams
• Process
– Business process
– Change Management process
– DevOps practices
• Technology
– Infrastructure as a code
– Delivery pipeline
– Deployment automation and release management
Delivery Pipeline