De facto DevOps, de facto Agile. Today DevOps is the Manufacturing Revolution of Our Age. There is no escape for us. When got a DevOps, you got a DevOps. DevOps simply is the combination of cultural philosophies,practices,and tools that increase an organization’s ability to deliver applications and services at high velocity : evolving and improving products at a faster pace than organizations using traditional software development and infrastructure management processes.

1. 1
The War
The DevOps Revolution

2. 2
Developer & Operation – The Tug of War
TheGREATWALLofConfusion
Thinks about Change, Automation, Tuning, Fixes, hotfixes Thinks about Release, Mess-up, Never-works, Instability
Receiving…
Package of Instability..!!!
Sending…
Package of code goodness
Impatient
Temperamental
Prima donna Artist
Careless about change
Ignorant about real world
How Dev sees Ops How Ops sees Dev
Slow to act
Temperamental
Rigid to change
Always says NO
Too dumb to understand App

3. 3
C.A.L.M.S.
L – Lean
M – Measurement
C – Culture
S – Sharing
A – Automation
Legacy of the Development and Operation Show
I am Developer,
I need a server…
now..!!!
I want access to the
production
systems…No Access..!
How can I work here?
Something is wrong
in PROD…whose
fault is it?
So many alerts they
are meaningless..
Get me the right one.
I don’t have time to
save time…Too
many release stuffs
and preparation
Our hero is a
bottleneck…
I am inside of Scripts
Hell…Help me…!!!
Doyouhearthesemoreoftenfromyour
DevelopmentandOpsTeam?
Then it’s correct time to think DevOps and be C.A.L.M.S

4. 4
Dev + Ops DevOps
Two perspectives, but one defined Goal. DevOps brings in both parties together to deliver customer value in high velocity and continuously.

5. 5
DevOps – A No-Brainer
Environment
Configuration lock down &
synergy among multiple
environments
Synergy
Developer and Operation
work together
Key things
Automation
Integrate, Build, Test and
Delivery Automation
1
2
3
4
Happy Customer
Less defect, faster delivery of
feature
DevOps is the combination of cultural
philosophies, practices, and tools that increases
an organization’s ability to deliver applications
and services at high velocity: evolving and
improving products at a faster pace than
organizations using traditional software
development and infrastructure management
processes. This speed enables organizations to
better serve their customers and compete more
effectively in the market.
Under a DevOps model, development and
operations teams are no longer “siloed.”
Sometimes, these two teams are merged into a
single team where the engineers work across the
entire application lifecycle, from development and
test to deployment to operations, and develop a
range of skills not limited to a single function.
Quality assurance and security teams may also
become more tightly integrated with
development and operations and throughout the
application lifecycle.
These teams use practices to automate processes
that historically have been manual and slow. They
use a technology stack and tooling which help
them operate and evolve applications quickly and
reliably.
What is what

6. 6
DevOps – The perpetual cycle’s Linear projection
Developer
Code & Artifact
Repository
CI/CD Tool Test/Stage PROD Customer

7. 7
DevOps - Tangible Benefits
Agility & Velocity
Rapid Delivery
Reliability & Confidence
Increased effectiveness
IT & IS Collaboration
Continuous Integration and Delivery
Technical benefits:
• Continuous software delivery
• Less complex problems to fix
• Faster resolution of problems
Business benefits:
• Faster delivery of features
• More stable operating environments
• More time available to add value
(rather than fix/maintain)
Customer Benefits
Agility in Process
FAST Delivery
More successful Production
Sharing and Collaboration Automated Repetition Measureable Scalability Focus Always

8. 8
Business Value Delivered of Adopting DevOps
DevOps is the Manufacturing Revolution
of Our Age

9. 9
DevOps Industry Challenges
Development and operations view the world from
different perspectives. Although they are both
concerned with the same outcomes, their
approaches are different, like two sides of the same
coin.
Selling DevOps to developers isn’t too difficult – for
development it’s easy to see the benefits to creativity
and innovation made possible through DevOps.
Operations, on the other hand, views DevOps with
suspicion, believing it is an attempted development
coup to enable developers to continually dump
buggy, untested software into production.
There is a popular sports adage that goes, “There is
no comfort in the growth zone, and there is no
growth in the comfort zone.” DevOps requires
change. Change requires adaptation. Adaptation
requires learning new skills.
DevOps will require new workflows, which if
implemented will cause a trickle-down effect
throughout the organization. Current tools will
become obsolete, and investment in new tools will
be necessary to support new workflows.
DevOps will shift the power balance in the
organization, in some way or another. It’s inevitable,
but not necessarily insidious.
DevOps lot of times is misunderstood or
mischaracterized. Such as -
DevOps replaces Agile, DevOps replaces ITIL, DevOps
means NoOps, DevOps is only for open source
software, DevOps is just “infrastructure as code” or
automation, DevOps is only for startups and unicorns
1
Language Barriers
2
Developer vs. Operations
mentality
3
Learning New Skills
4
Work Disruption
5
Management Responsibilities
6
A Bunch of Myths

10. 10
DevOps - Weapon Stack = Culture + following
• Test
o Jenkins
o Solano
• Build Systems
o Maven
o ANT
o Gradle
• Deployment
o Capistrano
Infrastructure as a Service
o Amazon Web Services
o Microsoft Azure
o Cloud Foundry
o OpenStack
o Rackspace
Containerization & Virtualization
o LXC
o Solaris Container
o Docker
o Rocket
Application Servers
• JBoss
• Tomcat
• Jetty
• Webspear
• Weblogic
Web Servers
• Nginx
• Apache
Databases
• Postgres
• MySQL, Oracle
• MongoDB, Cassandra
• Redis
• MS SQL
• Percona Server
Queues, Caches
• ActiveMQ
• RabbitMQ
• memcache
• varnish
• squid
Process Supervisors
o Monit
o runit
o Supervisor
o god
o Blue Pill
o Upstart
o systemd
Application Logging
o PaperTrail
o Logstash
o Loggly
o Logentries
o Splunk
o SumoLogic
Monitoring & Alerting
o New Relic
o Nagios
o Icinga
o Graphite
o Ganglia
o Cacti
o PagerDuty
o Sensu

11. 11
About the Author
Name: Somenath Ghosh
Contact: +91 9176596597 | +91 9830742553
Email: somenath.ghosh84@gmail.com
Blog: http://somenathghosh.space
Background:
With 10+ Years of IT experience of directing cross-functional team of technical experts to analyze, process, implement,
re-host and re-engineering Applications on TCS hosted Infrastructures. Recognized for Leadership in planning,
scheduling, crisis and risk management. Proven record of delivering application, automation, lift and shift Full Stack
Application to TCS owned Datacenter. Have larger spectrum of experience in Bank merger, acquisition and
transformation projects across consumer Deposit system, Financial Authorization system.
Acting as Techno-Delivery Manager at India's Largest IT service, the author has extensive knowledge in DevOps practices
across Banking and Financial Industries. Along with it, the author has executed Customer POCs on Docker, Dockerized
Application CI/CD, Hybrid Mobile App Development, Product Design & Delivery & UX/UI consultation, so on and so
forth.
Current passion:
Docker, Docker Orchestration, API Management and PWA(Progressive Web App), VR/AR