This diagram shows the architecture of the vVol implementation in a PowerMax or VMAX All Flash environment.
The diagram shows the VASA Provider separate from the storage array.
PowerMaxOS 10 (6079) and
PowerMaxOS 5978.669.669, and later, include an embedded VASA Provider that runs as a guest management application on the PowerMax array.
Components
The major components in the implementation of vVols are:
Virtual Machine (VM)
A virtual machine on an ESXi host managed through the VMware product.
vVol
A virtual disk associated with a specific VM.
Storage Container
A pool of storage on an array set aside for use by vVols.
Storage Resource
A subdivision of a storage container that has a specified capacity and has attributes like Service Level, Workload, and data reduction. There are one or more Storage Resources in each Storage Container.
The vSphere administrator creates vVols in the Storage Resources according to the capabilities that the VM requires.
Protocol endpoint
A thin device that acts as a data path between the vVols on a storage array and their virtual machines on the ESXi host.
VASA Provider
A software component that implements vSphere APIs for Storage Awareness (VASA). The vSphere administrator manages the resources on the array that are allocated to the VMs through the VASA Provider.
Management responsibilities
Table 1. Management responsibilities in a vVol environmentThis table shows who creates and manages each component.
Component
Manager
Virtual Machine
vSphere administrator
vVol
vSphere administrator
Storage Container
Storage administrator
Storage Resource
Storage administrator
Protocol Endpoint
Storage administrator
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\