containers
play

Containers Kill or Cure for OpenStack? Mark Smith Pete Chadwick - PowerPoint PPT Presentation

Containers Kill or Cure for OpenStack? Mark Smith Pete Chadwick Senior Product Market Manager Director of Product Management SUSE OpenStack Cloud Cloud & Systems Management Why are containers such a hot topic? This is stuff all of us


  1. Containers Kill or Cure for OpenStack? Mark Smith Pete Chadwick Senior Product Market Manager Director of Product Management SUSE OpenStack Cloud Cloud & Systems Management

  2. Why are containers such a hot topic? This is stuff all of us know, right? “Container technologies are now available on every major - public and private cloud platform” “Support for containers will only grow throughout 2017” - “Container technologies allow enterprises to create highly - differentiated apps and services faster, with better quality and geographic reach, to create compelling customer experiences” “Container Strategies Are Critical To Digital Business” - Source: Forrester - Vendor Landscape: Container solutions for cloud-native applications. Jan 30 th 2017 2

  3. OpenStack community’s view of containers Containers are top emerging technology that interests OpenStack users * - - OpenStack users are adopting containers 3x faster than rest of enterprise market ** Magnum in top 2 projects of highest interest to OpenStack users * - Which emerging technologies interest OpenStack Users? 3 Source: * OpenStack user survey, April 2017. ** 451 Research, Barcelona OpenStack Summit Oct 2016

  4. Where do containers fit into OpenStack? Business guy OpenStack guy 4 4

  5. Two types of containers Application Delivery Application Custom Micro Service Applications Containers Kubernetes / Magnum Private Cloud / IaaS OpenStack Cloud Software Service Software Defined Everything Containers Virtualization Storage Networking Hypervisors SDS SDN and NFV Operating System Linux Physical Infrastructure: Server, Switches, Storage 5

  6. OK. Let’s talk about SERVICE containers. How do you build OpenStack with service containers? Why would you do it? Operations guy OpenStack guy 6 6

  7. Tell me more about APPLICATION containers. How does OpenStack fit in? What would a typical use case look like? Development guy OpenStack guy 7 7

  8. Kubernetes as a Service Custom Micro Services App Open Open Open Open Container Container Container Container Linux Linux Linux Linux IaaS Runtime Runtime Runtime Runtime Heat Kubernetes / Magnum VM VM VM VM VM VM VM Linux Linux Linux Linux Linux Linux Linux OpenStack APIs Software Defined Everything Virtualization Storage Networking Hypervisors SDS SDN and NFV Operating System Linux Physical Infrastructure: Server, Switches, Storage OpenStack Cloud 8

  9. All right – but where are we going next? Will all workloads end up being containerized? Business guy OpenStack guy 9 9

  10. OpenStack is the ideal integration platform Bare metal Virtualized Containerized workloads workloads workloads Private Cloud / IaaS OpenStack Cloud Software Software Defined Everything Virtualization Storage Networking Hypervisors SDS SDN and NFV Operating System Linux Physical Infrastructure: Server, Switches, Storage 10

  11. OK. Let’s take an even longer range view? What does the future look like for Containers and OpenStack? Dev, Ops or Business guy OpenStack guy 11 1 1

  12. OpenStack provides the blueprint for SDI Application Delivery Custom Micro Service Applications Platform as a Service Kubernetes / Magnum Cloud Foundry Management Operations, Monitoring and Private Cloud / IaaS Patching OpenStack Cloud Software Cluster Public Cloud Deployment Software Defined Everything Virtualization Storage Networking Orchestration Hypervisors SDS SDN and NFV • Heat • Kubernetes Operating System Linux Physical Infrastructure: Server, Switches, Storage 12

  13. SUSE OpenStack Cloud Agility, innovation and faster time to value Visit SUSE at Booth B6 13 1 3

  14. 14 14 1 4

  15. General Disclaimer This document is not to be construed as a promise by any participating company to develop, deliver, or market a product. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. SUSE makes no representations or warranties with respect to the contents of this document, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. The development, release, and timing of features or functionality described for SUSE products remains at the sole discretion of SUSE. Further, SUSE reserves the right to revise this document and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. All SUSE marks referenced in this presentation are trademarks or registered trademarks of Novell, Inc. in the United States and other countries. All third- party trademarks are the property of their respective owners. 15 15

Recommend


More recommend