22CS910 DEVOPS

UNIT 1

D.M.KALAI SELVI AP R.M.D ENGINEERING COLLEGE 1

 OPERATION METHODOLOGIES -
ITIL
• ITIL, or Information Technology Infrastructure Library, is a
comprehensive framework that helps organizations manage their
IT services effectively.
• ITIL provides a defined approach to IT service management,
offering guidelines, best practices, and processes to ensure that
IT services align with the needs and goals of the business.
• Popular IT services covered by ITIL are Cloud services, backup,
network security, Data processing and storage, managed
print services, IT consulting, Help desk support, IOT etc.
D.M.KALAI SELVI AP R.M.D ENGINEERING COLLEGE 2
 ITIL PROCESS
• The ITIL Framework process contains the following
stages:
1. Service Strategy
2. Service Design
3. Service Transitions
4. Service Operations
5. Continual Service Improvement.

D.M.KALAI SELVI AP R.M.D ENGINEERING COLLEGE 3

D.M.KALAI SELVI AP R.M.D ENGINEERING COLLEGE 4
D.M.KALAI SELVI AP R.M.D ENGINEERING COLLEGE 5
 SERVICE STRATEGY
• Service Strategy Operations ensure that services such as
fulfilling user requests, working on service failures, fixing
problems and carrying out routine operational tasks
efficiently and effectively.
• Finance management
• The Financial Management services provides a means of
understanding and controlling costs and opportunities
associated with services.
D.M.KALAI SELVI AP R.M.D ENGINEERING COLLEGE 6
 SERVICE STRATEGY
• Service Portfolio Management
• Service Portfolio Management helps you to organizes the
process by which services are identified, evaluated,
selected, and chartered.
• Demand Management
• The Demand Management is concerned with
understanding and influencing customer demand. It also
involves User Profiles, which characterize various groups
of users for a given service.
D.M.KALAI SELVI AP R.M.D ENGINEERING COLLEGE 7
 Service Design

• This stage ensures agreed service are delivered when,

where, and at the defined cost.
• Service Level Management
• Service Level Management is deals with securing and
managing agreements between customers and the service
provider irrespective of the level of performance and
reliability associated with specific services.

D.M.KALAI SELVI AP R.M.D ENGINEERING COLLEGE 8

Service Level Management
• Availability Management
• Availability Management service is concerned with the agreed-upon availability
requirements as established in Service Level Agreements (SLA).
• Capacity Management
• Capacity Management is focused with ensuring that at all times, the cost-effective
capacity exists that meets or exceeds the demands of the business as established in
Service Level Agreements
• IT Service Continuity Management
• IT Service Continuity Management (ITSCM) process ensures that the service provider
provides the minimum agreed-upon levels of service. It uses techniques like Business
Impact Analysis (BIA) and Management of Risk (MOR).
• Service Catalog Management
• The Service Catalog is a subset which contains services available to customers and
users.
D.M.KALAI SELVI AP R.M.D ENGINEERING COLLEGE 9
 Service Transitions

• The goal of the Service Transition process is to build and deploy IT

services. It also make sure that changes to services and Service
Management ITIL processes are conducted in a coordinated way.
• Change Management
• Change management activity controls the lifecycle of all the changes
with minimum disruption to IT services.
• Service Asset and Configuration Management
• The goal of this service is to maintain information about configuration
items needed to deliver an IT service, including their relationships.
D.M.KALAI SELVI AP R.M.D ENGINEERING COLLEGE 10
• Release and Deployment Management
• This process helps you to plan, schedule, and control the movement of releases to
conduct testing to live environments. It also ensures that the integrity of the live
environment is protected and the correct components are released.
• Transition Planning and Support
• This ITIL process mainly focuses on planning and coordinating the use of resources to
deploy a major release within the expected cost, time and quality.
• Service Validation and Testing
• This process helps to deployed releases and the resulting services able to meet
expectations of the customer.
• Evaluation
• Evaluation process helps you to assess major changes, like the introduction of a new
service or a significant change to an existing service
• Knowledge Management
• The objective of knowledge management service is to gather, analyze, store, and
share knowledge and information within an organization. It helps improving efficiency
D.M.KALAI SELVI AP R.M.D ENGINEERING COLLEGE 11
by reducing the need to rediscover knowledge.
Service Operations
This ITIL stage focuses on meeting end-users’ expectations while balancing costs and
discovering any potential problems.
Service Desk
It is the main point of contact between users and the service provider. A service desk
handles communication with the users and also manages incidents and service requests.
Incident Management
The objective of Incident Management is to manage the lifecycle of all incidents. It also
makes sure that services are returning back to the IT service to users as fast as possible.
Problem Management
The objective of problem management is to manage the lifecycle of all problems. It helps
IT organization to prevent incidents from happening and minimize the impact of incidents
which cannot be prevented.
Event Management
The object of event management is to make sure configuration items and services are
continually monitored and to filter and categorize events to determine the specific actions.
D.M.KALAI SELVI AP R.M.D ENGINEERING COLLEGE 12
Request Fulfilment
The objective of request management is to fulfil service requests. In many cases, they
are minor changes (for example, requests for changing a password).
Technical Management
This function offers technical expertise and support for the management of the IT
infrastructure.
Application Management:
Application Management is a service that is responsible for managing applications
throughout their lifecycle.
IT Service Operations
The goal is to maintain information about configuration items needed to deliver an IT
service operations, including their relationships.
Continual Service Improvement
D.M.KALAI SELVI AP R.M.D ENGINEERING COLLEGE 13

