Scene 1

Introduction to DevOps. Definition DevOps is a set of practices intended to reduce the time between committing a change to a system and the change being placed into normal production while ensuring high quality. Implications of this definition
- Practices and tools
- Do not restrict the scope of DevOps to testing and development. 

Scene 2

Definition DevOps is a set of practices intended to reduce the time between committing a change to a system and the change being placed into normal production while ensuring high quality.
 Implications of this definition
- Practices and tools
- Do not restrict the scope of DevOps to testing and development

Introduction to DevOps. Perspective involved. Business. 

Scene 3

Quality: Checklist Approval Release Note Audit Compliance

Benefits of working in a DevOps environment. Timelines. 

Scene 4

Benefits of working in a DevOps environment

Benefits of working in a DevOps environment. Imbalance. 

Scene 5

Product	• Feature A  Release	• Feature B

Benefits of working in a DevOps environment. Blame Game. 

Scene 6

Benefits of working in a DevOps environment. Where is Operations? Development is All Well (Waterfall, Agile) Where is Operations?. 

Scene 7

Where is Operations? Development is All Well (Waterfall, Agile) Where is Operations?

Benefits of working in a DevOps environment. History DevOps Back in 2007 Patrick Debois [Belgian Engineer] Initially it was Agile Infrastructure but later coined the phrase DevOps Velocity conference in 2008 And if you see you may come across more tangential DevOps Initiative WinOps DevSecOps BizDevOps. 

Scene 8

History DevOps Back in 2007 Patrick Debois [Belgian Engineer] Initially it was Agile Infrastructure but later coined the phrase DevOps Velocity conference in 2008 And if you see you may come across more tangential DevOps Initiative WinOps DevSecOps BizDevOps

Benefits of working in a DevOps environment. More Handshakes. 

Scene 9

Benefits of working in a DevOps environment. No More Handshakes. 

Scene 10

DevOps Lifecycle. DevOps lifecycle is a combination of different phases of continuous software development, integration, testing, deployment, and monitoring. A competent DevOps lifecycle is necessary to leverage the full benefits of the DevOps methodology.. 

Scene 11

DevOps lifecycle is a combination of different  phases of continuous software development,  integration, testing, deployment, and monitoring.  A competent DevOps lifecycle is necessary to  leverage the full benefits of the DevOps  methodology.

[image] Operation
Development
DEVOPS
LIFECYCLE
Deployment
Feedback
Integration
Testing
Monitoring

DevOps Lifecycle. Key Components. Continuous development Continuous integration Continuous testing Continuous deployment Continuous monitoring Continuous feedback Continuous operations. 

Scene 12

Continuous development  Continuous integration  Continuous testing  Continuous deployment  Continuous monitoring  Continuous feedback Continuous operations

DevOps Lifecycle. Continuous development. Continous Development The first phase where the planning & sotware development takes place. 

Scene 13

Continous Development
The first phase where the planning &
sotware development takes place

Continuous development involves planning and coding the software. Here, the entire development process gets broken down into smaller development cycles. This process makes it easier for the DevOps team to accelerate the overall software development process

DevOps Lifecycle. Continuous integration. Continuous integration (CI) includes different steps related to the execution of the test process. Along with this, clients also provide information to be incorporated for adding new features to the application. Most changes happen in the source code during this phase.. 

Scene 14

Continuous integration (CI) includes different steps related to the execution of the test process. Along with this, clients also provide information to be incorporated for adding new features to the application. Most changes happen in the source code during this phase.

Continous Integration
All new code that support add-on
functionalites are built & integrated
into the existing code

DevOps Lifecycle. Continuous testing. Continous Testing The developed functionality in continously tested for bugs,The test environments are simulated using docker container.. 

Scene 15

Continous Testing
The developed functionality in
continously tested for bugs,The
test environments are simulated
using docker container.

Next in the DevOps lifecycle is the testing phase, wherein the developed code is tested for bugs and errors that may have made their way into the code. This is where quality analysis (QA) plays a major role in checking the usability of the developed software.

DevOps Lifecycle. Continuous deployment. Continuous deployment (CD) ensures hassle-free product deployment without affecting the application’s performance. It is necessary to ensure that the code is deployed precisely on all available servers during this phase. This process eliminates the need for scheduled releases and accelerates the feedback mechanism, allowing developers to address issues more quickly and with greater accuracy.. 

Scene 16

