SlideShare a Scribd company logo

Openstack Summit Container Day Keynote

•
•
Boyd Hemphill
Boyd Hemphill

Why do containers suddenly matter so much when they have been around since 1998? Take a look at the potential of OpenStack's Magnum, Murano and Nova-Docker in the context leveraging the incredible interest in Linux Containers brought about by Docker. Check out www.stackengine.com to learn more about our excellent container management solution.

Related slideshows

Bug smash day magnum
Bug smash day magnumBug smash day magnum
Bug smash day magnum
 
AWS Summit Singapore 2019 | Autoscaling Your Kubernetes Workloads
AWS Summit Singapore 2019 | Autoscaling Your Kubernetes WorkloadsAWS Summit Singapore 2019 | Autoscaling Your Kubernetes Workloads
AWS Summit Singapore 2019 | Autoscaling Your Kubernetes Workloads
 
Kubernetes Day 2017 - Build, Ship and Run Your APP, Production !!
Kubernetes Day 2017 - Build, Ship and Run Your APP, Production !!Kubernetes Day 2017 - Build, Ship and Run Your APP, Production !!
Kubernetes Day 2017 - Build, Ship and Run Your APP, Production !!
 
1 of 58
Download to read offline
Open Containers of Champagne OpenStack Magnum Boyd Hemphill Director of Evangelism @behemphi @stackengine
Background
Background Oracle Developer, MySQL DBA, PHP Developer, System Architect, DevOps Director (snickering encouraged), Evangelist
Background Oracle Developer, MySQL DBA, PHP Developer, System Architect, DevOps Director (snickering encouraged), Evangelist Build Communities (Docker Austin, Austin DevOps)
Background Oracle Developer, MySQL DBA, PHP Developer, System Architect, DevOps Director (snickering encouraged), Evangelist Build Communities (Docker Austin, Austin DevOps) Founded Container Days 2015. Austin, Boston, San Fran, Dallas
Why?
Walk away from this session thinking about uses for containers and what Magnum, Murano, nova- docker, et. al. could mean for the future of OpenStack.
Perspective
Perspective P = R - C
Perspective P = R - C If C = 0, you are out of business.
Perspective P = R - C If C = 0, you are out of business. R has no ceiling!
Perspective P = R - C If C = 0, you are out of business. R has no ceiling! Features = $ http://goo.gl/VUmbwP http://goo.gl/2Yq2Mg
Container v. VM
Container v. VM A VM is a full copy of on an entire computer running as software via a hypervisor
Container v. VM A VM is a full copy of on an entire computer running as software via a hypervisor A container is a slice of the kernel
Container v. VM A VM is a full copy of on an entire computer running as software via a hypervisor A container is a slice of the kernel Executive Summary: The lack of extra layers means big opportunity
Language
Docker != Containers FreeBSD Jail (1998) - CPU, Memory, Disk, !IO Solaris Zones (2005) CPU, Memory, Disk, IO OpenVZ (2005) CPU, Memory, Disk, IO LXC (2008) CPU, Memory, Disk, IO Docker (2013) CPU, Memory, !Disk, !IO Rocket (2014) ???
Docker != Container Containers in Production - Pantheon (LXC)
Docker != Container Containers in Production - Pantheon (LXC) Containers in build pipelines - Travis CI (OpenVZ)
Docker != Container Containers in Production - Pantheon (LXC) Containers in build pipelines - Travis CI (OpenVZ) Docker is, simply, linux containers for mere mortals
Magnum seeks to include container technologies other than Docker. Think broadly about the technology, not the tool.
Use Cases
Use Cases - SDLC Development Build / CI QA Production
Development
Use Case - Dev Disposable Dev Env New Devs productive 1st day
Use Case - Dev Disposable Dev Env New Devs productive 1st day Innovation Increase
Use Case - Dev Disposable Dev Env New Devs productive 1st day Innovation Increase Feature Velocity Increase
Build / CI
Build / CI Test more system permutations
Build / CI Test more system permutations Increased parallelism = increased innovation
Build / CI Test more system permutations Increased parallelism = increased innovation Increased parallelism = increased feature velocity
Quality Assurance
Quality Assurance Black Box Testing
Quality Assurance Black Box Testing Compliance instead of Governance Security Performance Functional
Quality Assurance Black Box Testing Compliance instead of Governance Security Performance Functional Increases Feature Velocity
Operations
Operations Process Density
Operations Process Density Ants not Cattle
Operations Process Density Ants not Cattle New Capacity Planning thinking
Bonus
System Architecture Micro Services mean Micro teams
System Architecture Micro Services mean Micro teams
System Architecture Micro Services mean Micro teams Increased Feature Velocity Lasting competitive business advantage
Batteries Not Included
Batteries Not Included Docker ~= Hypervisor and not much else
Batteries Not Included Docker ~= Hypervisor and not much else Further symmetry !Storage (Swift, Cinder) !Networking (Neutron) !Identity (Keystone)
Batteries Not Included Docker ~= Hypervisor and not much else Further symmetry !Storage (Swift, Cinder) !Networking (Neutron) !Identity (Keystone) Nascent Ecosystem
OpenStack, via Magnum, has the potential to provide excellent answers to very difficult questions about container workloads and application topologies
Parting Thoughts
Developer adoption of Docker is only valuable as a first step. There is not enough benefit from it alone to justify the effort, it must inform system architecture and production operations over time.
Developer adoption of Docker is only valuable as a first step. There is not enough benefit from it alone to justify the effort, it must inform system architecture and production operations over time. Docker’s system architecture ramifications have the potential to provide a significant and lasting competitive business advantage
Developer adoption of Docker is only valuable as a first step. There is not enough benefit from it alone to justify the effort, it must inform system architecture and production operations over time. Docker’s system architecture ramifications have the potential to provide a significant and lasting competitive business advantage Unlike most improvements from DevOps thinking, container adoption is Dev/QA driven since the greatest benefits are from system architecture. This fits existing common OpenStack use cases.
Developer adoption of Docker is only valuable as a first step. There is not enough benefit from it alone to justify the effort, it must inform system architecture and production operations over time. Docker’s system architecture ramifications have the potential to provide a significant and lasting competitive business advantage Unlike most improvements from DevOps thinking, container adoption is Dev/QA driven since the greatest benefits are from system architecture. This fits existing common OpenStack use cases. Horses are starting to become unicorns. Evolve or die.
Developer adoption of Docker is only valuable as a first step. There is not enough benefit from it alone to justify the effort, it must inform system architecture and production operations over time. Docker’s system architecture ramifications have the potential to provide a significant and lasting competitive business advantage Unlike most improvements from DevOps thinking, container adoption is Dev/QA driven since the greatest benefits are from system architecture. This fits existing common OpenStack use cases. Horses are starting to become unicorns. Evolve or die. The last point is FUD. “Consider how to evolve or die,” is the real truth.
Colophon
Unicorn Case Pantheon/Rackspace blog: http://goo.gl/93steF Note the date: October 7th, 2013 (This is LXC) Amazing video presentation: http:// goo.gl/gRkKGN Docker makes this easier to consider in our own contexts
Reading The Phoenix Project - Kim (Lean/tech) The Lean Startup - Reis (Lean) The Goal - Goldratt (Theory of Constraints) It’s not Luck - Goldratt (Theory of Constraints) Good to Great - Collins (Culture) The No Asshole Rule - Sutton (Culture) Continuous Deliver - Humble (*) (deep tech) The Lean Enterprise - Humble (*) (Lean) Twelve Factor - http://12factor.net (deep tech)

