DevOps Overview for Beginners

Ultimatix DevOps CoE

24-Oct-19 1
TCS Internal | Copyright © 2015 Tata Consultancy Services Limited
Typical Dev & Ops World

Customer gives
requirements to
ABC Project
Team

Project Manager recruits

Champion Developer
“Ram” & Champion
SysAdmin “Shyam”

TCS Internal 2
 Typical Dev & Ops World
Develop

Fix Security Vulnerabilities

Fix Defects / Bugs

Fix Performance Issues

Chang Code Review
Stability
e

Unit Testing
Dev Engineer Ops Engineer
Check-in

Build

Test Env. Setup

& Deployment
•••• Ram
Ram
Shyam
Ram’s
Ram
Ram
In case
What
Ram needs
now
feels
decides
has
finally
now
ofto
can
has heanow
to
application
also needs
needsTest
has
to
failures,
be
understands done to
breathes Env.
start
ensure
to check
done
is
test &huge
his
Unit
going
ahis
Shyam
to
build
the helphis
perform procures
ifcode
his
all he
Testing.
Applicationto be
Application
has
Ram
requirements
sigh
Code
to
& Infrastructure
application
needed
is
used
of always
relief
Review.
diagnose
Shyam
package
&
to
byfor has
& met
checks
available
awork
large
potential
&it
the gets no User’s
of
ready
errors
better
with other in the
&?users
security
to
find code in SVN
developers’ codeFunctional
••• The
at then
Requirements
He has
Hetheno
threats
promote to
ofconnects
same manually
Applications
&has
realizes
causes
His code time.
attacks
the with
test
Application
that
a lottheof Shyam
& every
its
checklist to
serverscomplete
unit
to Production
dependencies level
that
is 250 points code.
he Env.
has
Environment Setup
Every
to &
line, configurations
Every Method
long & may take hours to complete etc (UAT)
Testing
develops
••• administer
connects to the Application
User(s)
He
Ram
He realizes
Shyam hesets
needs
has
once
Still, &
decides tothere
isup
todoesn’t
his now all
coordinate
again
Dev
to is
the
constantly
check
connects
know
Team
manually ifto
nowant
way
now alltest
component
with to
growing
if all the
with
the
download the
the
Shyam functionalities
confirm
one if
by
&Security
to
checkpoints
“Changes” to entire
one.
functionalities
setup
the
package code
inmanually
Experts
the
are hishas been covered in the
&dependencies
relevant
Application
missing make
are not. Security
•• He & awaits
test cases
also
has
Application
changes
Production
Shyam User
toorclose
&checks
to his not
can Acceptance
Opswith
continuouswork
the
Environment
TeamRam
monitor
under
security
wanton Testing
exact
& look
“load” (UAT)forApproval
versions
when
vulnerabilities
“Stability” errorrequired
accessedscenarios
by& large
makes the env ready Testing
•• He
Ram may
no of
Once
This now need
users
the
creates ato
coordinates
at the
environmentmake
“Wall same changes
ofwith
istime himin
ready
Confusion” &case
he deploysuserthe
coordinates
between isthe
not
withhappy
Application
teamsShyammanually Performance
• with
Shyam
He needs
for thehasend
Deployment product
totoperform
complete the deployment
Performance Testing steps one by one
to simulate Real& cannot afford any mistake Testing
• Ram depends
Life load
Application & make on Shyam’s
is now necessary
live & its availability
tuning
Shyam’s & his skills fortodeployment.
if required
responsibility make Production Setup &
sure it runs as desired Deployment
TCS Internal 3
What if……..
 Ram & Shyam worked together as “One Team” towards “One Goal”
 Thought more alike & stopped blame games
 Removed Silos
 Shared responsibilities
 Change their mindset on how “Dev” & “Ops” work

DevOps

Dev Ops

TCS Internal 4
What is DevOps ?
 As the name suggests, DevOps brings “Dev” & “Ops” closer
 But its not just about Dev & Ops working together
 Let’s look at CALMS model to understand DevOps better
Culture • Embrace Change
• Eliminate Blame Game

Automation • CI / CD
• “Infrastructure As A Code”

Lean • Focus on Business Value for end-user

Metrics • Measure Everything

• Show the Improvement
Sharing • Open Information Sharing
• Collaboration

CALMS Model

TCS Internal 5
DevOps Culture
 DevOps teams eliminate silos, removes conflicting motivations

 Embrace the change to work towards common objectives

– Ops engineers attend Daily Stand Up calls & share Ops view

– Dev engineers jointly troubleshoot errors with Ops engineers

 Review & Test Applications very early in the SDLC cycle

– Shift Left. Fail Early & Fail Fast

 Programmable & Configurable Environments

– Eg: Ram & Shyam together write code to create Environments

TCS Internal 6
DevOps Automation
 Automate all SDLC Phases through DevOps tools
– Automate Reviews & Testing

– Automate Build & Deployments

– Automate Environment Setups  Infrastructure as a Code

– Automate Everything

 Integrate all SDLC Phases into single Toolchain

 “Continuous Integration”
– Faster Software Releases

– Better Quality of Deliverables

– Improved IT Agility
TCS Internal 7
Typical DevOps Automated Toolchain
Maintenance /
Develop Patch Upgrades

Fix Security Vulnerabilities

Fix Defects / Bugs

Enhancements & Bugs

Fix Performance Issues

Infra Configuration Changes

Code Review

Unit Testing

Check-in

Build

Test Env. Setup

& Deployment
Monitoring &
Functional Log Analytics
Testing (UAT)
Security
Testing

Performance
Testing
Production Setup &
Deployment
TCS Internal 8
Benefits of Thinking “The DevOps Way”

Changed Tighter Control

Mindset  Faster “SDLC of Build &
Repeatability
Single Common Execution Deployment
Objective Activities

Faster Better Quality of

Better Agility
“Time to Market” Deliverables
TCS Internal 9
Let’s think “The DevOps Way”

| Copyright © 2015 Tata Consultancy Services Limited

10