Continuous deployment (CD) ensures hassle-free product deployment without affecting the application’s performance. It is necessary to ensure that the code is deployed precisely on all available servers during this phase. This process eliminates the need for scheduled releases and accelerates the feedback mechanism, allowing developers to address issues more quickly and with greater accuracy.

Continous Deployment
Finalized Application code is Deployed
to the production servers-The Consistency
in the application's performance &
Functional Conditions in established & curated

DevOps Lifecycle. Continuous monitoring. Continous Monitoring For Sustaining the availability of Services in the application.lt also helps in tracking any unusal system behaviour. 

Scene 17

Continous Monitoring
For Sustaining the availability of Services
in the application.lt also helps in tracking
any unusal system behaviour

Continuous monitoring is an operational phase where the objective is to enhance the overall efficiency of the software application. Moreover, it monitors the performance of the app as well. Therefore, it is one of the most crucial phases of the DevOps lifecycle.

DevOps Lifecycle. Continuous feedback. Continuous feedback is essential to ascertain and analyze the final outcome of the application. It sets the tone for improving the current version and releasing a new version based on stakeholder feedback.. 

Scene 18

Continuous feedback is essential to ascertain and analyze the final outcome of the application. It sets the tone for improving the current version and releasing a new version based on stakeholder feedback.

Continous Feedback
A Phase for accomodating the
feedback for Contionus improvement
in code ad also crucial phase for
releasing newer version of the software.

DevOps Lifecycle. Continuous operations. The shortest and least complex step of the DevOps life cycle. Continuous service has the aim of automating the process of launching an application and subsequent updates. Continuous operations provide shorter development times, enabling developers to continually improve the application’s time-to-market.. 

Scene 19

The shortest and least complex step of the DevOps life cycle. Continuous service has the aim of automating the process of launching an application and subsequent updates. Continuous operations provide shorter development times, enabling developers to continually improve the application’s time-to-market.

Continous Testing
Release process and allow the
organization to accelerate
the overall time to market
continuously.

Activity Time. The trainer will ask the participants to make groups and discuss on topic DevOps life cycle. 

Scene 20

The trainer will ask the participants to make  groups and discuss on topic DevOps life cycle

Senior female teacher in the classroom. vector illustration. Vector  illustration of a senior female teacher in the classroom. | CanStock

DevOps Stages. code Dev -sest Deploy Monitor. The Plan stage covers everything that happens before the developers start writing code, and it’s where a Product Manager or Project Manager earns their keep. Requirements and feedback are gathered from stakeholders and customers and used to build a product roadmap to guide future development.. 

Scene 21

The Plan stage covers everything that happens before the developers start writing code, and it’s where a Product Manager or Project Manager earns their keep.  Requirements and feedback are gathered from stakeholders and customers and used to build a product roadmap to guide future development.

DevOps Stages. code Dev -sest Deploy Monitor. In addition to the standard toolkit of a software developer, the team has a standard set of plugins installed in their development environments to aid the development process, help enforce consistent code-styling and avoid common security flaws and code anti-patterns.. 

Scene 22

In addition to the standard toolkit of a software developer, the team has a standard set of plugins installed in their development environments to aid the development process, help enforce consistent code-styling and avoid common security flaws and code anti-patterns.

DevOps Stages. code Dev -sest Deploy Monitor. Build. 

Scene 23

Once a developer has finished a task, they commit their code to a shared code repository. There are many ways this can be done, but typically the developer submits a pull request — a request to merge their new code with the shared codebase. Another developer then reviews the changes they’ve made, and once they’re happy there are no issues, they approve the pull request.

DevOps Stages. code Dev -sest Deploy Monitor. Test. 

Scene 24

Once a build succeeds, it is automatically deployed to a staging environment for deeper, out-of-band testing. The staging environment may be an existing hosting service, or it could be a new environment provisioned as part of the deployment process. This practice of automatically provisioning a new environment at the time of deployment is referred to as Infrastructure-as-Code (IaC) and is a core part of many DevOps pipelines

DevOps Stages. code Dev -sest Deploy Monitor. Release. 

Scene 25

The Release phase is a milestone in a DevOps pipeline — it’s the point at which we say a build is ready for deployment into the production environment. By this stage, each code change has passed a series of manual and automated tests, and the operations team can be confident that breaking issues and regressions are unlikely.

DevOps Stages. code Dev -sest Deploy Monitor. Deploy. 

Scene 26

Finally, a build is ready for the big time and it is released into production. There are several tools and processes that can automate the release process to make releases reliable with no outage window.