It makes sure that IT services can recover and continue from a service incident. It
helps to conduct business simper analysis to prioritize business recovery.
 COBIT
• COBIT stands for “Control Objectives for Information
and Related Technology”
• It is a set of guidance materials for IT governance to
manage their requirements, technical issues, and business
risks.
• COBIT connects IT initiatives with business requirements,
monitors and improves IT management practices, and
ensures quality control and reliability of information
systems
D.M.KALAI inENGINEERING
SELVI AP R.M.D an organization.
COLLEGE 14
 Core Components of COBIT

• Control Objectives: Define specific IT goals and the means to

achieve them.
• Maturity Models: Help organizations assess the maturity of
their IT processes.
• Management Guidelines: Guide best practices for IT
management.
• Process Descriptions and Framework: Offer detailed
descriptions of IT processes and a structured framework for
implementation.
D.M.KALAI SELVI AP R.M.D ENGINEERING COLLEGE 15
 COBIT Domains

• COBIT defines IT activities in a generic process model within four domains:

• Plan and Organize: This domain addresses direction to solutions, Information
architecture, managing IT investments, assessing the risks, quality, and project.
• Acquire and Implement: This domain acquires and maintains application software
and technology infrastructure, develops as well as maintains procedures and manages
changes, implements desired solutions, and passes them to be turned into services.
• Deliver and Support: This domain defines and manages service levels, ensures the
security of the system, educates or trains, and advises users. It receives solutions and
makes them usable for end users.
• Monitor and Evaluate: This domain monitors the process, assesses internal control
capability, finds independent assurance, and provides independent audits.

D.M.KALAI SELVI AP R.M.D ENGINEERING COLLEGE 16

D.M.KALAI SELVI AP R.M.D ENGINEERING COLLEGE 17
 Principle of COBIT

• Facilitating a Holistic Approach: For thorough supervision, integrate IT

governance with risk management, compliance, and broader organizational
governance.
• Distinguishing Governance from Management: Clearly define the roles and
duties that fall into the domains of management (achieving of goals and execution)
and governance (achievement of objectives and monitoring).
• Putting Process Orientation First: To create distinct roles, workflows, and
methods for ongoing improvement, group IT operations into interrelated processes.
• Offering a Balanced Perspective on Governance: For efficient decision-making,
consider multiple aspects of IT governance, such as stakeholder needs, strategy
alignment, risk management, resource optimization, performance assessment, and
compliance
D.M.KALAI SELVI AP R.M.D ENGINEERING COLLEGE 18
D.M.KALAI SELVI AP R.M.D ENGINEERING COLLEGE 19
 KANBAN
• Kanban methodology is a software development process
within the agile framework that focuses on limiting
the amount of work-in-progress (WIP) at any given
time.
• Kanban is a visual work management system that provides
a clear representation of work progression within a
process.
• The primary aim of Kanban is to pinpoint any possible
obstructions in your process and resolve them, enabling 20
D.M.KALAI SELVI AP R.M.D ENGINEERING COLLEGE

work to move efficiently at an optimal pace, thus ensuring

cost-effectiveness.
D.M.KALAI SELVI AP R.M.D ENGINEERING COLLEGE 21
 Kanban Principles & Practices

1. Start with what you are doing now

2. Agree to pursue incremental, evolutionary change
3. Initially, respect current roles, responsibilities and job-
titles
4. Encourage acts of leadership at all levels

