Embed Size (px)
Citation preview
HP Storage
VMware vVols and HP 3PAR StoreServ What you need to know!
Calvin Zito, Blogger and HP Storage Evangelist
UserCon Milano
Introduction
2
About me
• Started with HP in 1983 (field engineer)
• Moved to HP Storage in 1990
• Starting blogging and social media in 2007
• Formerly @HPStorageGuy; now @CalvinZito
• vExpert for 5 years
How to connect with me
• Around the Storage Block blog: www.hpe.com/storage/blog
• HPE Storage Group on LinkedIn: http://hpstorage.me/HPStorageGroup
• Find me on LinkedIn: http://bitly/CalvinZ
@CalvinZito
Take HPE Storage for VMware for a test ride!
• Software defined block based storage StoreVirtual VSA:
www.hpe.com/storage/TryVSA
• Software defined deduplication StoreOnce VSA:
www.hpe.com/storage/TryVSA
• HPE 3PAR StoreServ Simulator: [email protected]
What you must know about vVols
6
Pre-HP
VMworld Preview
vVol introduced with HPE as
1 of 5 original design partners
Began vVol
Collaboration
HPE and VMware: Redefining Storage for vSphere
Aug 2011
Design partnership between HPE 3PAR StoreServ and VMware Virtual Volumes
VMware
vVol GA vSphere 6
with vVols GA
Release
Mar 2015 June 2014
Discover Demo
Live, hands-on demo of
3PAR and vVols
vVol Beta
HPE 3PAR 1 of 3 partners
ready on Beta Day 1
July 2014
Reference Platform
3PAR selected as the FC
reference platform
May 2012
3PAR & vVol Blog
Early preview of 3PAR
and vVol integration
Oct 2012
3PAR vVol GA
3PAR OS has full support
for vVols
Dec 2014
Goals of vVols
8
How vVols Transforms Storage in vSphere
Traditional VMFS Virtual Volumes
• LUN-centric model
• Static pre-allocated storage
• Over-provisioning of resources
• Creates siloed storage pools
• More complex management
• Manual space reclamation
• Vendor specific management tools
• Longer provisioning cycles
• Array services aligned to LUNS
• VM-centric model
• Dynamically allocated storage
• Only use what is needed
• No storage pools
• Simplified management
• Automatic space reclamation
• vSphere management tools
• Rapid provisioning
• Array services aligned to VMs
VMware’s Goal of vVols
More efficient operational
model centering it on the
application instead of the
physical infrastructure
New storage operational
model
Application level granularity
Value proposition of vVols
Simplified
Management
Better SLAs
Improved
Efficiency
Automating manual
tasks and eliminating
operational
dependencies
More flexible
consumption of
storage resources with
greater granularity
Finer control of
storage resources and
data services at the
VM level
vSphere Storage Features shift to Array Features
Goal is to offload storage functionality to the storage array but manage it via vSphere
vSphere
Admin
Create VM
Snapshot
Thin Provision
VM
Create Virtual
Disk
Delete VM
vSphere
Client
Array creates snapshot vVol
Array thin provisioning used
Array allocates spaces and
creates vVol
Array deletes vVols and reclaims
space
Storage
Admin
Empowers
vSphere
admin
Eliminates
common tasks
for Storage
admin
Automation
Not designed to
be managed
here
All
management
occurs here
Storage Array
Understanding vVols Architecture and Components
12
Overview of vVols Storage Architecture
– Protocol Endpoint: Logical I/O proxy that serves as the data path between ESXi hosts to VMs and their respective vVols
Protocol
Endpoint
ESXi hosts vCenter Server
Data
Path
Storage Array
Overview of vVols Storage Architecture
– Protocol Endpoint: Logical I/O proxy that serves as the data path between ESXi hosts to VMs and their respective vVols
– VASA Provider: Software component that mediates out-of-band communication for vVols traffic between vCenter Server, ESXi hosts & storage array
Protocol
Endpoint VASA
Provider
ESXi hosts vCenter Server
Control Path Data
Path
Storage Array
Overview of vVols Storage Architecture
– Protocol Endpoint: Logical I/O proxy that serves as the data path between ESXi hosts to VMs and their respective vVols
– VASA Provider: Software component that mediates out-of-band communication for vVols traffic between vCenter Server, ESXi hosts & storage array
– Storage Container: Pool of raw storage capacity that becomes a logical grouping of vVols
Protocol
Endpoint VASA
Provider
ESXi hosts vCenter Server
Control Path Data
Path
Storage Container
Storage Array
Overview of vVols Storage Architecture
– Protocol Endpoint: Logical I/O proxy that serves as the data path between ESXi hosts to VMs and their respective vVols
– VASA Provider: Software component that mediates out-of-band communication for vVols traffic between vCenter Server, ESXi hosts & storage array
– Storage Container: Pool of raw storage capacity that becomes a logical grouping of vVols
– Virtual Volume (vVol): Container that encapsulates VM files, virtual disks and their derivatives
Protocol
Endpoint VASA
Provider
ESXi hosts vCenter Server
Control Path Data
Path
VM VM VM VM VM
Storage Container
VV
OL
s
Storage Array
Overview of vVols Storage Architecture
– Protocol Endpoint: Logical I/O proxy that serves as the data path between ESXi hosts to VMs and their respective vVols
– VASA Provider: Software component that mediates out-of-band communication for vVols traffic between vCenter Server, ESXi hosts & storage array
– Storage Container: Pool of raw storage capacity that becomes a logical grouping of vVols
– Virtual Volume (vVol): Container that encapsulates VM files, virtual disks and their derivatives
– Storage Profile: Set of rules that define storage requirements for VMs based on capabilities provided by storage array
Protocol
Endpoint VASA
Provider
SPBM
ESXi hosts vCenter Server
Control Path Data
Path
VM VM VM VM VM
Storage Container
VV
OL
s
Storage Array
Meet The vVols…
Meet The vVols…
Config
Similar to .vmx
Contains VM
config data & disk
metadata
Also contains VM
log and lock files
Provisioned Thin
Max size 4GB
One per VM
Meet The vVols…
Config Data
Similar to .vmx
Contains VM
config data & disk
metadata
Also contains VM
log and lock files
Provisioned Thin
Max size 4GB
One per VM
Similar to .vmdk
Raw virtual disk
data file
Also used for
snapshot vVols
Provisioned Thin
(can be made full)
Max size 64TB
One for each VM
disk and snapshot
Meet The vVols…
Config Data Swap
Similar to .vmx
Contains VM
config data & disk
metadata
Also contains VM
log and lock files
Provisioned Thin
Max size 4GB
One per VM
Similar to .vmdk
Raw virtual disk
data file
Also used for
snapshot vVols
Provisioned Thin
(can be made full)
Max size 64TB
One for each VM
disk and snapshot
Similar to .vswp
Swap file for
memory over-
commitment
Created when VM
is powered on
Provisioned Full
Max size 4TB
One for each VM
Meet The vVols…
Config Data Swap Memory
Similar to .vmx
Contains VM
config data & disk
metadata
Also contains VM
log and lock files
Provisioned Thin
Max size 4GB
One per VM
Similar to .vmdk
Raw virtual disk
data file
Also used for
snapshot vVols
Provisioned Thin
(can be made full)
Max size 64TB
One for each VM
disk and snapshot
Similar to .vswp
Swap file for
memory over-
commitment
Created when VM
is powered on
Provisioned Full
Max size 4TB
One for each VM
Similar to .vmss
and .vmsn
Stores memory
state for
suspended VMs
and snapshots
Provisioned Full
Max size 4TB
One for each VM
(suspend) or each
snapshot
Storage Policy-Based Management
• vVols uses same SPBM engine that VSAN uses
• Allows VMs to be provisioned onto storage that best suits app requirements
• Storage Policies are built from array capabilities
1. Storage Array advertises capabilities via VASA Provider
2. Storage Policies created in vSphere and assigned array capabilities
3. VMs are assigned a Storage Policy based on requirements and SLAs
4. SPBM identifies compatible datastores on storage array
5. VMs are provisioned on appropriate storage as defined by policy
Gold Policy Silver Policy
vVols and HPE 3PAR StoreServ Demo
View demo at https://youtu.be/iwhYZwWVMcA
Comparing vVols and VMFS
vVols VMFS
Storage for VMs provisioned by vSphere Admin Storage Admin
Policy-based management Full (VASA 2.0) Limited (VASA 1.0)
Storage array features applied per VM per LUN
Supports VAAI Yes Yes
Supports replication Future vSphere or Storage array
Supports SRM or vMSC Future Yes
Supports Direct to SAN backup No Yes
Supports vRealize Operations
Mgr
Future Yes
Automatic space reclamation Yes No
Note: vVols can be used alongside VMFS in vSphere 6
Interoperability and Compatibility with vVols
VMware products that do not support vVols:
• VMware vRealize Operations Manager 6.0.x
• VMware vCloud Air
• VMware Site Recovery Manager 5.x to 6.0.x
• VMware vSphere Data Protection 5.x to 6.0.x
• VMware Data Recovery 2.x
• VMware vCloud Director 5.x
• VMware NSX for vSphere 6.x
vSphere features that
do not support vVols: • Storage I/O Control
• NFS version 4.1
• IPv6
• Storage Distributed Resource
Scheduler (SDRS)
• Fault Tolerance (FT)
• SMP-FT
• vSphere API for I/O Filtering
(VAIO)
• Array-based replication
• Raw Device Mapping (RDM)
• Microsoft Failover Clustering
Vendors that do
support vVols: • HP 3PAR StoreServ
• Dell Equalogic
• Hitachi HDS
• IBM XIV
• NetApp
• NEC
• SanBlaze
• Fujitsu
See VMware KB #2112039 See VMware Hardware Compatibility Guide
HPE 3PAR StoreServ and VMware
27
All cats look grey at night ...
Me too, Me too!!
I am Efficient, Autonomic and Resilient
But when you turn on the lights ...
Uuups!
HP 3PAR StoreServ
3PAR Flash Optimization
HPE 3PAR Industry Leadership
Best storage technology in the market – built for virtual environments
3PAR Optimization and Compaction Technologies
3PAR Thin Technologies
3PAR Persistent Technologies
3PAR Mesh-Active Architecture
3PAR Federation Technologies
3PAR Converged Block, File and Object Access
Traditional Modular Storage
Traditional Tradeoffs
Legacy vs. HPE 3PAR Hardware Architecture
Cost-efficient usually active/passive or active/optimized …
… but dual-controller design limits scalability and resiliency.
Cost-effective, scalable, resilient, meshed, active-active …
… and meets cloud-computing requirements for efficiency,
multi-tenancy and autonomic management. Host Connectivity
Data Cache
Drive Connectivity
Matrix switches
HPE 3PAR Architecture
Traditional Monolithic Storage
Scalable, resilient and active-active …
… but complex, costly, static and
inflexible.
Built-in Zero Detection &
Data Hashing for Dedup
All IO go through the
ASIC Tightly-Coupled
Clustering
High Bandwidth,
Low Latency Interconnect
Low Latency Cache
Mirroring
Minimal CPU cycles
required
Mixed Workload & CPU Offload
Independent Metadata and
Data Processing
Fast RAID 10, 50 & 60
Rapid RAID Rebuild
Integrated XOR Engine
The Heart of every 3PAR
HPE 3PAR ASIC
Watch the “Understand the 3PAR ASIC” video: http://www.youtube.com/watch?v=LmQMqWNGA7E
Most Arrays
It makes the difference in real-world environments
HPE 3PAR ASIC
Any
Processors
RAID Calculations
Replication
Mixed Workload
Thin Provisioning
Sub-LUN Tiering
Thin Reclamation
Snapshots
RAID Rebuilds
Inter-Node & Cache
IO
HPE 3PAR
RAID Calculations
Replication
Mixed Workload
Thin Provisioning
Sub-LUN Tiering
Thin Reclamation
Snapshots
RAID Rebuilds
Inter-Node & Cache
IO
+ 3PAR ASIC Intel x64
Processors
Data Deduplication Data Deduplication
CP
U L
oad
CP
U L
oad
3PAR VMware Integration
See also: http://h20195.www2.hp.com/V2/GetPDF.aspx/4AA3-4023ENW.pdf
HPE 3PAR is the perfect fit for virtualized environments
– Efficient integration of HP 3PAR Thin Technologies
– Simplified storage administration with vCenter Server and vRealize Operations
Manager (vROPS ex vCOPS) integration; VAAI and VASA support ; vSphere 6.x
vVol support; vCenter Site Recover Manager (SRM) integration
– High availability and disaster tolerance thanks to vSphere Metro Storage Cluster
certification
– Allows greater virtual machine (VM) density thanks to inherent wide-striping and
mixed workload support
– Easy recovery and replication using HP 3PAR Recovery Manager Software for
VMware vSphere
