VMware Cloud Director Object Storage Extension 2.1 BETA | 21 APR 2021 | Build 17898048
Check for additions and updates to these release notes.
What's in the Release NotesThe release notes cover the following topics:
VMware Cloud Director Object Storage Extension 2.1 introduces the following new capabilities:
Kubernetes Backup and Restore
- Tenant users can back up and restore their Kubernetes clusters using VMware Cloud Director Object Storage Extension.
Improved User Role Management
- Service provider administrators can customize the rights for built-in roles.
- A new user role for organization administrators named operator role is introduced. Operators can add an additional layer of granularity for tenant roles. Tenant administrators can now fine-tune access and permissions for certain features for other tenant users.
vApp Import and Export Enhancements
- Tenant users can import and export vApps directly through the VMware Cloud Director tenant portal.
Global Bucket Synchronization
- Service providers can now synchronize VMware Cloud Director Object Storage Extension platform with the underlying storage platform by on-demand requests or scheduling.
Archived Object Restoration
- Tenant users can restore objects from AWS S3 Glacier and Glacier Deep storage classes.
You can upgrade directly to VMware Cloud Director Object Storage Extension 2.1 from versions 2.x and 1.5. See Upgrading VMware Cloud Director Object Storage Extension.
Caveats and Limitations
- S3 API requests authenticated with application credentials do not support the following use cases:
- Accessing a shared bucket if another user grants you permissions for the bucket.
- Deleting multiple objects simultaneously with a single API request.
- Restriction on copying objects from buckets that you own.
- VMware Cloud Director and the underlying storage systems have different limitations on user names. To use VMware Cloud Director Object Storage Extension, user names must comply with both the requirements of VMware Cloud Director and the underlying storage system. A best practice is to use short user names (under 50 bytes) and to use alphanumeric characters.
- If you are using Cloudian storage, increase the maximum length of user IDs from 64 bytes to 255 bytes.
- If you are using ECS storage, the maximum length of user IDs is 91 bytes.
- If you are using ECS storage, using S3 API, or the find a bucket feature, you cannot visit a bucket that belongs to a different tenant organization in the ECS platform.
In addition to the current release notes, you can use the VMware Cloud Director Object Storage Extension documentation set at https://docs.vmware.com/en/VMware-Cloud-Director-Object-Storage-Extension/index.html.