This document discusses VMware's vision for software defined storage and integration with OpenStack's Cinder block storage service. It introduces Virtual SAN and Virtual Volumes as ways to provide shared storage using local disks and make external storage VM-aware. The document outlines VMware's driver for Cinder that allows creation and attachment of VMDK volumes on vSphere. It notes current API support and roadmap items like storage policy support.
2. 2 Confidential – Not for External Distribution
OpenStack on VMware
3. 3 Confidential – Not for External Distribution
VMware Vision: Software Defined Storage
Software Defined Storage
Software-Defined Storage Vision
Enable new storage tiers
Enable DAS & server flash for shared
storage along with enterprise SAN/NAS
Enable tight integration with storage
ecosystem
Tighter integrations with broad storage
ecosystem through APIs
Deliver policy-based automated
storage management
Automatically enforce per-VM SLAs for all
apps across different types of storage
“Gold”
Array(s)
“Silver”
Array(s)
Distributed
Storage
Hard
disks
SSD Hard
disks
SSD
Availability = 99.99%
DR RTO = 1
“Gold” SLA
Availability = 99%
Throughput = 1000 R/s, 20 W/s
Latency = 95% under 5 ms
DR RPO = 1’, RTO = 10’
Back up = hourly
Capacity res = 100%
Web Server
Database Server
Availability =
99.99%
DR RTO = 1 hour
Max Laten
“Bronze” SLA
Availability = 99%
Throughput = 100 R/s,10 W/s
Latency = 90% under 10 ms
DR RPO = 60’, RTO = 360’
Back up = weekly
Security = encryption
Reduce
Storage
Cost
and
Complexity
App Server
4. 4 Confidential – Not for External Distribution
Virtual SAN (VSAN)
What is Virtual SAN? Key Features
Converged compute + storage solution
Utilizes DAS and server attached disks
Auto-tiering between SSD and HDD
Intelligent policy driven data placement
across the cluster
vCenter-integrated, instant storage
provisioning
High performance storage at up to
50% lower cost
Radically Simple Storage – configure
and manage without complex workflows
Designed for dynamic scalability
and high resiliency
Clusters internal server disks to
provide scalable shared storage with
cloud agility and efficiency.
Customer Benefits
vSphere
Virtual SAN
Hard
disks
SSD
…………….
Hard
disks
SSD Hard
disks
SSD
Distributed Storage
Aggregated Datastore
vCenter Server
5. 5 Confidential – Not for External Distribution
vSphere
Virtual Volumes
What are Virtual Volumes? Key Features
Existing SAN/NAS systems become
VM-aware
Native representation of VMDKs
on SAN/NAS
New API for data operations at
VMDK granularity
Native representation of VMDKs
on storage
Snapshots, replications and other
operations at VM granularity on
external storage
Works with existing SAN/NAS
storage systems
VM level storage SLA enforcement
Current Paradigm
VMDKs
on
LUNs
LUNs replicated
Virtual Volumes
vSphere
VMDKs on
storage
systems
VMDK replicated
Customer Benefits
Broad partner ecosystem
6. 6 Confidential – Not for External Distribution
What is Policy-based Management?
Storage Policy Based Management (SPBM)
• Simple policies to specify app SLA
requirements
• Automation of storage provisioning and
VM placement across clusters
• Works for any protocol : block, file
and object
• SLA Compliance monitoring & automatic
remediation
Key Features
• Drastically simplify storage provisioning
• Management of different storage tiers
as one
• Reduce storage cost by optimizing
consumption
Software Defined Storage
Enterprise SAN/ NAS
Virtual SAN BLOB Storage
Availability =
99.99%
DR RTO = 1 hour
Max Laten
SLA Definitions
Availability = 99.99%
DR RTO = 1 hour
Back up = daily
Storage capacity = 1 TB
Performance = High I/O
Security = High
Availability =
99.99%
DR RTO = 1 hour
Max Laten
SLA Definitions
Availability = 99%
DR RTO = 4 hour
Back up = weekly
Storage capacity = 10 TB
Performance = High I/O
Security = High
Customer Benefits
7. 7 Confidential – Not for External Distribution
The Basics: Storage Abstraction in vSphere
The Datastore is the fundamental persistence abstraction.
The VMDK is the Disk abstraction
Storage Policy Based Management (SPBM) is the Control Plane
VMware is Moving Away from LUN based policy and towards
VMDK based policy
• For Local Storage, this is done via VSAN
• For Shared Storage, this is done via VVOL
VMware is Moving Away from Raw Device Map (RDM) Disks
Thus, a VMDK Driver for Cinder
8. 8 Confidential – Not for External Distribution
Cinder VMDK Driver Work Flow
As with Nova, vSphere Admin Sets Up Capacity Pools
• For Storage this Means Datastores in Havana
• For Icehouse, this will include SPBM
Cloud Admin Creates Cinder Volume Types
• Volume Type is our MetaData Injection Vehicle
Consumer Creates New Cinder Volume
• This Allows us to create meta data
Consumer Attaches Cinder Volume
• We Lazy Create the VMDK Based on VM Target
• VMDK Is Mounted By vSphere Against Target
9. 9 Confidential – Not for External Distribution
Volume types and extra specs
Driver allows additional configuration for volume creation via extra
specs in the volume type
VMDK type
• Use extra spec key ‘vmware:vmdk_type’
• Legal Values: ‘thin’, ‘thick’ and ‘eagerZeroedThick’
• Default type is ‘thin’
Clone type
• Use extra spec key ‘vmware:clone_type’
• Legal Values: ‘full’ and ‘linked’
• Default type is ‘full’
10. 10 Confidential – Not for External Distribution
What the Heck is a “Shadow” VM?
In vSphere There is No “First Class Disk” Object. Yet.
When You Create a VMDK It Must be the Child of a VM
However, Cinder Assumes a First Class Disk
Therefore, A “Shadow” VM is inserted
<<<KARTIK, INSERT SCREEN SHOT HERE OF SHADOW VM>>>
11. 11 Confidential – Not for External Distribution
DEMO
VMware VMDK Driver for Cinder
12. 12 Confidential – Not for External Distribution
Current API Support
Create volume
• Supported VMDK types – thin, thick, eagerZeroedThick
• From scratch
• From glance image
• From an available source volume – full clone and linked clone
• From a snapshot – full clone and linked clone
Attach volume to an instance
Detach volume from an instance
Snapshot an available volume
Delete snapshot of an available volume
Upload an available volume as glance image
Delete volume
13. 13 Confidential – Not for External Distribution
Committed Roadmap
Support for Storage Policy Based Management (SPBM)
Fix for SnapShot/Clone Issues with Attached Volumes
Move Core Storage Code into Oslo
Implement Remaining API Items
Incorporate Additional Icehouse APIs
Nova Support for SPBM
14. 14 Confidential – Not for External Distribution
Thoughts Beyond Icehouse
Common Meta Data Model Between Cinder and Nova
Support For Application Consistent Snapshots
DR/HA Considerations in Cinder
• How Do we Abstract Availability Zones?
Storage QOS
• How Do We Represent Performance Contracts?
Inter DC Data Mobility Services
Alerting/Policy Violation Support, Ceilometer?
Others?
15. 15 Confidential – Not for External Distribution
Demo
VMware vSphere on
OpenStack
by Scott Lowe
Location: Sponsor
Demo Theatre
Date: Wed @ 2 PM
General Session
Navigating the
Transition to
Network
Virtualization
With Martin Casado
Location: Asia World –
Summit Hall 2
Date: Tues @ 12:05 PM
http://vmware.com/go/openstack
Day Time Room Title Speaker
Tuesday 2:50
PM
Sky City Marriott -
Grand Ballroom C
User Panel: How did you bring OpenStack
Cloud to your company
Panel
Tuesday 3:40
PM
Expo Breakout Room 1 Bridging the Gap: Explaining OpenStack to
VMware Administrators
Scott Lowe
Wednesday 11:15
AM
Expo Breakout Room 1 OpenStack + VMware: Customer Success
Stories & What’s Next
Dan Wendlandt
Wednesday 5:30
PM
Expo Breakout Room 1 Network Virtualization with OpenStack
Neutron & VMware NSX
Somik Behera
Dimitri Desmidt
Thursday 9:50
AM
Sky City Marriott -
Meeting Room 4
Differentiated Services == Differentiated
Scheduling
Gary Kotton
Thursday 2:40
PM
Sky City Marriott -
Grand Ballroom C
Open vSwitch Deep Dive: The Virtual
Switch for OpenStack
Eric Lopez
Justin Pettit
Thursday 3:30
PM
Sky City Marriott -
Meeting Room 4
Bridging the Gap: Cinder and vSphere Alex Jauch
Kartik Bommepally
Thursday 5:20
PM
Sky City Marriott -
Grand Ballroom C
How to Write a Neutron Plugin, If You
Really Need To
Salvatore
Armando
Friday 11:00
AM
Sky City Marriott -
Grand Ballroom A&B
Hands-on with OpenStack + vSphere Gary Kotton
Friday 1:30
PM
Sky City Marriott -
Grand Ballroom A&B
OpenStack Networking Hands-on Lab Eric Lopez
Aaron Rosen
Learn More!
Software Defined Storage Vision:
1. Reduce cost of storage by enabling new tiers of storage. Utilize server based flash/SSD and DAS to create a tier of storage, with all the benefits of external shared storage
2. Enable integration with existing tiers of storage – Make existing SAN and NAS storage systems VM aware. i.e Enable VM-level operations natively on storage systems.
3. Automate SLA enforcement across any tier of storage through policies
The Virtual SAN feature clusters internal server disks to provide scalable shared storage with cloud agility & efficiency.
It’s VMware’s first major foray into delivering storage. We’re taking a software-defined approach that is radically simpler, more scalable and agile, and lower-cost than traditional monolithic SAN or NAS storage:
* The storage is flexible & elastic in that virtual storage can live anywhere across the pooled resource.
* It’s inherently a fault-replace model; any failure is handled without downtime.
* And, the entire system is tightly integrated with, and automated by, vCenter … and it’s specifically integrated into the application provisioning workflow so that it’ll maximize Cloud application deployment agility.
Radically Simple Storage
Automating storage provisioning & management for virtual machines
Designed For Cloud
Delivering the performance, agility and scalability demanded by current & next-gen apps
Up to 50% Lower TCO
Reducing storage capex & opex by using low-cost internal disks & eliminating complex workflow
VMware has been investing in storage integration over the years—features like VAAI for block and NAS and VASA have increase efficiency of storage provisioning. Continuing this we are working with the storage industry on he most ambitious collaboration in the history storage industry, called Virtual Volumes (VVOLs). With this we leapfrog our competition by several years while creating the ecosystem stickyness for years to come……
Current data granularity of datastores does not fit for delivering VM specific policies using storage capabilities. What we need to more granular data management capabilities at the storage. With VVOLs, we will make existing storage system understand VMs. With native representation of VMDKs and its derrivatives, we will be able to leverage any storage capability—replication, snapshots-- that exists at VM granularity. We will be able to deliver application specific QOS leveraging storage capabilities like resource management and so on.
We are working with top 5 storage vendors for the last 2 years on this initiative.
Finally….
We will create an orchestration layer which will control different storage tiers in order to deliver application specific SLAs. This will help with VMware’s vision of cloud scale provisioning by drastically simplifying storage provisioning. This will help customer create, manage and consolidate different storage tiers in order to reduce the storage cost by using right storage for right application. No more over provisioning of resources… increase utilization overall…
Application requirements are captured in simple policies.. Customer can create different services levels using these policies though self service portals.. The automated placement of VM’s storage to match the requirements would simplify how storage provisioning done for applications. Should reduce the app deployment time from days to minutes. The compliance monitoring and automatic remediation will enforce SLA automatically.