Monday, November 28, 2022
HomeCloud ComputingOSE 2.1.1 is now GA! What are the important thing enhancements?

OSE 2.1.1 is now GA! What are the important thing enhancements?

We’re glad to announce that OSE 2.1.1 is now usually obtainable. This upkeep launch provides to its predecessor OSE 2.1 the power to make the most of object lock and tagging for ECS 3.6.

Why is that this necessary?

Beforehand, Cloud Director tenants utilizing ECS weren’t capable of apply object lock and tagging to their S3 buckets as a result of used tenant consumer mapping. In OSE 2.1, an ECS object consumer is mapped to the tenant administrator account. The ECS object consumer is a world useful resource and is a consumer of the ECS information retailer. An object consumer can have privileges to learn and write buckets, and objects inside the namespace to which they’re assigned. Thus, the lack to individually apply object lock and tagging to an S3 bucket.

How is now totally different?

Consumer mapping in OSE 2.1.1 is achieved via using the IAM service of ECS 3.6. The IAM mapping permits VCD customers to be mapped to ECS 3.6 customers and customers created in VCD to be obtainable in ECS as properly. The previous ECS mapping utilizing an object consumer didn’t enable this granularity, thus the lack for OSE to offer particular person object lock and tagging within the earlier releases.

How does the OSE 2.1.1 tenant consumer mapping work?

After you put in and configure OSE 2.1.1 after which launch it within the Cloud Director supplier portal, you’ll discover the next notification:

Determine 1: Object Storage Extension 2.1.1 IAM Consumer Mapping

It helps you turn from the previous tenant consumer mapping, utilizing ECS object consumer to the brand new – ECS IAM consumer.

Observe: The change is elective and as soon as utilized can’t be reverted as soon as in place!

After you full the change, you’ll be able to create Cloud Director customers and sync them along with your ECS 3.6. First, you might want to apply the usual consumer creation process in Cloud Director.

Observe: After the brand new consumer logs in to Cloud Director, a document for this consumer will likely be created in ECS 3.6.

Go to the ECS 3.6 Administration Console, IAM part and verify if this consumer seems for the tenant org namespace. The ID of the namespace will be taken from the Cloud Director Tenant listing within the supplier portal. That is how the synced-in Cloud Director consumer will appear like in ECS 3.6.

Determine 2: Cloud Director Consumer Syncked with ECS 3.6

Object Lock and Tagging for ECS 3.6

The article lock and tagging in OSE 2.1.1 for ECS 3.6 provides the identical performance as for Cloudian and AWS. You’ll be able to apply an object lock to guard your bucket content material from malicious or unintended deletion.

Determine 3: Object Lock for ECS 3.6 Buckets

Object tagging lets you categorize objects by making use of a key and worth. See an instance under:

Determine 4: Object Tagging for ECS 3.6 Buckets

What else does OSE 2.1.1 provide?

One other good thing about the OSE 2.1.1 mapping for ECS 3.6 is that customers can have their entry keys rotated. OSE 2.1.1 retains the previous static entry key for a consumer but additionally provides a brand new one that may be rotated. You’ll be able to delete the previous static entry key if there aren’t any consumer functions which might be utilizing it.

Determine 5: Entry Key Rotation for Tenant Customers

Along with ECS 3.6 enhancements, OSE 2.1.1 helps 3 extra working programs: Photon OS 3+, Debian 10+, and Ubuntu 18+.

Determine 6: Supported Operations Techniques by OSE 2.1.1

The set up of OSE will be made with a deb file (obtainable from Nonetheless, the set up course of for the brand new working programs stays the identical.

Ought to I improve to OSE 2.1.1?

In case you are utilizing ECS 3.6, then improve to OSE 2.1.1 to totally make the most of the enhancements it provides. In case you are utilizing one other S3 storage vendor, then you’ll be able to follow OSE 2.1.

The best way to improve to OSE 2.1.1?

The improve course of stays the identical on this launch. What you might want to do is:

  1. Uninstall the earlier OSE model. See Uninstall VMware Cloud Director Object Storage Extension.
  2. Put together the database if operating OSE 1.0 or 1.5. See Put together the Database for Improve.
  3. Migrate information if you’re utilizing OSE 1.0 or 1.5. See Migrate VMware Cloud Director Object Storage Extension Information.
  4. Set up and configure OSE 2.1.1. See Set up VMware Cloud Director Object Storage Extension.


  1. OSE 2.1.1 Announcement Weblog
  2. OSE 2.1.1 Launch Notes
  3. OSE 2.1.1 RPM & Deb
  4. OSE 2.1.1 Official Documentation
  5. OSE 2.1.1 Reference Design White Paper


Please enter your comment!
Please enter your name here

Most Popular

Recent Comments