1 / 27

Bridging the Gap

Bridging the Gap. OpenStack for VMware administrators in the context of a fictional use case. Presenters. Kenneth Hui Technology Evangelist Rackspace Twitter: @hui_kenneth. Scott Lowe Engineering Architect VMware, Inc. Twitter: @ scott_lowe. Agenda. Agenda.

wyome
Download Presentation

Bridging the Gap

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Bridging the Gap OpenStack for VMware administrators in the context of a fictional use case

  2. Presenters Kenneth Hui Technology Evangelist Rackspace Twitter: @hui_kenneth Scott Lowe Engineering Architect VMware, Inc. Twitter: @scott_lowe

  3. Agenda

  4. Agenda • Up first: A tale of two workloads • Fictitious customer use case: how we’ll structure our discussion • Proposed solution: looking at OpenStack and VMware together • Q&A

  5. A tale of two workloads

  6. Workload dictates architecture

  7. Traditional design principles Monolithic architecture Stateful Services Operator focused

  8. Design goal: Resilient infrastructures

  9. Cloud-native design principles Distributed architecture Stateless Services Developer focused

  10. Design assumption: Fragile infrastructures

  11. We architect clouds for rapid scale

  12. Chaos and failures are inevitable at scale

  13. So design for failure

  14. This translates into certain design guidelines Let the application handle its own resiliency Build loosely-coupled distributed systems Use the scale out approach instead of the scale-up approach (scale horizontally not vertically) Choose cattle over pets

  15. Fictitious customer use case

  16. Our customer is Acme Corporation • Wile E. Coyote is a huge customer, and business is booming (no pun intended) • Acme runs most of their apps on vSphere, including some Oracle DBs • IT recently tasked with building out environment for new mobile applications • Been using AWS for prototyping • Want to bring that in-house but maintain “AWS-like” experience • Plan to leverage cloud-native application architectures

  17. Proposed solution

  18. Multi-hypervisor OpenStackarchitecture

  19. vSphere in OpenStack

  20. Cloud Controller Cloud Controller Workload zones Compute Node Compute Node/KVM +N vCenter Oracle Host Aggregate App Host Aggregate KVM VMs KVM Host Aggregate +N +N ESXi ESXi ESXi VMs ESXi VMs Virtual Computer Node

  21. Networking Physical Network(131.107.x.x/16) • Leverage VMware NSX with OpenStack Neutron for cross-hypervisor networking services • Acme developers can spin up their own isolated logical networks for development and prototyping • Production workloads can leverage existing IP address space for seamless integration into the rest of the network yet remain isolated from each other Logical Network(192.168.1.x/24) Logical Network(131.107.2.x/24) Logical Network(131.107.1.x/24) Logical Network(192.168.1.x/24)

  22. Virtual Computer Node Cloud Controller vSphere storage in OpenStack ESXi ESXi vCenter Compute Node ESXI VMs ESXI VMs Cinder Volume Cinder Volume Cinder Node

  23. Operational challenges of this solution • Must build and maintain multiple Glance images • One image needed for each hypervisor in the OpenStack environment • Image metadata associates the image with the appropriate hypervisor • Development/testing on KVM but production on vSphere can introduce issues • Networking could be challenging without VMware NSX (or other cross-platform Neutron-capable solution) • Organizational and staff readiness to support multiple hypervisors (“Layer 8” concerns)

  24. Summary

  25. Key takeaways to remember • OpenStack and VMware’s products (including vSphere) are complementary in many ways • Workload dictates architecture; different requirements result in different architectures • Use the right tool for the job

  26. Questions?

  27. THANK YOU! Ken Hui ken.hui@rackspace.com Scott Lowe slowe@vmware.com

More Related