This document discusses opportunities for Ansible and partners in the DevOps market. It covers topics like cloud natives inventing DevOps practices, Conway's Law relating organizational structure to system design, infrastructure as code, immutable infrastructure use cases, microservices architecture, containers, orchestration, and culture change aspects of DevOps transformations. The document analyzes various technology trends and entry points where Ansible could sell solutions to help organizations adopt DevOps practices.

1. 10.20.2005
DevOps Market / Opportunity for Ansible & Partners
James Governor, analyst and founder
Ansible Partner Summit, February 2016

2. 2
About Me
@monkchips

3. 3
About Us

4. 4

5. 5
Disruption!

6. 6
Foraging vs Farming

7. 7
Fragmentation is the new Normal

8. 8
Explosion of Forms

9. 9

10. 10
Cloud Natives Invented DevOps
So Learn From Them

11. 11
Conway’s Law
"Any organization that designs a system (defined more broadly here than just
information systems) will inevitably produce a design whose structure is a copy of the
organization's communication structure."

12. 12
Tapas Table Dev Teams

13. 13
Continuous Integration

14. 14
Infrastructure as Code, DevOps as Tooling

15. 15

16. 16
Immutable Infrastructure Use Cases
builds
cloud native as a thing
configuring databases - Big Data
provisioning cloud and virtual infrastructure
Provisioning servers
deploying application code
managing SSH keys
patching
setting up web servers
testing changes

17. 17
Monitoring: the new APM

18. 18
DevOps Enterprise-Defined
“DevOps is a way to make the developer experience better. How can we help
developers to build better apps? It’s about putting more power in the hands of
the developer via automation.”
Jay Snyder, Aetna director of platform engineering

19. 19
PaaS – Enterprise Defined
People make the difference. either in successfully utilising available
technology, they sharpen available services within the framework to better
serve the customer.
We changed the DNA of the people, their attitude and styles.
PaaS means a standardised reliable predictable platform - allowing
developers to shorten the delivery cycle. We hire people with the right
sparkle in their eyes."
- Mark Willemse, ING Bank

20. 20
So?

21. 21
The Rise of Micro-services
“The microservice architectural style is an approach to developing a single application
as a suite of small services, each running in its own process and communicating with
lightweight mechanisms, often an HTTP resource API. These services are built around
business capabilities and independently deployable by fully automated deployment
machinery. There is a bare minimum of centralized management of these services,
which may be written in different programming languages and use different data
storage technologies.”
Martin Fowler, Thoughtworks, March 2014

22. 22
Cattle vs Pets

23. 23
Failure is Expected

24. 24
Containers
Convenient
Composable
Disposable
Immutable
Standard - OCF
Production Ready?

25. 25
Orchestration

26. 26
Just Culture

27. 27
With Responsibility

28. 28
Empathy and Soft Skills

29. 29
ALL THE ENTRY POINTS!
Agile
Big Data
CI
Cloud Enablement – refactoring and onboarding
Culture. DevOps is a Reorg. The Classic 1:10
A Seat at the Tapas Table
DevOps
Docker
Microservices
PaaS – container mixed messages
Security through immutability
Selling into the Red Hat base
VMware – embrace and extend. Containers again!