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

0/5 No votes

Report this app

Description

[ad_1]

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 vital?

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 knowledge 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 completely different?

Person 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 nicely. The previous ECS mapping utilizing an object consumer didn’t permit this granularity, thus the lack for OSE to supply 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 Person Mapping

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

Observe: The swap is non-obligatory and as soon as utilized can’t be reverted as soon as in place!

After you full the swap, you possibly can create Cloud Director customers and sync them along with your ECS 3.6. First, you must apply the usual consumer creation process in Cloud Director.

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

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

Determine 2: Cloud Director Person Syncked with ECS 3.6

Object Lock and Tagging for ECS 3.6

The item lock and tagging in OSE 2.1.1 for ECS 3.6 provides the identical performance as for Cloudian and AWS. You may apply an object lock to guard your bucket content material from malicious or unintentional deletion.

Determine 3: Object Lock for ECS 3.6 Buckets

Object tagging permits you to categorize objects by making use of a key and worth. See an instance beneath:

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 in addition provides a brand new one that may be rotated. You may delete the previous static entry key if there are not any consumer functions which are 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 could be made with a deb file (obtainable from www.customerconnect.vmware.com). Nonetheless, the set up course of for the brand new working programs stays the identical.

Ought to I improve to OSE 2.1.1?

If you’re utilizing ECS 3.6, then improve to OSE 2.1.1 to totally make the most of the enhancements it provides. If you’re utilizing one other S3 storage vendor, then you possibly can stick with OSE 2.1.

improve to OSE 2.1.1?

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

  1. Uninstall the earlier OSE model. See Uninstall VMware Cloud Director Object Storage Extension.
  2. Put together the database if working OSE 1.0 or 1.5. See Put together the Database for Improve.
  3. Migrate knowledge in case you are 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.

Assets

  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

[ad_2]

Leave a Reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.