+1

Thanks
Hanisha

On Thu, May 26, 2022 at 3:06 PM Ethan Rose <er...@cloudera.com.invalid>
wrote:

> +1
>
> On Thu, May 26, 2022 at 2:06 PM Prashant Pogde <ppo...@cloudera.com.invalid
> >
> wrote:
>
> > +1
> >
> > > On May 23, 2022, at 8:40 PM, Siyao Meng <si...@apache.org> wrote:
> > >
> > > Dear Ozone devs,
> > >
> > >    I am starting this vote thread for merging 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,
> > > Ranger policies and roles synchronization background thread, global
> > config
> > > key to enable S3 Multi-Tenancy feature (disabled by default) are
> > > implemented and tested working. Documentations are added as well.
> > >
> > >  The S3 multi-tenancy feature umbrella JIRA is HDDS-4944
> > > <https://issues.apache.org/jira/browse/HDDS-4944>.
> > >
> > >  We are very close to finishing the final patch (HDDS-6701
> > > <https://issues.apache.org/jira/browse/HDDS-6701> in a week) that we
> > deem
> > > necessary before merging this feature to the master branch.
> > >
> > >  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
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscr...@ozone.apache.org
> > For additional commands, e-mail: dev-h...@ozone.apache.org
> >
> >
>

Reply via email to