DevOps aims to reduce conflict between development and operations teams through improved collaboration and automation. It advocates destroying stereotypes, involving both teams in strategy, instilling process discipline, and accelerating workflows with automation. Automation can perform tasks and connect processes to reduce complexity and accelerate application deployment. Successful DevOps requires open communication across the development lifecycle and treating releases as packaged transitions rather than individual components.
6. Stereotypes fuel conflict
• Impatient • Slow to act
• Temperamental • Temperamental
• Careless about changes • Too rigid about changes
• Prima donna artists • Always says “No!”
• Ignorant about the “real world” • Too dumb to understand apps
7. How can you reduce the conflict?
An improved collaboration between Dev& Ops
• Destroy the stereotypes! Get people talking!
• App Dev and Operations CAN join forces
• Involve both in the industrialization strategy
• Instill discipline with flexible process
• Accelerate with automation
• Do it now or executives WILL take action
8. How to make DevOps work
• Talk!
• Measure
• Accept and hide complexity but don’t love it
• Embrace process discipline across the lifecycle
• Start with a common release management process
• Automate release management execution
• Inject rich feedback across the lifecycle
• Change the incentives
• Adapt the organization(s)
• Measure
9. What is automation?
Tools that perform functions otherwise done by humans
Task Execution
• Individual tasks
• Repetitive tasks are candidates
Process Flow
• Connects tasks and decisions
• Workload automation and RBA
Decision Trigger
• Analytics (not just monitoring)
• When and why to take action
10. “Fast and Accurate” is not a paradox
• “Process = Bureaucracy”
is a misconception
• Discipline becomes
oppressive only
if taken too far
• Good process
enhances agility
• Automation
further
accelerates
execution
11. Agile Dev meets Agile Ops
Traditional Leaving Welcome To
Transition Dev Ops
Come Back Soon! Drive Safe!
Release Management is Too Slow
Agile Leaving Welcome To
Transition Dev Ops
Come Back Soon! Drive Safe!
Streamlined Release Management
12. The Typical Life Cycle Is Broken
Ops
App
EA Dev QA Ops
• One-way flow doesn’t allow for continual improvement
• Information developed early is lost when given to Ops
• Ops must resort to reverse engineering (a wasteful effort)
• Release from App Dev to Operations is a huge problem
• Thus, also a huge opportunity
• Cultural barriers must fall but tools must also evolve
• New tool developments are promising
13. Collaborate Across The Life Cycle
App
EA Dev QA Ops
Agile Process
• Feedback makes it a true lifecycle with continual improvement
• Automation based upon apps span the lifecycle
• Apps become adaptive like infrastructure now is
• Information is preserved and put to good use everywhere
• A well-managed portfolio emerges from people communicating!
14. Package releases for speed & accuracy
Move packages, not individual components
Development Staging Production
Transitions
? of
Components
Package
Transitions
of a
Package
15.
16. The evolution of trust and technology
Trust Gap
Automation
Silver Bullet
Automation Evolution
Manual
Ability
Trust
Evolution
YOU ARE HERE
17. Will automation replace my job?
• Don’t fear automation … embrace it!
• This is the future … be a part of the future!
• History has not been kind to those who
resist the inevitability of progress!
18.
19. Hot new roles emerge
• Business relationship manager
• Automation architect
• Service designer
• Service manager
• Vendor manager
• Process owner
20. Who does DevOps? …. Who automates?
Everyone does, but who “owns” it?
21. Summary
Pursue DevOps automation to lead industrialized IT
• Embrace the new reality of industrialized IT
• Talk to each other!
• Abandon the stereotypes of all parties
• Abandon the love affair with complexity – your job is to simplify
• Streamline the handoff from Dev to Ops (agile lifecycle)
• Get serious about process discipline, but don’t go too far!
• Institute systems engineering practices across the entire lifecycle
28. Role of DevOps Infrastructure Teams
Build Automation
Tool-chains
32 http://www.urbancode.com/html/resources/webinars/Building_a_
DevOps_Toolchain.html
29. Role of DevOps Infrastructure Teams
Build Automation
Tool-chains
• Product Mindset
• Delivered as a service
• Models
- Post Office
- Some assembly required
33 http://www.urbancode.com/html/resources/webinars/Building_a_
DevOps_Toolchain.html
30. Reduce Tool per Siloism
• Common backlogs
We’re soo different in
• Common builds our needs, we need our
own thing
• Common IaaS
• Common deployments
34
33. Urbancode References
http://urbancode.com/resources
White Papers
– Enterprise CD Maturity Model
– Lean Build & Deployment Automation
– Deployment Automation Basics
Stay in touch:
Blogs.urbancode.com
Twitter:@UrbanCodeSoft, @EricMinick
37
34. Yes, we sell DevOps oriented products
• uBuild
– Build automation and CI for the hard problems
• uDeploy
– Deployment and release management
• uProvision
– Spins up virtual environments. Integrated with
VMWare, Azure and EC2
• uRelease
– Release & Environment management / planning
38