The document is a presentation by Mike Kavis on deriving value from enterprise DevOps. It discusses how DevOps aims to build better quality software faster and more reliably through collaboration between development and operations teams. It outlines some common misperceptions of DevOps and explains that the most fundamental goal is to remove waste from processes like redundant work and wait times. The presentation also examines what is driving DevOps from both a business perspective of faster deployments and fewer failures, and a technology perspective of new cloud-based architectures requiring more automation and collaboration across teams. It argues that DevOps needs a culture shift toward continuous improvement and removing waste from systems through automation.

1. © 2013 Cloud Technology Partners, Inc. / Confidential
1
Deriving Value from Enterprise DevOps
Cloud Computing Expo – NYC
June 10, 2014

2. © 2013 Cloud Technology Partners, Inc. / Confidential
2
Mike Kavis
About the Presenter
VP / Principal Architect, Cloud Technology Partners
@madgreek65
mike.kavis@cloudtp.com

3. © 2013 Cloud Technology Partners, Inc. / Confidential
3
WTF is DevOps?
DevOps Gut Check

4. © 2013 Cloud Technology Partners, Inc. / Confidential
4
A culture shift or movement that encourages
great collaboration to……
“Build Better Quality Software Faster & More Reliably”
DevOps Gut Check

5. © 2013 Cloud Technology Partners, Inc. / Confidential
5
Common
Misperceptions of
DevOps
DevOps Gut Check

9. © 2013 Cloud Technology Partners, Inc. / Confidential
9
The most fundamental goal of
DevOps – Remove waste
DevOps Gut Check

10. © 2013 Cloud Technology Partners, Inc. / Confidential
10
Examples of Waste
• Redundant work across silos
• Wait time
• Provisioning times
• Inconsistent environments
• Manual testing processes
• A domain expert as a bottleneck
• Long approval processes
DevOps Gut Check

11. © 2013 Cloud Technology Partners, Inc. / Confidential
11
What is Driving DevOps – Business Perspective
High Performance IT Shops:
• Deploy 30 times more with
50% fewer failures
• Strong business performance,
helping to boost productivity,
profitability, and market share
• Employee satisfaction
• Competitive advantage

12. © 2013 Cloud Technology Partners, Inc. / Confidential
12
Old Way – The Dictatorship
What is Driving DevOps – Technology Perspective
Pre-Cloud
- Lack of choices
- Vertical scale
- Long procurement processes
- Vendor supported infrastructure
- Standard n-tier architectures

13. © 2013 Cloud Technology Partners, Inc. / Confidential
13
New Way – Sovereignty Model
What is Driving DevOps – Technology Perspective
Cloud
- Developer chooses
- Horizontal scale
- Provisioning in minutes
- COTS infrastructure (virtual)
- Distributed architectures

14. © 2013 Cloud Technology Partners, Inc. / Confidential
14
Old Way – Maslow’s Hammer
What is Driving DevOps – Technology Perspective
Pre-Cloud
- If all you have is a hammer…..
- One single database solution
- Typically a SQL DBMS on a big server
- Scales Vertically
- Centralized

15. © 2013 Cloud Technology Partners, Inc. / Confidential
15
New Way – Freedom of Choice
What is Driving DevOps – Technology Perspective
Cloud
- Many ways to skin a cat
- Many different database technologies
- Many different size servers
- Scales horizontally
- Distributed
Source: http://aws.amazon.com/solutions/case-studies/parse/

16. © 2013 Cloud Technology Partners, Inc. / Confidential
16
Cloud architectures require…
New Breed of Architectures Require a New Operating Model
- Centralized logging solutions
- Proactive monitoring (Nagios is not enough)
- Enhanced security design
- More regulatory controls
- Cost optimization strategies
- Stateless architectures
- High levels of automation
- Better collaboration between domain experts (app, ops, security)

17. © 2013 Cloud Technology Partners, Inc. / Confidential
17
Old Way – Man Behind the Curtain
New Breed of Architectures Require a New Operating Model
- Tribal Knowledge
- Reactive mode – Fire Fighting
- Fragile software
- Big disruptive releases
- Long wait for enhancements
- Inefficient processes
- Bugs in new code carried forward
- Ops stuck holding the bag

