Home > Storage > PowerFlex > White Papers > Implementing Dell PowerFlex with VMware Tanzu > Introduction
As part of the Tanzu setup, the user must setup storage policies within vCenter. A storage policy is an object that encompasses defined rules or qualities about storage. These rules dictate where to create a VM or even .vmdk (for example, first class disk). For example, a storage policy might be created that says the VM or .vmdk must be created on an SSD datastore. Tanzu uses these policies when creating persistent storage for the containers by converting them into storage classes.
In this Tanzu setup, tagging is used which enables the user to specify exactly which datastores should be in a policy. There is no ability to create a storage policy that is only associated with SDC-presented volumes or NVMe/TCP-presented volumes. Instead, create a “tag” and manually assign it to the datastores based on the protocol.
Note: The naming of storage policies in VMware is flexible, for example, upper case, spaces, and so on. Storage class names that are associated with these policies are not. Therefore, VMware automatically converts noncompliant storage policy names when creating storage classes. For example, a storage policy that is named TCP policy is changed to the tcp-policy storage class. Users may be better served in adhering to the storage class naming restrictions when creating storage policies, unlike the guide.