VMware Cloud Director Object Storage Extension 2.1 | 23 SEP 2021 | Build 18626693

Check for additions and updates to these release notes.

What's New

VMware Cloud Director Object Storage Extension 2.1 provides a list of new features:

  • Kubernetes Backup and Restore

    Tenants can back up and restore their Kubernetes clusters using VMware Cloud Director Object Storage Extension. See Backing up and Restoring Kubernetes Clusters.

  • Cloudian Storage Policies

    • Cloud providers have the option to create custom storage policies for tenants who use the Cloudian platform. Storage policies help you to protect your data and to avoid losses in case of a failure. See Cloudian Storage Policies.
    • Tenant users can apply the storage policies when creating buckets and objects. See Apply a Cloudian Storage Policy.
  • Global Bucket Synchronization

    Cloud providers can now synchronize VMware Cloud Director Object Storage Extension platform with the underlying storage platform by on-demand requests or scheduling. See Global Bucket Synchronization.

  • Archived Object Restoration

    Tenant users can restore objects from AWS S3 Glacier and Glacier Deep storage classes. See Restore an Archived Object.

  • vApp Import and Export Enhancements

    Tenant users can import and export vApps directly through the VMware Cloud Director tenant portal. See Working with vApps.

  • Improved User Role Management

    • Cloud providers can customize the rights for built-in roles. See Edit 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. See Edit Subordinate Roles.

Upgrade

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.

Resolved Issues

  • When you access S3 resources by using virtual hosted-style API requests, if your FQDN contains a hyphen (-), the API calls fail.

    When you access S3 resources using virtual hosted-style API requests, if the URL contains a hyphen, for example https://a-bucket.s3.ose-host.com/xyz.txt, the request fails.

    This issue is now resolved.

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.

  • Bucket synchronization supports up to 10 million objects per a single synchronization job

    When the cloud provider enables bucket synchronization for a tenant in the provider portal, the synchronization can support up to 10 million objects for the tenant. VMware Cloud Director Object Storage Extension 2.1 does not support the synchronization for more than 10 million objects per a single bucket synchronization job.

Product Documentation

All documentation is available on the VMware Cloud Director Object Storage Extension Documentation page.

Known Issues

  • Synchronization tasks of buckets with more than 60 thousand objects fail with a timeout error

    When you try to sync a bucket that contains more than 60 thousand objects, the synchronization task expires after 24 hours.

    Workaround: Click the Sync button repeatedly until the synchronization task completes successfully.

check-circle-line exclamation-circle-line close-line
Scroll to top icon