This document provides an overview of DevOps including: - What DevOps is and why it is needed to solve challenges of miscommunication between development and operations teams - How DevOps differs from traditional IT and Agile approaches through its principles of automating processes, measuring outcomes, and sharing knowledge - The DevOps lifecycle and tools used at each stage including source control, containers, infrastructure as code, and monitoring - Roles of DevOps engineers in facilitating continuous integration, delivery, and deployment through automation

1. Harsh Manvar
@Manvar_harsh
Masterclass on DevOps

2. DevOps Overview
● What is DevOps ?
● Why DevOps is Needed ?
● How is DevOps different from traditional IT
● DevOps Use cases in business
● DevOps Lifecycle
● DevOps WorkFlow/Road Map
● How DevOps different from Agile ? DevOps vs Agile
● DevOps Principles
● Who is DevOps Engineer ?
● Roles, Responsibilities, and Skills of DevOps Engineer
● DevOps Automation Tools
● What is the future of DevOps ?
● 30-60-90 days DevOps plan

3. Evolution of Computing

4. What DevOps
Looks like ?

5. Typical software Release Process
Idea Requirements Code it Test Build & package
Deploy
Configure server
● Installing tools
● Deploy application
● Firewall rules

6. Typical software Release Process
Idea Requirements Code it Test Build & package
Deploy
Improvements
● Add new features
● Optimize performance by server, code etc
● Bug fixes
● Versioning and quick release to end users

7. Challenges DevOps tries to solve
Developers
Code the application
● Can’t deploy
● Don’t consider, where app gets
deployed
● Try to delivery feature fast
Operations
Deploy & Operation the application
● Don’t know how the app works
● Deployment guide not well documented
● Maintain stability
● Miscommunications leads release period delay for days..!
● No clearly defined automated process
● Checklists & Documentations
● Both have different Priorities (New feature vs Stability)

8. Challenges with Testers
Feature/Code Test Build & package
● Tester - Verify
the feature
checks
● Overall system
performance and
checks after
each new
feature
Issues
● Manual traditional process to test also delay
release

9. DevSecOps in picture
Feature/Code Test Build & package
● Operations - will
it affect system’s
stability ?
● Security - will it
affect system’s
security ?
Issues
● Manual traditional process to check security
delay release

10. Tons of manual work in operations
● Executing commands on servers to configure tools, packages
● Manually preparing the deployment environment,
● Manually configuring the environment variables
● Manually configuring the user access & permission
● Manually deploying application
Issues
● Slow & more errors
● Knowledge sharing issues
● Hard to trace, who executed what when
● If some issue hard to replicate or recover state

11. Continuous Delivery
It’s all about a continuous process

12. How is DevOps different from traditional IT

13. DevOps Principle
● Culture represented by human
communication, technical
processes, and tools
● Automate everything
● Measurement of KPIs,
Continuous improvement
● Sharing feedback, best practices
& knowledge
Culture
Automate
Measure
Share

14. DevOps lifecycle

15. Benefits of DevOps
● Speed
● Reliability
● Improved Collaboration
● Rapid Delivery
● Scale
● Security DevOps is a mentality.
Ship small increments quickly a
safely.

16. DevOps goes along with Agile process

17. How does DevOps help achieve this?
Combination of :
Cultural philosophies Practices Tools
● Anything that creates the process of releasing the software fast and with high quality
● Main part was that Dev and Ops should work together more often

18. Each company has different practices
Combination of :
Cultural philosophies Practices Tools
Let’s do this
way
Let’s do this
way
Let’s do this
way

19. DevOps as a separate Role & Streamline process
Developer doing DevOps Operation team doing DevOps
Doing only Devops
DevOps as a Set of tools
● DevOps Engineer need to know
tools & technologies
Source code
mgt
Cloud
Containers Infra as code
Monitoring
CI/CD Pkg mgt

20. DevOps Tools &
Technologies

21. DevOps Engineering Role

22. Who is DevOps Engineer ?
● Responsibilities
○ CI/CD management
○ Writing specification & docs
○ Work with automation services & platforms
○ Scripting & Coding
○ Performance assessment
○ Monitoring
● Experience & skills
○ BS/MS in CS or related field
○ 2 years of work experience as System administrator, software
engineer
○ IT operation & Data management/Database (SQL & NoSQL)
○ Open-source automation tools (Git, Jenkins, Ansible, Docker, K8s,
Puppet)
○ Cloud services (AWS, Google, Oracle, IBM)
○ Scripting (Python, Go, Bash, Perl)

23. Boundaries of DevOps from Development
Developer
Git
● How Developer work
● Which Git workflow they follows
● How application configured required Databases,
Env, connection with other services
● Git tool idea
● Linux basics
● CLI/Commands
● HTTP/HTTPS
● IP, DNS, Ports
Server
● Cloud
● IAC
● Databases
Linux

24. Micro services

25. Containerization

26. Boundaries of DevOps from Development
Developer
Git
● How Developer work
● Which Git workflow they follows
● How application configured required Databases,
Env, connection with other services
● Git tool, Containers tools
● Linux basics
● CLI/Commands
● HTTP/HTTPS
● IP, DNS, Ports
Server
● Cloud
● IAC
● Databases
Linux
How to release application ?

27. Continuous Delivery
and Automation
● Development
● Continuous Integration
● Continuous Delivery
● Continuous Deployment
● Continuous Monitoring

28. Continuous
Integration

29. Continuous Integration
Developer
Git
Server
Run test
Package app
Java Jar
Build tools & package manager
● Maven
● Gradel
● Npm
● Pip

30. CI with Container Images
Developer
Git
Server
Run test
● Docker
● Artifacts repository
Container
Package app
Java Jar
Push to artifacts
repository

31. Continuous
Deployment

32. Continuous Deployment
Developer
Git
Server
Run test Container
Package app
Java Jar
Push to artifacts
repository
Deploy to
server
Core concept CI/CD
Notification
Slack/Email
Extra
CDN images to
bucket sync
Managing failed
build plan

33. Continuous
Delivery

34. Continuous Delivery
Developer
Git
Server
Run test Container
Package app
Java Jar
Push to artifacts
repository
Approve
Deploy

35. Continuous
Delivery
Vs
Continuous
Deployment

36. Cloud infra

37. Cloud concepts
Load Balancing Backup Security
Cloud
providers
Clustering Networking
Monitoring
● Offer range of services
● Save costs in focus
● Different services idea across the diff
cloud provider

38. Kubernetes

39. Infrastructure
As
Code

40. Diff environments with Infra as Code
Development Staging Production
Infra Code

41. Monitoring

42. 1 tool in each category to learn to become DevOps
Dev concepts CI/CD
OS systems &
Linux basics
Networking &
Security
Cloud Provider Scripting
Containers
Container
Orchestration
Monitoring
Infra as Code Version Control

43. DevOps vs SRE (friends)
● DevOps focuses on speed of development
& delivery while enforcing continuity.
● DevOps works with product development
teams.
● Setup tools which help makes
development process quicker and deliver
feature asap
● SRE mainly focuses on enhancing system
availability and reliability.
● SRE works with operation teams
● SRE mostly focuses on operation &
service level commitments (SLIs, SLAs,
SLOs)
● Handling support escalation issues
● Conducting and reporting on incident
reviews

44. Thank you!
Find me on :
LinkedIn - Harsh Manvar
Twitter - manvar_harsh
Medium - harsh.manvar111
GitHub - harsh4870