+1 (pending blocking JIRAs) On Tue, May 10, 2022 at 11:54 AM Siyao Meng <si...@apache.org> wrote:
> Hi Ozone devs, > > I am starting this discussion thread for proposing to merge the Ozone S3 > Multi-Tenancy feature branch (HDDS-4944) to the master branch. > > S3 multi-tenancy allows multiple S3-accessible volumes to be created. > Each volume can be managed separately by their own tenant admins via CLI > for tenant creation and user operations. Before S3 Multi-Tenancy, all S3 > access to Ozone (via S3 Gateway) are > confined to a single designated S3 volume (s3v volume by default). > > The feature has been in development for about 14 months now. Currently, > functions like tenant creation/deletion (along with volume and bucket > Ranger policy creation), user assign/revoke, tenant admin assign/revoke are > implemented and tested working. Documentations have also been added. > > The S3 multi-tenancy feature umbrella JIRA is HDDS-4944 > <https://issues.apache.org/jira/browse/HDDS-4944> > > There are only 3 merge blocking JIRAs left (all under review) at the > moment, which should hopefully be resolved in a week or two: > > 1. HDDS-6612 <https://issues.apache.org/jira/browse/HDDS-6612>. Add a > config key to enable or disable S3 Multi-Tenancy feature globally > 2. HDDS-6371 <https://issues.apache.org/jira/browse/HDDS-6371>. > Implement Ranger policy and role background sync service in OM > 3. HDDS-6701 <https://issues.apache.org/jira/browse/HDDS-6701>. (a > follow-up to the 2nd) Add proper locking between Ranger Background Sync > Service and tenant requests > > > For more information (feature overview, Docker dev and production setup > guide, CLI guide and access control guide), please check out the S3 > multi-tenancy feature wiki page here: > > https://cwiki.apache.org/confluence/display/OZONE/S3+Multi-Tenancy+%28HDDS-4944%29+Merge+Checklist > > > Thanks, > Siyao > -- Thanks & Regards, Aravindan
