For a beginner, this is a good quality pictorial representation of DevOps and DevOps Center of Excellence. Opex Software focuses on consulting, implementation and development of DevOps tools and platforms. Have helped small and large data centers! This presentation talks about Continuous Integration, Continuous Delivery at a high level. For detailed presentations and flows, please ping us. Thanks again, Enjoy!

1. 15/13/2015
What is DevOps and its
Center of Excellence?
Breaking into the new-age
May 2015
Sanju Burkule – Founder & CEO, DevOps Enthusiast
Gunanand Nagarkar – CoFounder & CTO, DevOps Solutions Expert
Amit Patel – CoFounder & DevOps Evangelist, Australia

2. Market expectations from Cloud Businesses
Expectation
High reliability | Faster time to market | Software Quality
Keep in mind
Technical problems can result in permanent loss of customers
Very high speed expectations, unheard of speeds
Flickr: Deploys 10 times a day in 2009!
Amazon deploys once every 11 minutes! (ChefConf2015!)

3. Summary of DevOps CoE
35/13/2015
The primary goals
• increase speed of execution,
• maximize staff productivity, and
• improve service quality.
CoE Role:
• Driving cultural change
• Encourages collaboration between Dev & Ops
• automate IT processes, standardize ToolChain
• collect metrics across Dev & Ops Vs a siloed approach
• Incubate, release and support DevOps projects
• Integrated toolsets based on loosely-coupled platforms
will best support DevOps and continuous deployment
Share the reports and measurements across all Development
& Operations as well as other stakeholders.
Reimagine speed
Break Silos
Deliver together

4. Challenges in implementing DevOps

5. • Unclear understanding of DevOps benefits
• Business Case doesn’t include the resources
necessary to maintain solution
• No clear ownership of the Project
• No definite champions to evangelize
• No designated metrics to define success
• Inconsistent reporting
• Ambitious end-goal with no clear milestones
to measure progress
• No plan for continued education
Why do DevOps Projects Fail?
Potential Gaps in Planning

6. Critical learnings to manage continuous change
• To succeed, grow beyond pockets of IT automation to span
organizational groups and their project activities
• DevOps successes can be incubated, expanded and sustained
through Centers of Excellence
• Integrated toolsets based on loosely-coupled platforms will best
support DevOps and continuous deployment
• Consider microservices. Own platform in CoE.
• Inspire and educate Architects, component level upgrades Vs
Application upgrade
• Start with smaller project to setup vCoE.
• Identify, evaluate, standardize on a DevOps toolset.
– Use containers effectively, educate larger organizations on new-age tools
(docker, packer, serf, new relic, chef, mesosphere, atlas, terraform,
vagrant….) simple/elegant/fast/focused tools.

7. Basics of DevOps COE
• Consistent Project Management with clear milestones
• Focus on business value, not just technical sophistication
• Multi-Disciplinary team to support the project
• Business Analytics with well-defined metrics and regular reporting
• Focus on common automation standards and processes
• Continual search for new automation opportunities
DevOps Center of Excellence
Definition
A core group of individuals with specific technical, business and management skills
that acts as a evangelist for new projects, a clearinghouse of knowledge, and most
importantly as a developer of automated DevOps processes.

8. Center of Excellence – Roles
Operators
Engineers
Business
Analysts
Program
Manager
• Ensure timely completion of milestones
• Provide regular reporting of metrics and project progress
• Identify appropriate business metrics(key success metrics)
• Track and report project metrics and ongoing savings
• information dashboards with drill-down detail.
• Identify potential new automation use cases
• Create standardized automation processes and procedures
• Design automation architecture and incorporate new tools
• Maintain automation infrastructure over time
• Infrastructure as code

9. The Wall of Confusion causes both Development &
Operations to lose sight of the overall business
perspective. Business needs change and stability.
Business needs an IT culture that recognizes it.
Culture & the Wall of Confusion
95/13/2015
Development Operations
“I want
change.”
“I want
stability.”
• Development is paid to accomplish change.
• Business counts on Development to respond to
changing needs.
• Development is often incentivized to create as much
change as possible.
• Operations is paid to maintain stability.
• Business counts on operations to “keep the lights on”
and deliver services that make the business money
today.
• Operations is motivated to resist change as it
undermines stability and reliability.
Wall of Confusion