18. © 2013 Cloud Technology Partners, Inc. / Confidential
18
New Way – Intelligent Services
New Breed of Architectures Require a New Operating Model
- Collaborative
- Proactive mode – Fire Prevention
- Stable software
- Small, frequent releases
- Fast to market
- Waste removed from processes
- Bugs not allowed in build
- Shared Accountability

19. © 2013 Cloud Technology Partners, Inc. / Confidential
19
Modern Architectures are harder to manage
and scale using traditional processes
The Dilemma
Cloud
Provider
Customers
Employees
Application
Source: Compuware
XML/SOAPhttp SQL TCIP/IP

20. © 2013 Cloud Technology Partners, Inc. / Confidential
20
Shift From Product-Centric to Service-Centric
On Premise
• Up front Licenses
• 18-20% Annual Maintenance
• IT Cost/Risk on Customer
• SLA on Customer
• Remote troubleshooting
• 18-36 Month Release Cycle
• Highly Customized
• Upgrade Cost/Risk on Customer
• Cost of Trained Staff on Customer
ASP/Cloud Washed
• License and Annual Maintenance
• A la carte App/Hosting Services
• IT Cost/Risk Shared
• Manual Scaling
• SLA Shared
• 18-36 Month Release Cycle
• Moderately Customized, Integration
Challenged
• Periodic Upgrade Cost/Risk Shared
• Highly Skilled Staff for Manual Changes
and One Off Issues
• Ongoing Debate on Shared Roles
SaaS/True Cloud
• Subscription Including Maintenance
• Continuous Operations Services
Included
• IT Cost/Risk on Provider
• Autoscaling
• Availability and Performance SLA on
Provider
• Frequent Releases/Upgrades
• Configurable Customization and
Integration Toolkit
• Self-Service and Dashboards
• Automation and Proactive Monitoring
Product Delivery Service Delivery

21. © 2013 Cloud Technology Partners, Inc. / Confidential
21
What Needs to Change?
Traditional Challenge – Dev needs speed, Ops needs control
Speed
APIs
Security
Compliance
Availability
Auditing
The Great Balancing Act

22. © 2013 Cloud Technology Partners, Inc. / Confidential
22
What needs to Change?
Old Way New Way
Done means
“It’s an OPS problem now”
A service is never done
until it is turned off
“The best developers are the
ones who get the call when
the system goes down”

23. © 2013 Cloud Technology Partners, Inc. / Confidential
23
What needs to Change?
Old Way = Ops as a Bottleneck

24. © 2013 Cloud Technology Partners, Inc. / Confidential
24
What needs to Change?
New Way = Ops as a Service Provider
Automated/
Self Service
Provisioning
Asset/
Upgrade/ Patch
Management
Monitoring/
Logging
Services
Availability
Management
Performance/
Capacity
Management
Security &
Compliance
Services

25. © 2013 Cloud Technology Partners, Inc. / Confidential
25
Focus on Removing Waste from the System
Remove waste first, then automate
Source: http://nicholsoncartoons.com.au/2012-07-04-deloitte-report-warns-on-port-infrastructure.html

26. © 2013 Cloud Technology Partners, Inc. / Confidential
26
Focus on Removing Waste from the System
Don’t automate what you don’t understand
Source: http://nicholsoncartoons.com.au/2012-07-04-deloitte-report-warns-on-port-infrastructure.html

27. © 2013 Cloud Technology Partners, Inc. / Confidential
27
Continuous Operations:
“Characteristics of a data-processing system that reduce
or eliminate the need for planned downtime, such as
scheduled maintenance” - Gartner
Build a Culture of Continuous Improvement
IT Performance

28. © 2013 Cloud Technology Partners, Inc. / Confidential
28
Automation and Orchestration Logging, Monitoring and Metrics
The DevOps Toolkit
Implement
Feedback

29. © 2013 Cloud Technology Partners, Inc. / Confidential
29
At the end of the Day,
DevOps only matters if the
business needs are met
Keep Your Eye on the Prize

30. © 2013 Cloud Technology Partners, Inc. / Confidential
30
Recommended Reading

31. © 2013 Cloud Technology Partners, Inc. / Confidential
31
Questions?
Thank you for your time and interest.
Mike Kavis VP / Principal Architect,
Cloud Technology Partners
@madgreek65 / mike.kavis@cloudtp.com