VMware Cloud Director Object Storage Extension 2.1.1 | 24 FEB 2022 | Build 19362139 Check for additions and updates to these release notes. |
VMware Cloud Director Object Storage Extension version 2.1.1 includes the following new features:
Support for additional operating systems
This release adds support for the following operating systems:
For more information on how to install VMware Cloud Director Object Storage Extension, see Installing and Configuring VMware Cloud Director Object Storage Extension.
Object lock and object tagging for Dell ECS 3.6 users
VMware Cloud Director Object Storage Extension 2.1.1 introduces new user mapping for tenants who use Dell ECS 3.6. VMware Cloud Director tenant users are now mapped to ECS Identity and Access Management (IAM) users and no longer to ECS object users.
You can upgrade user mapping with a single click in the cloud provider portal. The upgrade is optional.
The upgrade of user mapping allows you to use the object lock and object tagging features. The object lock feature protects an object version from accidental or malicious deletion. You activate the object lock and set a retention policy when you create a bucket. Object tagging allows users to categorize buckets by assigning tags to individual objects using key-value pairs.
You can upgrade directly to VMware Cloud Director Object Storage Extension 2.1.1 from versions 2.1 and 2.0. See Upgrading VMware Cloud Director Object Storage Extension.
Sync Now option does not work when synchronizing buckets
When objects or folders are uploaded through the S3 API, the changes are not showing up in VMware Cloud Director Object Storage Extension after clicking the Sync Now button.
The usage of the S3 HEAD request method on a folder causes the service to fail with an error
When a folder contains huge objects, repeated calls of the HEAD method on the folder leads to an OutOfMemoryError
.
Restore from a vApp backup times out
If the vApp backup contains NVRAM files, the restoring of the backup fails with a Timed Out
error.
S3 API requests authenticated with application credentials do not support the following use cases:
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.
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.
If you are using ECS storage, S3 API, or the Find a Bucket feature, you cannot visit a bucket that belongs to a different tenant organization in the ECS platform.
All documentation is available on the VMware Cloud Director Object Storage Extension Documentation page.
NEW Unable to add catalogs from VMware Cloud Director Object Storage Extension to VMware Cloud Director libraries for Cloud Director 10.3 and later
When tenant users create a new catalog and click "Add to libraries" to upload an object, the import of the object fails.
Workaround: None
NEW The Permissions and Lifecycle tabs in the tenant portal are not displayed
Tenant users that are mapped to IAM of ECS 3.6 or later cannot view the Permissions and Lifecycle tabs in the VMware Cloud Director Object Storage Extensions tenant portal.
Workaround: None
NEW Kubernetes clusters are not listed in VMware Cloud Director Object Storage Extension for Container Service Extension (CSE) 3.2 and later
When a tenant administrator tries to back up a Kubernetes cluster for CSE 3.2 or later, the tenant cannot see the Kubernetes clusters list in VMware Cloud Director Object Storage Extension.
Workaround:
The cluster is now listed in the Kubernetes Clusters tab.
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 Now button repeatedly until the synchronization task completes successfully.