When creating vSphere, KVM (RHEV), or SCVMM Create, Clone, FlexClone, or Linked Clone blueprints, tenant administrators and business group managers can assign datastores to volumes, or assign storage reservation policies to volumes.

Depending on the type of blueprint you are working with and your storage needs, the procedure to assign datastores to volumes differs slightly.

Table 1. Choosing a Storage Scenario

Scenario

Supported Platforms

Procedure

Assign a datastore to a Create, Clone, or FlexClone blueprint.

Note:

SDRS is not supported for FlexClone.

  • vSphere

  • KVM (RHEV)

  • SCVMM

Add a Datastore to a Create, Clone, or FlexClone Blueprint.

Assign a datastore to a Linked Clone blueprint.

vSphere

Add a Datastore to a Linked Clone Blueprint.

Assign a storage reservation policy to a Create, Clone, or FlexClone blueprint.

Note:

SDRS is not supported for FlexClone.

  • vSphere

  • KVM (RHEV)

  • SCVMM

Add a Storage Reservation Policy to a Create, Clone, or FlexClone Blueprint.

Assign a storage reservation policy to a Linked Clone blueprint.

vSphere

Add a Storage Reservation Policy to a Linked Clone Blueprint.

Prevent provisioning from failing in the case of insufficient space on the datastores in a storage reservation policy.

  • vSphere

  • KVM (RHEV)

  • SCVMM

Allow Alternative Datastores at Provisioning Time.

Note:

If you have SDRS enabled on your platform, you can allow SDRS to load balance storage for individual virtual machine disks, or all storage for the virtual machine. If you are working with SDRS datastore clusters, conflicts can occur when you use reservation policies and storage reservation policies. For example, if a standalone datastore or a datastore within an SDRS cluster is selected on one of the reservations in a policy or storage policy, your virtual machine storage might be frozen instead of driven by SDRS.