VMware Cloud Director Object Storage Extension 2.0 | 15 OCT 2020 | Build 17024017

Check for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

What's New

VMware Cloud Director Object Storage Extension 2.0 introduces the following new capabilities:

Native AWS S3 Integration

  • Service providers can offer native AWS S3 to tenant users with seamless integration with the multi-tenancy of VMware Cloud Director. See Configure VMware Cloud Director Object Storage Extension with AWS. Service providers have four options for onboarding tenants to VMware Cloud Director Object Storage Extension.
    • Invite an existing AWS account to join the provider’s AWS organization.
    • Create a new AWS account on behalf of the VMware Cloud Director tenant user
    • Reuse the existing AWS account of the provider from its AWS organization
    • Share an AWS account for multi-site VMware Cloud Director tenant organizations

                      See Onboarding VMware Cloud Director Organizations and Users to AWS.

  • Enables tenant users to use object storage service that is backed by native AWS S3 integration.
  • Provides complete S3 APIs comparable with the native AWS S3 APIs.

 

Support for VMware Cloud Director Service

 

Object Lock

  • Tenant users can enable object lock during bucket creation.
  • Tenant users can change the retention policy of buckets and objects.
  • This feature is available for native AWS S3 and Cloudian HyperStore version 7.2.2.1 or later.
See Edit Object Lock Configuration at the Object Level and Edit Object Lock Configuration at the Bucket Level.

Object Lifecycle

  • Tenant users can define lifecycle rules for buckets.
  • Tenant users can migrate, expire, and purge objects based on prefixes, tags, and durations.
See Working with Lifecycle Rules.

 

Bucket Encryption

  • Tenant users can enable encryption methods for specific buckets.
  • Tenant users can protect objects at rest at the following levels:
    • object level by using the S3 API
    • bucket level by using the S3 API or the VMware Cloud Director Object Storage Extension user interface 
    • tenant level by using the VMware Cloud Director Object Storage Extension user interface

See Edit Bucket Encryption.

 

Bucket Policy

 

Upgrade

You can upgrade directly to VMware Cloud Director Object Storage Extension 2.0 from versions 1.5 and 1.0.1. See Upgrading VMware Cloud Director Object Storage Extension

Supported Browsers

VMware Cloud Director Object Storage Extension is compatible with Internet Explorer 11 and the current and last major versions of the following browsers:

  • Google Chrome
  • Mozilla Firefox
  • Microsoft Edge

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.

Product Documentation

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.

Known Issues

  • Multipart upload to a folder fails with exceptions

    If the target for a multipart upload is a folder, the process fails.

    Workaround: To work around this issue, set the HTTP request header to Accept: application/xml.

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