DevOps Stages. code Dev -sest Deploy Monitor. Operate. 

Scene 27

The new release is now live and being used by the customers. The operations team is now hard at work, making sure that everything is running smoothly. Based on the configuration of the hosting service, the environment automatically scales with load to handle peaks and troughs in the number of active users.

DevOps Stages. code Dev -sest Deploy Monitor. Monitor. 

Scene 28

The ‘final’ phase of the DevOps cycle is to monitor the environment. this builds on the customer feedback provided in the Operate phase by collecting data and providing analytics on customer behavior, performance, errors, and more.

DevOps Stages. Five different categories of DevOps practices Treat Ops as first-class citizens from the point of view of requirements Make Dev more responsible for relevant incident handling Enforce the deployment process used by all, including Dev and Ops personnel Use continuous deployment Develop infrastructure code, such as deployment scripts. 

Scene 29

Five different categories of DevOps practices
 Treat Ops as first-class citizens from the point of view of requirements Make Dev more responsible for relevant incident handling Enforce the deployment process used by all, including Dev and Ops personnel Use continuous deployment Develop infrastructure code, such as deployment scripts

DevOps Stages. • Treat Operations personnel as first• class stakeholders • Get their input when developing requirements • Small teams • Limited coordination • Unit tests Build • Build tools • Supports continuous integration Testing • Automated testing • User acceptance testing Deployment • Deployment tools • Supports continuous deployment • Monitoring • Respondng to error conditions DevOps life cycle processes [Notation: Portefls Value Chain]. 

Scene 30

• Treat Operations
personnel as first•
class stakeholders
• Get their input
when developing
requirements
• Small teams
• Limited
coordination
• Unit tests
Build
• Build tools
• Supports
continuous
integration
Testing
• Automated
testing
• User
acceptance
testing
Deployment
• Deployment
tools
• Supports
continuous
deployment
• Monitoring
• Respondng to
error conditions
DevOps life cycle processes [Notation: Portefls Value Chain]

DevOps Delivery Pipeline. The most common components of a pipeline in DevOps are build automation or continuous integration, test automation, and deployment automation.. 

Scene 31

The most common components of a pipeline in DevOps are build automation or continuous integration, test automation, and deployment automation.

A pipeline consists of a set of tools which are classified into the following categories such as: Source control Build tools Containerization Configuration management Monitoring Continuous Integration Pipeline

DevOps Delivery Pipeline. DevOps Myths & Misconception DevOps is a Team CI/CD is all about DevOps Non-Compliant to Industry Standards. 

Scene 32

DevOps Myths & Misconception DevOps is a Team CI/CD is all about DevOps Non-Compliant to Industry Standards

An additional team is likely  to cause more  communication issues
 Scalability  Consistency  Reliability
 Regulations implement  control in order to be  compliant Controls reduce the risk  that may affect the  confidentiality, integrity,  and availability of  information

DevOps Delivery Pipeline. DevOps Myths & Misconception Automation eliminates ALL bottlenecks “Universal" Continuous Delivery pipeline All about Tools Release as fast as Amazon / Facebook. 

Scene 33

DevOps Myths & Misconception Automation eliminates ALL bottlenecks “Universal" Continuous Delivery pipeline All about Tools Release as fast as Amazon / Facebook

DevOps Delivery Pipeline. Benefits of CI: Small changes are easy to integrate into large codebases. More comfortable for other team members to see what you have been working. Fewer integration issues allow rapid code delivery. Bugs are identified early, making them easier to fix, resulting in less debugging work.. 

Scene 34

Benefits of CI:
 Small changes are easy to integrate into large codebases. More comfortable for other team members to see what you have been working. Fewer integration issues allow rapid code delivery. Bugs are identified early, making them easier to fix, resulting in less debugging work.

DevOps Delivery Pipeline. Benefits of the CD: Faster bug fixes and features delivery. CD allows the team to work on features and bug fixes in small batches, which means user feedback is received much quicker. It reduces the overall time and cost of the project.. 

Scene 35

Benefits of the CD:
 Faster bug fixes and features delivery. CD allows the team to work on features and bug fixes in small batches, which means user feedback is received much quicker.  It reduces the overall time and cost of the project.

Activity Time. Learners need to form into groups and search for the topic DevOps Agile and discuss same with the trainer. 

Scene 36

Learners need to form into groups and search for the topic DevOps Agile and discuss same with the trainer

