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

Bridging the Gap

  • Upload
    wyome

  • View
    22

  • Download
    0

Embed Size (px)

DESCRIPTION

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. - PowerPoint PPT Presentation

Citation preview

Page 1: Bridging the Gap

OpenStack for VMware administrators in the context of a fictional use case

Bridging the Gap

Page 2: Bridging the Gap

#rackstackatl

Presenters

Kenneth HuiTechnology EvangelistRackspaceTwitter: @hui_kenneth

Scott LoweEngineering ArchitectVMware, Inc.Twitter: @scott_lowe

Page 3: Bridging the Gap

#rackstackatl

Agenda

Page 4: Bridging the Gap

#rackstackatl

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

Page 5: Bridging the Gap

#rackstackatl

A tale of two workloads

Page 6: Bridging the Gap

#rackstackatl

Workload dictates architecture

Page 7: Bridging the Gap

#rackstackatl

Traditional design principles

Monolithic architecture

Stateful Services

Operator focused

Page 8: Bridging the Gap

#rackstackatl

Design goal: Resilient infrastructures

Page 9: Bridging the Gap

#rackstackatl

Cloud-native design principles

Distributed architecture

Developer focusedStateless Services

Page 10: Bridging the Gap

#rackstackatl

Design assumption: Fragile infrastructures

Page 11: Bridging the Gap

#rackstackatl

We architect clouds for rapid scale

11

Page 12: Bridging the Gap

#rackstackatl

Chaos and failures are inevitable at scale

12

Page 13: Bridging the Gap

#rackstackatl

So design for failure

13

Page 14: Bridging the Gap

#rackstackatl

• 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

This translates into certain design guidelines

Page 15: Bridging the Gap

#rackstackatl

Fictitious customer use case

Page 16: Bridging the Gap

#rackstackatl

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

Page 17: Bridging the Gap

#rackstackatl

Proposed solution

Page 18: Bridging the Gap

#rackstackatl

18

Multi-hypervisor OpenStack architecture

Page 19: Bridging the Gap

#rackstackatl

vSphere in OpenStack

Page 20: Bridging the Gap

#rackstackatl

Workload zones

Cloud Controller Cloud Controller

ESXi

ESXi VMs

+N

Oracle Host Aggregate

vCenter

ESXi

ESXi VMs

Compute Node

+N

Compute Node/KVM

KVM VMsApp Host Aggregate

+N

KVM Host Aggregate

Virtual Computer Node

Page 21: Bridging the Gap

#rackstackatl

• 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

NetworkingPhysical Network(131.107.x.x/16)

Logical Network(131.107.1.x/24)

Logical Network(131.107.2.x/24)

Logical Network(192.168.1.x/24)

Logical Network(192.168.1.x/24)

Page 22: Bridging the Gap

#rackstackatl

vSphere storage in OpenStack

vCenter

ESXi

ESXI VMs

ESXi

ESXI VMsCompute Node

Virtual Computer Node

Cinder Volume Cinder Volume

Cloud Controller

Cinder Node

Page 23: Bridging the Gap

#rackstackatl

• 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)

Operational challenges of this solution

Page 24: Bridging the Gap

#rackstackatl

Summary

Page 25: Bridging the Gap

#rackstackatl

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

Page 26: Bridging the Gap

#rackstackatl

Questions?

Page 27: Bridging the Gap

#rackstackatl

THANK YOU!Ken [email protected]

Scott [email protected]