This document summarizes a presentation about containers, developer defined data centers, and DevOps. It discusses how containers and Kubernetes can enable developers to define their own infrastructure and release code more frequently. It also notes challenges like finding full-stack engineers and complexity. Finally, it recommends trying the open source OpenEBS project for persistent storage in containers and Kubernetes.

1. Containers: And 3D-C
Containers & Developer Defined Data Centers (D^3, C)
Evan Powell - @epowell101
Containers in Production
Bangalore
April 7, 2017

2. Your 1st curves

3. Your 1st curves

4. Your 1st curves
‘80-’90 ‘90-’00 ‘00-’10 ‘10-’15 ‘80-’90 ‘90-’00 ‘00-’10 ‘10-’15

5. Your 1st curves
‘80-’90 ‘90-’00 ‘00-’10 ‘10-’15 ‘80-’90 ‘90-’00 ‘00-’10 ‘10-’15

7. “Bimodal IT”
“Automation platforms”
“IoT...Innovation”
“Outcome based”
“Start-up ecosystem”

8. “Bimodal IT”
“Automation platforms”
“IoT...Innovation”
“Outcome based”
“Start-up ecosystem”

9. “Bimodal IT”
“Automation platforms”
“IoT,...Innovation”
“Outcome based”
“Start-up ecosystem”
DevOps & DDDC
Holocracy
OpenSource community
Machine learning

10. Who dat?
2001 2008 2016

11. Who dat?
2001 2008 2016
The 2017 case for acceleration in innovation & the persistence of unicorns:
https://venturebeat.com/2017/02/11/were-not-in-a-bubble-were-in-a-revolution/

12. 4:45PM Kubernetes - Google - standards and OCI
Today!
App security Kubernetes
design
Docker in
production
Containers in
prod w Rancher
Containers in
prod w K8S
Containers in
prod w Cl
Foundry
NOW DevOps & Containers: Developer Defined Data Centers &
you
Cloud
alternatives

13. Why DevOps? So what?
https://puppet.com/resources/white-paper/2016-state-of-devops-report

14. Why DevOps? So what?
https://puppet.com/resources/white-paper/2016-state-of-devops-report
SAY DEVOPS
ONE MORE TIME

15. Why DevOps? So what?
https://puppet.com/resources/white-paper/2016-state-of-devops-report
‘80-’90 ‘90-’00 ‘00-’10 ‘10-’15
Revenue per employee, India tech (‘80-
’15)
SAY DEVOPS
ONE MORE TIME

16. Adoption: Bimodal IT: Retailer
Marks and Spencer: Enterprise DevOps presentation ‘15

17. Before After
4 releases per year
45-90 days of testing
Big releases
Monolithic
Large operations teams that limit risk and
developer choice
Hopelessly outclassed vs. Amazon

18. Before After
4 releases per year 5-7 releases per week
45-90 days of testing 1-3 hours of testing
Big releases Tiny releases
Monolithic 12 factor, containerized
Large operations teams that limit risk and
developer choice
NoOps - or DevOps - with a handful of
engineers doing the work of dozens
Hopelessly outclassed vs. Amazon Competitive

19. http://www.slideshare.net/ITRevolution/does-sfo-2016-ross-clanton-and-chivas-nambiar-devops-at-
verizon
First consolidate, then innovate

20. Challenges
People Full stack engineers that are willing to wear a
pager are rare.
Complexity Many simple bricks, tied together, work well; until
they don’t.
OpenSource Communities that grow quickly are great; until
they don’t.
Transparency Everyone knows everything.
Infrastructure as code Ops teams using GitHub.
Failure Daily. Ones you notice & understand are good.
Persistence You need it. To keep going. And to enable the
next wave in analytics - machine learning.

21. People Full stack engineers that are willing to wear a
pager are rare.
Complexity Many simple bricks, tied together, work well; until
they don’t.
OpenSource Communities that grow quickly are great; until
they aren't.
Transparency Everyone knows everything.
Infrastructure as code Ops teams using GitHub.
Failure Daily. Ones you notice & understand are good.
Persistence You need it. To keep going. And to enable the
next wave in analytics - machine learning.
Challenges

22. What projects?
Hard to overstate the promise of
Kubernetes
● Makes real the hype that crazy people were
throwing around about software defined
years ago*
● Part of a move to DevOps & NoOps
○ Which is disrupting all tech vendors
○ Also disrupting most industries
* https://blog.openebs.io/software-defined-storage-finally-37fdffc0e37c

23. The magic of K8S
Manifests
express
intent
stateless

24. Before OpenEBS DevOps workflow broken
Manifests
express
intent
K8S used rarely for apps requiring persistence
because they require brittle tight coupling.
Container 1 Container 2 Container 2
Hard wired connections via plug-in
stateless
stateful
NAS SAN S3 NAS SAN S3
Legacy storage
Flocker, Docker,
EMC plug-ins

25. Manifests
express
intent
stateless stateful
No changes to DevOps workflow even for containers requiring
persistence. Users manifest their intent and the storage and
storage controllers adjust automatically as needed.
Maya
Policy engine
Remote Storage
Local Storage
OpenEBS Storage
Hosts
OpenEBS VSMs
OpenEBS Storage Cluster
APIs
Containers and underlying storage,
local on host or dedicated storage
pods OR remote S3 or EBS storage
all grouped into a storage cloud that
just works. Billing by AWS.
Manifests
express
intent
With OpenEBS the workflow works

26. What if I were you, what would I try to do?
1
2
3
Try OpenEBS - find OSS that you can use & influence
● 0.2 being released in the next few days

27. What if I were you, what would I try to do?
1
2
3
Rage quit
Try OpenEBS - find OSS that you can use & influence
● 0.2 being released in the next few days

28. What if I were you, what would I try to do?
1
2
3
Rage quit
Save the world
Try OpenEBS - find OSS that you can use & influence
● 0.2 being released in the next few days

29. 4:45PM Kubernetes - Google - standards and OCI
Today!
App security Kubernetes
design
Docker in
production
Containers in
prod w Rancher
Containers in
prod w K8S
Containers in
prod w Cl
Foundry
NOW DevOps & Containers: Developer Defined Data Centers &
you
Cloud
alternatives
@epowell101