Unit – 9 DevOps

1. What is devOps ? What are the DevOps principles & best practices? (7
Marks , s-2021)
Ans.
• The word DevOps is the mixture of two words Dev (it represents Software
Development) and Ops (Itrepresents IT Operations e.g. Application and infrastructure
planning, Automation implementation, incident response, and incident management,
etc.)

• DevOps is a group of practices & principals that perfectly blends software development
(Dev) and IT operations (Ops).

• The main aim of DevOps is to provide continuous & high-quality delivery of the
software by making shortening SDLC (Software Development Life Cycle)

• DevOps bridges the gap between the operation team & development team, which
generally used to work in isolation with another.

• Principles :

DevOps principles guide how to organize a DevOps

environment.

o Incremental Releases

o Automation

o DevOps Pipeline

o Continuous Integration

o Continuous Delivery

o Continuous Monitoring

o Feedback Sharing

o Version Control

o Collaboration

• Practices :
 o Process automation

o Continuous Integration (CI)

o Continuous Delivery (CD)

o Continuous Deployment

o Infrastructure as code

o Microservices

o Configuration management and many more.

2. Explain DevOps Life Cycle. ( 7 Marks , w-2021)

Ans.
1. Continuous Development

• Planning and Coding of the software are involved in this initial phase.
• During the planning phase, the vision of the project and scope is decided.
• After the planning, developers used to begin coding the application.
• For the planning no DevOps tools available, but many tools available to maintain
the code.

2. Continuous Integration

• This is the main stage of the DevOps lifecycle.

• Developers should commit the changes to the source code more frequently as a
software development practice. This should be on daily and weekly basis.
• Next step is to build the every commit, this is used for early detection of problems
if they are present. Building the code involves not the compilation, but also includes
unit testing, integration testing, code review, and packaging.
• The new functionality is continuously integrated with the existing code. So, there is
continuous development of software. The newly written code needs to be integrated
continuously and smoothly with the systems to reflect changes to the end-users.
• Jenkins is a famous tool used for continuous integration. Once the change in the Git
repository is ready, then Jenkins fetches the committed code and prepares a build
of that code. Then this build is given to the test server or the production server.

3. Continuous Testing
 • In this phase, software continuously testing for bugs. The tools like TestNG, JUnit,
Selenium etc are used for the constant testing.
• This phase, where the developed software is continuously testing for bugs. For
constant testing, automation testing tools such as TestNG, JUnit, Selenium, etc are
used.
• These testing tools allow QAs to test multiple code-bases in parallel to ensure that
there is no flaw in the functionality. Docker Containers can be used for simulating
the test environment.
• Replacing manually testing to Automation testing saves a lot of time and effort for
executing the tests. The code is continuously integrated with the existing code, after
the testing.

4. Continuous Monitoring

• Monitoring is the phase where important information about the use of software is
recorded and processed to identify the problem areas. Monitoring is integrated with
the operational capabilities of the software application. The system errors such as
server not reachable, low memory, etc are resolved in this phase. It maintains the
security and availability of the service.

5. Continuous Feedback

• By analyzing the results from the operations of the software, one can improve the
application development.
• This can be achieved by constant feedback among the development and the
operations of the next version of the current software applications.

6. Continuous Deployment

• This phase deploys the code to the production servers.

• This is essential to ensure that the code is correctly working on the production
servers and real environments. The new code should be deployed continuously.
• The new code is deployed continuously, and configuration management tools play
an essential role in executing tasks frequently and quickly. Here are some popular
tools which are used in this phase, such as Chef, Puppet, Ansible, and SaltStack.

7. Continuous Operations

• All the operations in DevOps are based on the continuity with complete automation
of the release process. It allow the organization to accelerate the overall time to
market.
• It is clear that continuity is the critical factor in the DevOps in removing steps that
often distract the development, take it longer to detect issues and produce a better
version of the product after several months. With DevOps, we can make any
software product more efficient and increase the overall count of interested
customers in your product.
 3. What are the fundamental differences between DevOps & Agile
Development ? (4 Marks , w-2021)
Ans.

AGILE DevOps

The core activities under the Agile practice of The core activities under the DevOps are
software development are the Requirement phase/ process/ Requirement/ Design/ Engineering/
Design phase/ Development phase/ Test phase/ Construction/ Testing/ Debugging/
Debugging phase/ Maintenance phase. Deployment and Maintenance.

Tools for Agile are Compiler/ Debugger/ Profiler/ Tools for DevOps are Compiler/ Debugger/
GUI designer/ Modelling/ IDE/ Build Automation/ Profiler/ GUI designer/ Modelling/ IDE/ Build
Release Automation/ Infrastructure as code/ Automation/ Release Automation/
Testing. Infrastructure as code/ Testing.

BABOK, PMBOK, CMMI are some of the BABOK, CMMI, IEEE standards, ISO 9001,
standards and bodies of knowledge. ISO and ITIL, are some of the standards and
bodies of knowledge.

4. What is DevOps ? (4 Marks , w-2020)

Ans. Refer Que. 1

5. What are the challenges with DevOps implementation ? (4 Marks , w-

2020)

Ans.

Few Critical DevOps Implementation Challenges

DevOps is still thriving because of its implementation that helps in faster cloud development.
It’s more about how the team adopts the culture, rather than referring to the specific roles. Let’s
have a glance at top 5 DevOps challenges.
1. Achieving the Shared Goal of Dev and Op:
DevOps denotes the close relationship between development and operation teams.
However, both teams have their own goals and challenges. Since both works on Silos,
it creates a gap between both teams.
2. Moving away from Legacy System:
 Older applications and infrastructure can be a knotty even they have served for the
years. The lack of support and being not innovative can be challenging in offering
customers’ need.
3. Struggling in Adopting Change:
DevOps practices cannot be implemented overnight. It’s a continuous and smooth
process. It should be an evolution of the existing development practices instead of a
new revolution.
4. Define the Processes:
It seems that new tools of DevOps solve all the problems. However, they should be
integrated correctly, and people should be trained enough. If the correct structure is in
place, the team will follow the processes.
5. High Learning Curve of Tools:
DevOps has introduced the concepts of continuous development, deployment and
reporting. Wide set of tools requires significant training to team and implementation.