You can edit the mapping between the VMware Cloud Director and the storage platform tenant entities.
When you first activate VMware Cloud Director Object Storage Extension for a tenant organization, VMware Cloud Director Object Storage Extension creates an equivalent group in the underlying storage platform. When the storage tenant is created, VMware Cloud Director Object Storage Extension maps it to the VMware Cloud Director tenant organization. You can change the mapping configuration.
If you have vendor-specific object storage data (buckets and objects) in your data center, before you start using VMware Cloud Director Object Storage Extension, you can introduce the existing data to VMware Cloud Director Object Storage Extension by editing the tenant mapping.
By configuring the tenant mapping, you can also use one storage tenant for multiple VMware Cloud Director tenant organizations.
You can map multiple VMware Cloud Director tenant organization to the same storage group, for example, to share the storage for tenant organizations within a multisite VMware Cloud Director environment. A best practice is to create a standalone storage group in your storage platform and then map tenant organizations to it. It is not a best practice to map one tenant organization to the default storage group of another tenant organization.
When you edit the default tenant mapping configuration, consider the following constraints:
- For example, by default tenant1 is mapped to storage1. If you edit the mapping for tenant1 and map it to storage2, you cannot map another tenant to storage1.
- For example, by default tenant1 is mapped to storage1. If you map tenant2 to storage1, you cannot map tenant1 to another storage.
Prerequisites
Verify that you deactivated VMware Cloud Director Object Storage Extension for the tenant organization for which you want to edit the mapping configuration. See Deactivate VMware Cloud Director Object Storage Extension for a Tenant Organization.