Storage Classification was introduced in System Center 2012 Virtual Machine Manager (VMM 2012) to provide the Fabric Administrator an easier way to classify storage with a friendly name (e.g. GOLD, HI-IOPS, etc). Now in SCVMM 2012 R2 Update Rollup 2 (UR2), VMM will enforce the storage classification rules for VM deployment on cloud. Let me explain how this works.
For those who are updating to VMM 2012 R2 UR2, if you want to select the storage classification on cloud then make sure they are set. This can be set thru the cloud properties on the Storage tab.
In VMM, the host group has storage attached with classification. The storage can be attached from three sources such as storage pool (lun must be unmasked), storage disk, and file share. You can also add multiple storage with different classifications to a single host group. When creating a cloud, the storage classification list is presented depending on the host group selected. You can select all, some or none of the classifications to be assigned to the cloud as you see in the figure below.
Once the cloud is created with the selected storage classification, the next steps is to deploy the VM from the VM template. When deploying, VMM will check the list of the selected storage classification and VM template classification. If the classification matches it will allow the VM deployment. (See the diagram below. ) However, if there is no match in the selected storage classification list and the VM template, the VM deployment is restricted.
If no cloud storage classification is selected while creating the cloud but there is a matching storage classification on the host group, VMM will allow the VM deployment on the storage.
The table below summarizes the classifications and the rules.