DevOps on Cloud. The centralized nature of cloud computing provides DevOps automation with a standard and centralized platform for processes like testing, deployment, and production. Most public and private cloud computing providers support DevOps systemically on their platform, including continuous integration and continuous development tools. Cloud-based DevOps lessens the need to account for resources leveraged.. 

Scene 37

The centralized nature of cloud computing provides DevOps automation with a standard and centralized platform for processes like testing, deployment, and production.  Most public and private cloud computing providers support DevOps systemically on their platform, including continuous integration and continuous development tools. Cloud-based DevOps lessens the need to account for resources leveraged.

DevOps on Cloud. Cloud as a Catalyst for DevOps On-demand self-service Broad network access Resource pooling Rapid elasticity It is the Capabilities can be elastically provisioned and released Measured service. 

Scene 38

Cloud as a Catalyst for DevOps
 On-demand self-service Broad network access Resource pooling Rapid elasticity It is the Capabilities can be elastically provisioned and released Measured service

DevOps on Cloud. Python File Operations | Learn to Perform any Operation in Python File. 

Scene 39

Python File Operations | Learn to Perform any Operation in Python File

Cloud as a Catalyst for DevOps Characterization of the cloud by National Institute of Standards and Technology (NIST) On-demand self-service Broad network access Resource pooling Rapid elasticity Measured service Software as a Service (SaaS) Platform as a Service (PaaS) Infrastructure as a Service (IaaS)

DevOps on Cloud. Software as a Service (SaaS) In this the consumer is provided the capability to use the provider’s applications running on a cloud infrastructure The applications are accessible from various client devices through either a thin client interface, such as a web browser (e.g., web-based e-mail) or an application interface The consumer does not manage or control the underlying cloud infrastructure including networks, servers, operating systems, storage. For an example, you can relate google apps, Cisco WebEx, as a Service, Office 365 service, where Provider deals with the licensing of software’s. 

Scene 40

Software as a Service (SaaS) In this the consumer is provided the capability to use the provider’s applications running on a  cloud infrastructure The applications are accessible from various client devices through either a thin client interface,  such as a web browser (e.g., web-based e-mail) or an application interface The consumer does not manage or control the underlying cloud infrastructure including  networks, servers, operating systems, storage. For an example, you can relate google apps, Cisco WebEx, as a Service, Office 365 service,  where Provider deals with the licensing of software’s

DevOps on Cloud. Platform as a Service (PaaS) The consumer is provided the capability to deploy onto the cloud infrastructure consumer- created or acquired applications created using programming languages, libraries, services, and tools supported by the provider The consumer does not manage or control the underlying cloud infrastructure including networks, servers, operating systems, or storage, but consumer has control over the deployed applications and possibly configuration settings for the application-hosting environment For an Example: .NET Development platform is considered as a platform.. 

Scene 41

Platform as a Service (PaaS) The consumer is provided the capability to deploy onto the cloud infrastructure consumer-  created or acquired applications created using programming languages, libraries, services, and  tools supported by the provider The consumer does not manage or control the underlying cloud infrastructure including  networks, servers, operating systems, or storage, but consumer has control over the deployed  applications and possibly configuration settings for the application-hosting environment For an Example: .NET Development platform is considered as a platform.

DevOps on Cloud. Infrastructure as a Service (IaaS) The consumer is provided the capability to provision processing, storage, networks, and other fundamental computing resources where the consumer is able to deploy and run arbitrary software, which can include operating systems and applications The consumer does not manage or control the underlying cloud infrastructure but the consumer has control over operating systems, storage, and deployed applications; and possibly limited control of select networking components (e.g., host firewalls). For this, you can consider any Server Provisioning is IaaS,. 

Scene 42

Infrastructure as a Service (IaaS) The consumer is provided the capability to provision processing, storage, networks, and other  fundamental computing resources where the consumer is able to deploy and run arbitrary  software, which can include operating systems and applications The consumer does not manage or control the underlying cloud infrastructure but the consumer has control over operating systems, storage, and deployed applications; and possibly limited control of select networking components (e.g., host firewalls). For this, you can consider any Server  Provisioning is IaaS,

DevOps on Cloud. Three of the unique aspects of the cloud that impact DevOps Three of the unique aspects of the cloud that impact DevOps: The ability to create and switch environments simply Simply create and migrate environments is—as is the ease of cloning new instances The ability to create VMs easily Administering the running VMs are important to find out for which VM we are paying but not using it Tool such as Janitor Monkey to scan an account The management of databases. 

