4. Resource Group Architecture : 4.3 Storage Resources : 4.3.1 Storage Tiering
4.3.1 Storage Tiering
Storage tiering in vCloud Director 5.1 is enabled on a per virtual machine basis through storage profiles:
*Authoring, renaming, and deletion of storage profiles are performed through vSphere.
*Storage profiles can be added, disabled, or removed at the provider virtual datacenter level.
*All available storage profiles across selected clusters are listed at provider virtual datacenter creation.
*Organization virtual datacenter storage profiles are based on a subset of storage profiles provided by the provider virtual datacenter.
*Each organization virtual datacenter has an associated default storage profile.
*All virtual machines have an associated storage profile that defaults to the organization virtual datacenter storage profile.
*Virtual machine placement is based on storage profiles.
*Other entities that support storage profiles:
*Independent disks.
*OVF storage profiles support:
*vSphere does not export storage profile association when exporting a virtual machine to OVF.
*vCloud Director template download exports a template virtual machine’s default instantiation profile.
*vCloud Director template upload applies OVF-specified template virtual machine’s default instantiation profile.
*Disks independent of virtual machine:
*Are associated with an organization virtual datacenter storage profile.
*Allow selection of datastore to place the disk accounts for storage profile.
*Can have their storage profile changed.
*Are allowed to be on a different storage profile than the virtual machine to which the disk is attached.
*The following are vSphere changes that affect vCloud Director storage profiles:
*Changed datastore labels.
*Deleted storage profiles.
*Changed virtual machine storage profile association.
*Virtual machine migration to a new datastore using VMware vSphere Storage vMotion.
*Storage profile compliance checks are performed:
*When initiated through the REST API.
*When automatically performed at set time intervals.
*When a storage profile in use by an organization virtual datacenter is deleted in vCenter.
*When a virtual machine is migrated using vSphere Storage vMotion.
Non-compliance shows up in the form of system alerts on the virtual machine.