D.M.KALAI SELVI AP R.M.D ENGINEERING COLLEGE 22

1. Start with what you are doing now
The Kanban Method strongly emphasizes not making any change to your existing
setup/ process right away. Kanban must be applied directly to current workflow.
2. Agree to pursue incremental, evolutionary change
Kanban encourages you to make small incremental changes rather than making
radical changes that might lead to resistance within the team and organization.
3. Initially, respect current roles, responsibilities and job-titles
Unlike other methods, Kanban does not impose any organizational changes by
itself. So, it is not necessary to make changes to your existing roles and functions
which may be performing well.
4. Encourage acts of leadership at all levels
Kanban encourages continuous improvement at all the levels of the organization
D.M.KALAI SELVI AP R.M.D ENGINEERING COLLEGE 23

and it says that leadership acts don’t have to originate from senior managers only.
 6 Core Practices of the Kanban
Method:
1. Visualize the flow of work
2. Limit WIP (Work in Progress)
3. Manage Flow
4. Make Process Policies Explicit
5. Implement Feedback Loops
6. Improve Collaboratively, Evolve Experimentally

D.M.KALAI SELVI AP R.M.D ENGINEERING COLLEGE 24

 1. Visualize the flow of work

• You need to visualize – either on a physical board or an

electronic Kanban Board, the process steps that you
currently use to deliver your work or your services.
• Depending on the complexity of your process and your
work-mix (the different types of work items that you work
on and deliver), your Kanban board can be very simple to
very elaborate. Once you visualize your process, then you
can visualize the current work that you and your team are
doing.
D.M.KALAI SELVI AP R.M.D ENGINEERING COLLEGE 25
 2. Limit WIP (Work in Progress)

• Limiting work-in-progress (WIP) is fundamental to implementing Kanban – a ‘Pull-

system’. By limiting WIP, you encourage your team to complete work at hand first
before taking up new work. Thus, work currently in progress must be completed and
marked done..
• Once you have sufficient data, define WIP limits for each stage of the workflow
(each column of your Kanban board) as being equal to half the average WIP. Typically,
many teams start with a WIP Limit of 1 to 1.5 times the number of people working
in a specific stage.
• Limiting WIP and putting the WIP limits on each column of the board not only helps the
team members first finish what they are doing before taking up new stuff – but also
communicates to the customer and other stakeholders that there is limited
capacity to do work for any team – and they need to plan carefully what work they
ask the team to do.
D.M.KALAI SELVI AP R.M.D ENGINEERING COLLEGE 26
 3.MANAGE FLOW
• A Kanban system helps you manage flow by highlighting the
various stages of the workflow and the status of work in each
stage.
• Depending on how well the workflow is defined and WIP Limits are
set, you will observe either a smooth flow within WIP limits or work
piling up as something gets held up and starts to hold up capacity.
• All of this affects how quickly work traverses from start to the end of
the workflow (some people call it value stream). Kanban helps your
team analyze the system and make adjustments to improve flow so as
to reduce the time it takes to complete each piece of work.
D.M.KALAI SELVI AP R.M.D ENGINEERING COLLEGE 27
 4. Make Process Policies Explicit

• As part of visualizing your process, it makes sense to also

define and visualize explicitly, your policies (process rules
or guidelines) for how you do the work you do. By
formulating explicit process guidelines, you create a
common basis for all participants to understand how to do
any type of work in the system.
• examples of explicit policies include the definition of when
a task is completed, the description of individual lanes or
columns, who pulls when, etc.
D.M.KALAI SELVI AP R.M.D ENGINEERING COLLEGE 28
 5. Implement Feedback Loops

• The Kanban Method encourages and helps you implement

feedback loops of various kinds – review stages in your
Kanban board workflow, metrics and reports and a range
of visual cues that provide you continuous feedback on
work progress – or the lack of it – in your system.

D.M.KALAI SELVI AP R.M.D ENGINEERING COLLEGE 29

 6. Improve Collaboratively, Evolve Experimentally

• The Kanban Method is an evolutionary improvement

process. It helps you adopt small changes and improve
gradually at a pace and size that your team can handle
easily.
• It encourages the use of the scientific method – you form
a hypothesis, you test it and you make changes
depending on the outcome of your test.
• As a team implementing Lean/ Agile principles, your key
task is to evaluate your process constantly and improve
D.M.KALAI SELVI AP R.M.D ENGINEERING COLLEGE 30

continuously as needed and as possible.

 CLASSIC KANBAN BOARDS