Scene 43

Three of the unique aspects of the cloud that impact DevOps Three of the unique aspects of the cloud that impact DevOps: The ability to create and switch environments simply Simply create and migrate environments is—as is the ease of cloning new instances The ability to create VMs easily Administering the running VMs are important to find out for which VM we are paying but not using it Tool such as Janitor Monkey to scan an account The management of databases

Various AWS services. AWS is the best cloud service provider, and DevOps is the implementation of the software development lifecycle. Here are some reasons which make AWS DevOps a highly popular combination, such as: AWS CloudFormation AWS EC2 AWS Cloud Watch AWS Code Pipeline. 

Scene 44

AWS is the best cloud service provider, and DevOps is the implementation of the software development lifecycle.
 Here are some reasons which make AWS DevOps a highly popular combination, such as: AWS CloudFormation AWS EC2 AWS Cloud Watch AWS Code Pipeline

Various AWS services. [image]. Flickr / Yahoo Flickr was able to reach 10+ Deploy per day after adopting DevOps •	In 2009 You May Also Refer: YouTube Link: https://www.youtube.com/watch?v=LdOe18KhtT4. 

Scene 45

Flickr / Yahoo Flickr was able to reach 10+ Deploy per day after adopting DevOps •	In 2009 You May Also Refer: YouTube Link: https://www.youtube.com/watch?v=LdOe18KhtT4

Various AWS services. [image]. Netflix Netflix's streaming service is a large distributed system hosted on Amazon Web Services (AWS) So many components that have to work together to provide reliable video streams to customers across a wide range of devices Netflix engineers needed to focus heavily on the quality attributes of reliability and robustness for both server- and client-side components Achieved this with DevOps by introducing a tool called Chaos Monkey Chaos Monkey is basically a script that runs continually in all Netflix environments, causing chaos by randomly shutting down server instances Thus, while writing code, Netflix developers are constantly operating in an environment of unreliable services and unexpected outages Unique opportunity to test their software in unexpected failure conditions. 

Scene 46

Netflix Netflix's streaming service is a large distributed system hosted on Amazon Web Services (AWS) So many components that have to work together to provide reliable video streams to customers  across a wide range of devices Netflix engineers needed to focus heavily on the quality attributes of reliability and robustness  for both server- and client-side components Achieved this with DevOps by  introducing a tool called Chaos Monkey Chaos Monkey is basically a script that runs continually in all Netflix environments, causing  chaos by randomly shutting down server instances Thus, while writing code, Netflix developers are constantly operating in an environment of  unreliable services and unexpected outages Unique opportunity to test their software in unexpected failure conditions

Activity Time. Learners need to form into groups and find out real-time case studies for DevOps technology. 

Scene 47

Learners need to form into groups  and find out real-time case studies for DevOps technology

Various AWS services. Anti-Patterns Blame Culture A blame culture is one that tends toward blaming and punishing people when mistakes are made, either at an individual or an organizational level Silos A departmental or organizational silo describes the mentality of teams that do not share their knowledge with other teams in the same company Root Cause Analysis Root cause analysis (RCA) is a method to identify contributing and “root” causes of events or near-misses/close calls and the appropriate actions to prevent a recurrence Human Errors Human error, the idea that a human being made a mistake that directly caused a failure, is often cited as the root cause in a root cause analysis. 

Scene 48

Anti-Patterns Blame Culture A blame culture is one that tends toward blaming and punishing people when mistakes are made,  either at an individual or an organizational level Silos A departmental or organizational silo describes the mentality of teams that do not share their  knowledge with other teams in the same company Root Cause Analysis Root cause analysis (RCA) is a method to identify contributing and “root” causes of events or near-misses/close calls and the appropriate actions to prevent a recurrence Human Errors Human error, the idea that a human being made a mistake that directly caused a failure, is often cited  as the root cause in a root cause analysis

Various AWS services. Example for Silos TVS India T. V. Sundaram Iyengar Founded in 1978. 

Scene 49

Example for Silos TVS India T. V. Sundaram Iyengar Founded in 1978

Various AWS services. Three dimensions of DevOps People Process Tools / Technology. 

Scene 50

Three dimensions of DevOps People Process Tools / Technology

Module 1 Communication Skills

 Flickr / Yahoo Flickr was able to reach 10+ Deploy per day after adopting DevOps •	In 2009 You May Also Refer: YouTube Link: https://www.youtube.com/watch?v=LdOe18KhtT4