More Related Content

Openstack Summit Container Day Keynote

  • 1. Open Containers of Champagne OpenStack Magnum Boyd Hemphill Director of Evangelism @behemphi @stackengine
  • 3. Background Oracle Developer, MySQL DBA, PHP Developer, System Architect, DevOps Director (snickering encouraged), Evangelist
  • 4. Background Oracle Developer, MySQL DBA, PHP Developer, System Architect, DevOps Director (snickering encouraged), Evangelist Build Communities (Docker Austin, Austin DevOps)
  • 5. Background Oracle Developer, MySQL DBA, PHP Developer, System Architect, DevOps Director (snickering encouraged), Evangelist Build Communities (Docker Austin, Austin DevOps) Founded Container Days 2015. Austin, Boston, San Fran, Dallas
  • 7. Walk away from this session thinking about uses for containers and what Magnum, Murano, nova- docker, et. al. could mean for the future of OpenStack.
  • 10. Perspective P = R - C If C = 0, you are out of business.
  • 11. Perspective P = R - C If C = 0, you are out of business. R has no ceiling!
  • 12. Perspective P = R - C If C = 0, you are out of business. R has no ceiling! Features = $ http://goo.gl/VUmbwP http://goo.gl/2Yq2Mg
  • 14. Container v. VM A VM is a full copy of on an entire computer running as software via a hypervisor
  • 15. Container v. VM A VM is a full copy of on an entire computer running as software via a hypervisor A container is a slice of the kernel
  • 16. Container v. VM A VM is a full copy of on an entire computer running as software via a hypervisor A container is a slice of the kernel Executive Summary: The lack of extra layers means big opportunity
  • 18. Docker != Containers FreeBSD Jail (1998) - CPU, Memory, Disk, !IO Solaris Zones (2005) CPU, Memory, Disk, IO OpenVZ (2005) CPU, Memory, Disk, IO LXC (2008) CPU, Memory, Disk, IO Docker (2013) CPU, Memory, !Disk, !IO Rocket (2014) ???
  • 19. Docker != Container Containers in Production - Pantheon (LXC)
  • 20. Docker != Container Containers in Production - Pantheon (LXC) Containers in build pipelines - Travis CI (OpenVZ)
  • 21. Docker != Container Containers in Production - Pantheon (LXC) Containers in build pipelines - Travis CI (OpenVZ) Docker is, simply, linux containers for mere mortals
  • 22. Magnum seeks to include container technologies other than Docker. Think broadly about the technology, not the tool.
  • 24. Use Cases - SDLC Development Build / CI QA Production
  • 26. Use Case - Dev Disposable Dev Env New Devs productive 1st day
  • 27. Use Case - Dev Disposable Dev Env New Devs productive 1st day Innovation Increase
  • 28. Use Case - Dev Disposable Dev Env New Devs productive 1st day Innovation Increase Feature Velocity Increase
  • 30. Build / CI Test more system permutations
  • 31. Build / CI Test more system permutations Increased parallelism = increased innovation
  • 32. Build / CI Test more system permutations Increased parallelism = increased innovation Increased parallelism = increased feature velocity
  • 35. Quality Assurance Black Box Testing Compliance instead of Governance Security Performance Functional
  • 36. Quality Assurance Black Box Testing Compliance instead of Governance Security Performance Functional Increases Feature Velocity
  • 40. Operations Process Density Ants not Cattle New Capacity Planning thinking
  • 41. Bonus
  • 44. System Architecture Micro Services mean Micro teams Increased Feature Velocity Lasting competitive business advantage
  • 46. Batteries Not Included Docker ~= Hypervisor and not much else
  • 47. Batteries Not Included Docker ~= Hypervisor and not much else Further symmetry !Storage (Swift, Cinder) !Networking (Neutron) !Identity (Keystone)
  • 48. Batteries Not Included Docker ~= Hypervisor and not much else Further symmetry !Storage (Swift, Cinder) !Networking (Neutron) !Identity (Keystone) Nascent Ecosystem
  • 49. OpenStack, via Magnum, has the potential to provide excellent answers to very difficult questions about container workloads and application topologies
  • 51. Developer adoption of Docker is only valuable as a first step. There is not enough benefit from it alone to justify the effort, it must inform system architecture and production operations over time.
  • 52. Developer adoption of Docker is only valuable as a first step. There is not enough benefit from it alone to justify the effort, it must inform system architecture and production operations over time. Docker’s system architecture ramifications have the potential to provide a significant and lasting competitive business advantage
  • 53. Developer adoption of Docker is only valuable as a first step. There is not enough benefit from it alone to justify the effort, it must inform system architecture and production operations over time. Docker’s system architecture ramifications have the potential to provide a significant and lasting competitive business advantage Unlike most improvements from DevOps thinking, container adoption is Dev/QA driven since the greatest benefits are from system architecture. This fits existing common OpenStack use cases.
  • 54. Developer adoption of Docker is only valuable as a first step. There is not enough benefit from it alone to justify the effort, it must inform system architecture and production operations over time. Docker’s system architecture ramifications have the potential to provide a significant and lasting competitive business advantage Unlike most improvements from DevOps thinking, container adoption is Dev/QA driven since the greatest benefits are from system architecture. This fits existing common OpenStack use cases. Horses are starting to become unicorns. Evolve or die.
  • 55. Developer adoption of Docker is only valuable as a first step. There is not enough benefit from it alone to justify the effort, it must inform system architecture and production operations over time. Docker’s system architecture ramifications have the potential to provide a significant and lasting competitive business advantage Unlike most improvements from DevOps thinking, container adoption is Dev/QA driven since the greatest benefits are from system architecture. This fits existing common OpenStack use cases. Horses are starting to become unicorns. Evolve or die. The last point is FUD. “Consider how to evolve or die,” is the real truth.
  • 57. Unicorn Case Pantheon/Rackspace blog: http://goo.gl/93steF Note the date: October 7th, 2013 (This is LXC) Amazing video presentation: http:// goo.gl/gRkKGN Docker makes this easier to consider in our own contexts
  • 58. Reading The Phoenix Project - Kim (Lean/tech) The Lean Startup - Reis (Lean) The Goal - Goldratt (Theory of Constraints) It’s not Luck - Goldratt (Theory of Constraints) Good to Great - Collins (Culture) The No Asshole Rule - Sutton (Culture) Continuous Deliver - Humble (*) (deep tech) The Lean Enterprise - Humble (*) (Lean) Twelve Factor - http://12factor.net (deep tech)