D.M.KALAI SELVI AP R.M.D ENGINEERING COLLEGE 31

 KANBAN CARDS

D.M.KALAI SELVI AP R.M.D ENGINEERING COLLEGE 32

 Kanban WIP Limits

D.M.KALAI SELVI AP R.M.D ENGINEERING COLLEGE 33

 SCRUM VS KANBAN
D.M.KALAI SELVI AP R.M.D ENGINEERING COLLEGE 34
 Scrum
• Scrum is a structured Agile framework that divides work into
fixed time periods known as sprints.
• Each sprint typically lasts two to four weeks and involves a
defined set of work items. Scrum teams hold regular planning
and review meetings and daily stand-ups to manage their work.
• Scrum emphasizes teamwork, with roles like Product Owner,
Scrum Master, and Development Team members. It offers
predictability and a sense of urgency, making it ideal for
projects with well-defined requirements and stable workloads.
D.M.KALAI SELVI AP R.M.D ENGINEERING COLLEGE 35
 KANBAN
• Kanban is a more flexible framework designed for visualizing and
continuously improving workflow.
• Instead of time-boxed sprints, Kanban focuses on a continuous flow of
work items through stages.
• Work is pulled when there is capacity, allowing for variability in work
item sizes and priorities. Kanban boards are used to track work items’
progress.
• With its adaptability and a “pull” approach, Kanban is excellent for
teams with variable workloads, frequent changes, and a desire to
optimize workflow without drastic process changes
D.M.KALAI SELVI AP R.M.D ENGINEERING COLLEGE 36
 DEVOPS OVERVIEW

DevOps is a culture that promotes the collaboration What is DevOps?

between Development and Operations team

This allows a single team to handle the entire application Dev & Test IT Operations

lifecycle, from development to testing, deployment,

and operations

Approach that combines, automate and streamline

the IT methodology of Delivery.
Automatio Culture
n
 DevOps Architecture
• DevOps architecture is used for the applications hosted on the cloud platform and
large distributed applications.

• Agile Development is used in the DevOps architecture so that integration and delivery can
be contiguous.

• When the development and operations team works separately from each other, then it is
time-consuming to design, test, and deploy.

• And if the terms are not in sync with each other, then it may cause a delay in the delivery.

• So DevOps enables the teams to change their shortcomings and increases

productivity.
DevOps Components
1. BUILD

• Without DevOps, the cost of the consumption of the

resources was evaluated based on the pre-defined
individual usage with fixed hardware allocation.
• And with DevOps, the usage of cloud, sharing of
resources comes into the picture, and the build is
dependent upon the user's need, which is a mechanism
to control the usage of resources or capacity.
 2.CODE

• Many good practices such as Git enables the code to be

used, which ensures writing the code for business, helps
to track changes, getting notified about the reason
behind the difference in the actual and the expected
output, and if necessary reverting to the original code
developed.
• The code can be appropriately arranged in files, folders,
etc. And they can be reused.
3.TEST

• The application will be ready for production after

testing. In the case of manual testing, it consumes more
time in testing and moving the code to the output.
• The testing can be automated, which decreases the
time for testing so that the time to deploy the code to
production can be reduced as automating the running of
the scripts will remove many manual steps.
4.PLAN

• DevOps use Agile methodology to plan the

development.
• With the operations and development team in sync, it
helps in organizing the work to plan accordingly to
increase productivity.
5.MONITOR

• Continuous monitoring is used to identify any risk of

failure.
• Also, it helps in tracking the system accurately so that
the health of the application can be checked.
• The monitoring becomes more comfortable with
services where the log data may get monitored through
many third-party tools such as Splunk.
6.DEPLOY

• Many systems can support the scheduler for automated

deployment.
• The cloud management platform enables users to
capture accurate insights and view the optimization
scenario, analytics on trends by the deployment of
dashboards.
7.OPERATE

• DevOps changes the way traditional approach of

developing and testing separately.
• The teams operate in a collaborative way where both
the teams actively participate throughout the service
lifecycle.
• The operation team interacts with developers, and they
come up with a monitoring plan which serves the IT and
business requirements.
8.RELEASE

• Deployment to an environment can be done by

automation.
• But when the deployment is made to the production
environment, it is done by manual triggering.
• Many processes involved in release management
commonly used to do the deployment in the production
environment manually to lessen the impact on the
customers.
 DevOps Principles
