Support for Virtual Volumes¶
Virtual Volumes is an integration and management framework delivering a new operational model for external storage (SAN/NAS). It is comprised of a control plane using SPBM, and a data plane using VASA APIs for external storage and vSphere APIs for IO Filtering for in-hypervisor software data services.
A storage container is a logical abstraction on to which Virtual Volumes are mapped and stored. Storage containers are setup at the array level and associated with array capabilities. vSphere will map storage containers to VVol Datastores and provide applicable datastore level functionality.
Currently the VMware driver in Nova supports VMFS, NFS and vSAN datastores. This is a proposal for adding support for VVol Datastores.
The VMware driver cannot provision instances on VVol Datastores.
As an End User I want to provision instances on VVol Datastores when using the VMware driver in Nova.
Adding support for VVol Datastores would be pretty straightforward – we just need to whitelist datastores with type “VVOL” when choosing a datastore for the instance. There is also an additional restriction that the virtual disk size of the image that is provisioned should be an even multiple of 1MB.
Data model impact¶
REST API impact¶
Other end user impact¶
Other deployer impact¶
- Primary assignee:
It will be implemented in a single patch that whitelists the VVol type and does the required checks for the virtual disk size.
Virtual Volumes are introduced in vSphere 6.0. However, we don’t need any checks for the VC version in the code but simply whitelist the VVol type.
There will be a separate CI job that will run tempest with VVol datastores