[ad_1]
We’re glad to announce that OSE 2.1.1 is now usually accessible. 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 because of the 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 worldwide 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 completely different?
Consumer mapping in OSE 2.1.1 is achieved by 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 accessible in ECS as properly. The outdated 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:
It helps you turn from the outdated tenant consumer mapping, utilizing ECS object consumer to the brand new – ECS IAM consumer.
Be aware: The change is elective and as soon as utilized can’t be reverted as soon as in place!
After you full the change, you possibly can create Cloud Director customers and sync them together with your ECS 3.6. First, you could apply the usual consumer creation process in Cloud Director.
Be aware: After the brand new consumer logs in to Cloud Director, a document 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 listing within the supplier portal. That is how the synced-in Cloud Director consumer will appear like in 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 affords the identical performance as for Cloudian and AWS. You possibly can apply an object lock to guard your bucket content material from malicious or unintended deletion.
Object tagging lets you categorize objects by making use of a key and worth. See an instance beneath:
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 outdated static entry key for a consumer but additionally provides a brand new one that may be rotated. You possibly can delete the outdated static entry key if there aren’t any shopper purposes which are utilizing it.
Along with ECS 3.6 enhancements, OSE 2.1.1 helps 3 extra working methods: Photon OS 3+, Debian 10+, and Ubuntu 18+.
The set up of OSE could be made with a deb file (accessible from www.customerconnect.vmware.com). Nonetheless, the set up course of for the brand new working methods 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 affords. If you’re utilizing one other S3 storage vendor, then you possibly can follow OSE 2.1.
Easy methods to improve to OSE 2.1.1?
The improve course of stays the identical on this launch. What you could do is:
- Uninstall the earlier OSE model. See Uninstall VMware Cloud Director Object Storage Extension.
- Put together the database if operating OSE 1.0 or 1.5. See Put together the Database for Improve.
- Migrate information in case you are utilizing OSE 1.0 or 1.5. See Migrate VMware Cloud Director Object Storage Extension Knowledge.
- Set up and configure OSE 2.1.1. See Set up VMware Cloud Director Object Storage Extension.
Sources
[ad_2]
