Transcript Cloud-native design principles

Bridging the Gap
OpenStack for VMware administrators in the
context of a fictional use case
Presenters
Kenneth Hui
Scott Lowe
Technology Evangelist
Engineering Architect
Rackspace
VMware, Inc.
Twitter: @hui_kenneth
Twitter: @scott_lowe
#rackstackatl
Agenda
#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
#rackstackatl
A tale of two workloads
#rackstackatl
Workload dictates architecture
#rackstackatl
Traditional design principles
Monolithic architecture
Stateful Services
Operator focused
#rackstackatl
Design goal: Resilient infrastructures
#rackstackatl
Cloud-native design principles
Distributed architecture
Stateless Services
Developer focused
#rackstackatl
Design assumption: Fragile infrastructures
#rackstackatl
We architect clouds for rapid scale
#rackstackatl
1
Chaos and failures are inevitable at scale
#rackstackatl
1
So design for failure
#rackstackatl
1
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
#rackstackatl
Fictitious customer use case
#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
#rackstackatl
Proposed solution
#rackstackatl
18
Multi-hypervisor OpenStack architecture
#rackstackatl
vSphere in OpenStack
#rackstackatl
Workload zones
Cloud Controller
Cloud Controller
Compute Node
vCenter
Oracle Host
Aggregate
ESXi
ESXi VMs
Compute Node/KVM
+N
App Host
Aggregate
ESXi
+N
KVM VMs
KVM Host
Aggregate
+N
ESXi VMs
Virtual Computer Node
#rackstackatl
Networking
• 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
Physical Network
(131.107.x.x/16)
Logical Network Logical Network
(131.107.1.x/24) (131.107.2.x/24)
Logical Network Logical Network
(192.168.1.x/24) (192.168.1.x/24)
#rackstackatl
vSphere storage in OpenStack
Virtual Computer Node
Cloud Controller
Compute Node
vCenter
ESXi
ESXi
ESXI VMs
ESXI VMs
Cinder Node
#rackstackatl
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)
#rackstackatl
Summary
#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
#rackstackatl
Questions?
#rackstackatl
THANK YOU!
Ken Hui
[email protected]
Scott Lowe
[email protected]
#rackstackatl