bridging the gap: explaining openstack to vmware administrators kenneth hui, open cloud architect,...

30
Bridging the Gap: Explaining OpenStack to VMware Administrators Kenneth Hui, Open Cloud Architect, Rackspace Scott Lowe, Engineering Architect, VMware

Upload: landon-bower

Post on 16-Dec-2015

222 views

Category:

Documents


0 download

TRANSCRIPT

Bridging the Gap:Explaining OpenStack toVMware Administrators

Kenneth Hui, Open Cloud Architect, RackspaceScott Lowe, Engineering Architect, VMware

Before we start

•Get involved! Audience participation is encouraged and requested.

•Feel free to post updates to your social media platform of choice

•I encourage you to take photos or videos of today’s session and share them online

•This presentation will be made available online after the event

Architecture

•vSphere and OpenStack have very different origins

•Those origins greatly influenced the resulting architectures

•vSphere originated as a way to provide virtualized infrastructure

•OpenStack originated as a way to provide consumable infrastructure services

Different origins

(picture of hammer and nail)

(picture of multiple tools)

•Loosely coupled vs. tightly coupled (more on that in a moment)

•API driven

•Multiple hypervisors (KVM, Xen, vSphere, Hyper-V)

•Multiple disk formats (QCOW, RAW, VMDK...)

•Integrated networking

Key architectural attributes

OpenStack architecture

vSphere architecture

Architectural mapping

Terminology

Virtual machines and instances

Custom VMs and flavors

Templates and images

Virtual disks and volumes

Operations

•Cloud instances are disposableVMs are not uniqueTune and groom apps not the cattleReplace when necessaryShoot the cattle when it is sick

Cattle vs. pets

•Virtual Machines needs care and feeding•Name the VM•Tune and groom regularly•Feed pets with good food and supplements

•Take pets to the vet when they are sick

No vSphere-style HA using KVM with libvirt

Instance evacuation

•Without Shared Storage

•The instance will be booted from a new disk, but will preserve the configuration, e.g. id, name, uid, ip...etc.

•With Shared Storage

•The instance will be booted from same disk and data will be preserved

vMotion and Storage vMotion

Instance migration

OpenStack storage options

Ephemeral storage

Block storage

Object storage

•Differences in how networking is handled really reflect the architectural differences in OpenStack and vSphere

•Networking in vSphere is a bit more separate

•OpenStack networking is more integrated

Networking

Networking

Networking

Additional Resources

• OpenStack Configuration Reference• http://docs.openstack.org/trunk/config-reference/content/section_compute-

hypervisors.html• vSphere with OpenStack Blog Posts

• http://cloudarchitectmusings.com/2013/06/24/openstack-for-vmware-admins-nova-compute-with-vsphere-part-1/

• http://cloudarchitectmusings.com/2013/06/26/openstack-for-vmware-admins-nova-compute-with-vsphere-part-2/

• http://cloudarchitectmusings.com/2013/07/09/openstack-compute-for-vsphere-admins-part-3-ha-and-vm-migration/

• http://cloudarchitectmusings.com/2013/08/05/openstack-compute-for-vsphere-admins-part-4-overcommitment-in-nova-compute/

• http://cloudarchitectmusings.com/2013/08/13/openstack-compute-for-vsphere-admins-part-5-designing-for-vsphere-with-nova-compute

Thank youKenneth [email protected]@hui_kennethhttp://cloudarchitectmusings.com

Scott [email protected]@scott_lowehttp://blog.scottlowe.org