10. DevOps Maturity Model
105/13/2015
Practice
Build management and
continuous integration
Environments and
deployment
Release
management and
compliance
Testing Data management
Level 3 – Optimizing:
Focus on process improvement
Teams regularly meet to discuss
integration problems and resolve
them with automation, faster
feedback, and better visibility.
All environments managed
effectively. Provisioning fully
automated. Virtualization used if
applicable.
Operations and delivery
teams regularly
collaborate to manage
risks and reduce cycle
times.
Production
rollbacks rare.
Defects found and
fixed immediately.
Release to release
feedback loop of database
performance and
deployment process.
Level 2 – Quantitatively
managed:
Process measured and controlled
Build metrics gathered, made
visible, and acted on. Builds are
not left broken.
Orchestrated deployments
managed. Release and rollback
processes tested.
Environment and
application health
monitored and
proactively managed.
Cycle time monitored.
Quality metrics and
trends tracked.
Non functional
requirements
defined and
measured.
Database upgrades and
rollbacks tested with every
deployment. Database
performance monitored
and optimized.
Level 1 – Consistent:
Automated processes applied
across whole application lifecycle
Automated build and test cycle
every time a change is
committed. Dependencies
managed. Re-use of scripts and
tools.
Fully automated self-service push-
button process for deploying
software. Same process to deploy
to every environment.
Change management and
approvals processes
defined and enforced.
Regulatory and
compliance conditions
met.
Automated unit and
acceptance tests,
the latter written
with testers.
Testing part of
development
process.
Database changes
performed automatically
as part of deployment
process.
Level 0 – Repeatable:
Process documented and partly
automated
Regular automated build and
testing. Any build can be re-
created from source control using
automated process.
Automated deployment to some
environments. Creation of new
environments is cheap. All
configuration externalized /
versioned.
Painful and infrequent,
but reliable, releases.
Limited traceability from
requirements to release.
Automated tests
written as part of
story development.
Changes to databases done
with automated scripts
versioned with application.
Level -1 – Regressive:
Processes unrepeatable, poorly
controlled, and reactive
Manual processes for building
software. No management of
artifacts and reports.
Manual process for deploying
software. Environment-specific
binaries. Environments
provisioned manually.
Infrequent and unreliable
releases.
Manual testing
after development.
Data migrations
unversioned and
performed manually.
Current State Desired State

11. 11
Key ingredient needed to seed DevOps CoE
5/13/2015

12. 12
People wanting to create time
5/13/2015

13. 13
This can be solved…
5/13/2015

14. 14
Dev and Ops are responsible together
5/13/2015

15. 15
DevOps is about
5/13/2015

16. 16
How it started…
5/13/2015

17. 17
Basics: CI Server in DevOps
5/13/2015

18. 18
Email results to required people
5/13/2015

19. 19
Use containers effectively in DevOps pipelines
5/13/2015

20. 20
DevOps with Analytics - SmartiX
5/13/2015

21. 21
How Blueprints are taken into Dev
5/13/2015

22. 22
High level workload split of DevOps
5/13/2015

23. 23
How to cut down “automation” related work?
Use readymade platforms.
5/13/2015
[http://tinyurl.com/deploynow]
[http://tinyurl.com/opextestnow]
• Use strong tools with ease, with very less ramp up time.
• No need to learn Chef, Puppet, Ruby, and can still use their
power.
• No need to rewrite integrations with various cloud vendors and
keep the integrations up to date.
DeployNow, TestNow already has integrations to these tools &
clouds built in! Now you can hit the ground running!

24. 24
All platforms are created from factual experience
5/13/2015
[http://tinyurl.com/deploynow] : Details of how it works
DeployNow platform supports configuration management tools like Chef, Puppet and clouds
such as AWS, Digital Ocean, Linode, openstack, Google Compute.

25. 25
Need of the hour! A must have platform!
5/13/2015
http://tinyurl.com/opextestnow] : Details of how it works
TestNow platform supports configuration management tools like Chef, Puppet and
clouds such as AWS, Digital Ocean, Linode, openstack, Google Compute.

26. 26
Make Ops stronger
5/13/2015
http://www.slideshare.net/SanjuBurkule/real-timebigdataanalyticsmachinelearning13

27. 27
DevOps benefits
5/13/2015

28. 28
Business benefits (notice increase in sales)
5/13/2015

29. 29
If one survey does not help, here is one more survey
5/13/2015

30. 30
Tools Explosion: Which one is right for you?
5/13/2015

31. 315/13/2015
Here are
details of
one tool -
GIT.
Knowing,
choosing
all tools
in a
DevOps
toolchain
takes
time.

32. 32
Opex Software helps on where to start
5/13/2015

33. 33
Identify bottlenecks, slowest operations
Make processes work with each other
5/13/2015

34. 34
Reduce clutter. Standardize.
Larger companies: Establish a DevOps CoE
5/13/2015

35. 35
Implement it right. Take help. Reap value
5/13/2015

36. 36
Benefits of DevOps – Note New Services, Revenue
5/13/2015

37. 37
Engage professionals (hint: Opex Software  )
5/13/2015

38. Start a short communication with us right now! Simply send a
quick email
Email us:
sanju.burkule@opexsoftware.com or
gg@opexsoftware.com
Skypeid: sanju.burkule

39. Thanks to all contributors
Thanks to all the contributors in helping with the images. If any image used here is a direct or indirect copyright violation, please
send an email to info@opexsoftware.com ASAP. It will be removed from the deck ASAP.