Scribd
Upload
8 views12 pages

Dev Ops

DevOps is a methodology that combines agile practices with collaboration between development and operations teams to enhance software development and deployment processes. It aims to improve deployment frequency, reduce failure rates, and shorten recovery times through various maturity phases, including continuous integration and continuous delivery. Key tools used in DevOps include Jenkins, Docker, and Ansible, and roles within DevOps encompass various positions such as release managers and automation architects.

Uploaded by

Ameer hamza khan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
8 views12 pages

Dev Ops

DevOps is a methodology that combines agile practices with collaboration between development and operations teams to enhance software development and deployment processes. It aims to improve deployment frequency, reduce failure rates, and shorten recovery times through various maturity phases, including continuous integration and continuous delivery. Key tools used in DevOps include Jenkins, Docker, and Ansible, and roles within DevOps encompass various positions such as release managers and automation architects.

Uploaded by

Ameer hamza khan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 12

Topic: DevOps

Group Members:
Fazal Azeem
Malaika Taqveem
Danyal Khan
Irfan Shah
1. Muhammad Ikram
DEVOPS
Definition of DevOps
• DevOps is a new term emerging from the collision of
two major related trends. The first was also called
“agile infrastructure” or “agile operations” it sprang
from applying Agile and Lean approaches to
operations work.
• The second is a much expanded understanding of the
value of collaboration between development and
operations staff throughout all stages of the
development lifecycle when creating and operating
a service, and how important operations has become in
our increasingly service-oriented world.
What Are the Challenges DevOps
Solves?
• Prior to DevOps application development, teams were
in charge of gathering business requirements for a
software program and writing code.
• Then a separate QA team tests the program in an
isolated development environment, if requirements
were met, and releases the code for operations to
deploy.
• The deployment teams are further fragmented into
siloed groups like networking and database. Each time
a software program is “thrown over the wall” to an
independent team it adds bottlenecks.
What Is the Goal of DevOps?

• Improve deployment frequency


• Achieve faster time to market
• Lower failure rate of new releases
• Shorten lead time between fixes
• Improve mean time to recovery
DevOps Tools

• Nagios
• Monit
• Puppet
• Jenkins
• Docker
• Ansible
• Chef
Phases of DevOps Maturity
1.Waterfall Development
Before continuous integration, development teams
would write a bunch of code for three to four months.
Then those teams would merge their code in order to
release it. The different versions of code would be so
different and have so many changes that the actual
integration step could take months. This process was
very unproductive.
2.Continuous Integration
• It is the practice of quickly integrating newly
developed code with the main body of code that is to
be released. Continuous integration saves a lot of
time when the team is ready to release the code.
• DevOps didn’t come up with this term. It is an agile
engineering practice originating from the Extreme
Programming methodology.
• The terms been around for a while, but DevOps has
adopted this term because automation is required to
successfully execute continuous integration.
Continuous integration is often the first step down
the path toward DevOps maturity.
3. Continuous Delivery
• It is an extension of continuous integration
[DevOps stage 2]. It sits on top of continuous
integration.
• When executing continuous delivery, you add
additional automation and testing so that you
don’t just merge the code with the main code line
frequently, but you get the code nearly ready to
deploy with almost no human intervention.
• It’s the practice of having the code base
continuously in a ready-to-deploy state.
4. Continuous Deployment
• It not to be confused with continuous delivery
[DevOps nirvana], is the most advanced evolution of
continuous delivery.
• It’s the practice of deploying all the way into
production without any human intervention.
An agile approach
• People: teammates, customers, and interactions
between these people – instead of processes and tools
• Immediacy: Working software – instead of
comprehensive documentation
• Flexibility: Responding to, and even embracing,
change – instead of following a predetermined plan
Rolls of Devops
• The DevOps evangelist
• The release manager
• The automation architect
• The software developer/tester
• The experience assurance (XA) professional
• The security engineer
• The utility technology player

You might also like