[HDDS-5362] [FSO] Support bucket layout in OM

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Component/s: Ozone Manager
• Labels: pull-request-available
• Assignee: Aryan Gupta Assign to me
• Reporter: Aryan Gupta
• Created: 21/Jun/21 07:48
• Updated: 26/Aug/21 05:21
• Resolved: 10/Aug/21 15:45

Description

We are introducing 3 kind of bucket layouts as of now in Ozone:

FSO (File System Optimized):- For this bucket, we need the configuration “ozone.om.enable.filesystem.paths” to be set to true.
Behavior:

• Supports atomic rename and delete operations.
• Files written to this bucket can be read via S3.
• Keys written via S3 with a delimiter “/” will create intermediate directories.
• This bucket will allow interoperability between S3 and FS APIs.

OBS (Object Store):- For this bucket, we need the configuration “ozone.om.enable.filesystem.paths” to be set to false.
Behavior:

• Keys written to this bucket will behave as a pure object-store.
• Keys written via S3 with a delimiter “/” will not create intermediate dirs.
• This bucket will not allow interoperability between S3 and FS APIs.

LEGACY:- This bucket layout has been introduced to handle the case of upgrading an existing cluster with pre-created buckets. Users can’t create a LEGACY bucket explicitly via the Ozone client.

Issue Links

• links to: GitHub Pull Request #2357