The main principles of DevOps are Continuous delivery,
automation, and fast reaction to the feedback.
• End to End Responsibility: DevOps team need to provide
performance support until they become the end of life. It
enhances the responsibility and the quality of the products
engineered.
• Continuous Improvement: DevOps culture focuses on
continuous improvement to minimize waste. It continuously
speeds up the growth of products or services offered.
• Automate Everything: Automation is an essential principle of
the DevOps process. This is for software development and also
for the entire infrastructure landscape.
 DevOps Principles
• Custom Centric Action: DevOps team must take
customer-centric for that they should continuously
invest in products and services.
• Monitor and test everything: The DevOps team
needs to have robust monitoring and testing
procedures.
• Work as one team: In the DevOps culture role of the
designers, developers, and testers are already defined.
All they needed to do is work as one team with
complete collaboration.
 DEVOPS LIFECYCLE

The 3 P's of DevOps

People - Fosters collaboration &

cultural shift
Processes - Streamlines workflow
and automate task
Products - Enable automation and
efficiency in pipeline
 DevOps Lifecycle

• DevOps defines an agile

relationship between
operations and
Development.
• It is a process that is practiced
by the development team
and operational engineers
together from beginning to the
final stage of the product.
• The DevOps lifecycle includes
seven phases
1.Continuous Development

• This phase involves the planning and coding of the

software.
• The vision of the project is decided during the planning
phase.
• And the developers begin developing the code for the
application.
• There are no DevOps tools that are required for
planning, but there are several tools for maintaining the
code.
2.Continuous Integration

• This stage is the heart of the entire DevOps lifecycle.

• It is a software development practice in which the developers require to
commit changes to the source code more frequently.
• This may be on a daily or weekly basis.
• Then every commit is built, and this allows early detection of problems if
they are present.
• Building code is not only involved compilation, but it also includes unit
testing, integration testing, code review, and packaging.
• The code supporting new functionality is continuously integrated with the
existing code.
• Therefore, there is continuous development of software.
• The updated code needs to be integrated continuously and smoothly with
the systems to reflect changes to the end-users.
2.Continuous Integration

• Jenkins is one of the popular

tool used in this phase.
• Whenever there is a change
in the Git repository, then
Jenkins fetches the updated
code and prepares a build of
that code, which is an
executable file in the form of
war or jar.
• Then this build is forwarded
to the test server or the
production server.
3.Continuous 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 tools allow QAs to test multiple code-bases thoroughly in
parallel to ensure that there is no flaw in the functionality.
• In this phase, Docker Containers can be used for simulating the
test environment.
• Selenium does the automation testing, and TestNG generates the
reports.
• This entire testing phase can automate with the help of a
Continuous Integration tool called Jenkins
4.Continuous Monitoring

• Monitoring is a phase that involves all the operational factors of the

entire DevOps process, where important information about the use of
the software is recorded and carefully processed to find out trends and
identify problem areas.
• Usually, the monitoring is integrated within the operational capabilities
of the software application.
• It may occur in the form of documentation files or maybe produce
large-scale data about the application parameters when it is in a
continuous use position.
• 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

• The application development is consistently improved by

analyzing the results from the operations of the software.
• This is carried out by placing the critical phase of constant
feedback between the operations and the development of
the next version of the current software application.
• The continuity is the essential factor in the DevOps as it
removes the unnecessary steps which are required to take a
software application from development, using it to find out
its issues and then producing a better version.
• It kills the efficiency that may be possible with the app and
reduce the number of interested customers.
6.Continuous Deployment

• In this phase, the code is deployed to the production

servers.
• Also, it is essential to ensure that the code is correctly
used on all the servers.
• 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.
6.Continuous Deployment

• Containerization tools are also playing an essential role in the

deployment phase.
• Docker is a popular tools that are used for this purpose. These tools help
to produce consistency across development, staging, testing, and
production environment.
• They also help in scaling up and scaling down instances softly.
• Containerization tools help to maintain consistency across the
environments where the application is tested, developed, and deployed.
• There is no chance of errors or failure in the production environment as
they package and replicate the same dependencies and packages used
in the testing, development, and staging environment.
• It makes the application easy to run on different computers.
7.Continuous Operations

• All DevOps operations are based on the continuity with

complete automation of the release process and allow the
organization to accelerate the overall time to market
continuingly.
• It is clear from the discussion 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.
 DEVOPS TOOLS

DevOps tools that helps to automate & manage the CI/CD process with Faster development
cycles, Reduced manual intervention
62
63
64
65
66
67
D.M.KALAI SELVI AP R.M.D ENGINEERING COLLEGE 69