I had a question last week from Bozo Popovic during our EMEA field SE training session on vSAN operations relating to SPBM support for service providers that use vCloud Director in their environments.
Next up Mr. @mylesagray giving a #vSAN operations overview to our EMEA field at the @vmwarevsan workshop this morning pic.twitter.com/48seQc8i7d
— Cormac Hogan (@CormacJHogan) November 30, 2017
I am stating this for clarity – since the vCD 9.0 release we have supported native SPBM compatibility for vCloud Director. SPBM policies can be adopted into vCD and assigned to PVDCs and to tenants via Org VDCs.
Within vCenter you create your SPBM policies as normal, you can see in my lab I have two vSAN policies: vSAN Default Storage Policy and vSAN High Throughput.
Moving to vCloud Director then, navigate to Manage & Monitor -> vSphere Resources -> Storage Policies and you will see your SPBM policies available listed here.
This is an obvious departure from the previous architecture of vCD datastores where tags were assigned to datastores and objects were placed directly on to them, as vSAN is a single datastore vCD required the awareness that objects on the same datastore could have different storage policies.
To assign resources to a PVDC in order to allow tenants access to the resource you need to navigate to Manage & Monitor -> Cloud Resources -> Provider VDCs -> {Your PVDC} -> Storage Policies.
From here you click on the green + icon and select the relevant SPBM policy available in vCenter to have it utilised by the Provider VDC. You can now allocate this SPBM policy to the tenant Org VDCs that are children of the Provider VDC. Again, navigate to the Org VDC and go to the Storage Policies tab and click the green + icon to move a policy into the Org VDC for consumption by the tenant.
At this point the tenant can configure VMs with disparate SPBM policies for individual disks/the whole VM if they wish, during their provisioning cycle, or retrospectively change policies via the VM properties window in vCloud Director.
This includes changing from a traditional tag-based datastore to a vSAN based SPBM policy, which will automatically kick off a Storage vMotion in the background for that resource.
Why not follow @mylesagray on Twitter for more like this!
Leave a Reply