Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Git branch: https://github.com/apache/ozone/tree/Feature branch HDDS-4944 has been merged to master on May 29.


Git branchCompare (feature branch rebase in-progress): https://github.com/apache/ozone/comparetree/master...HDDS-4944

Compare with my fork (rebased, CI in progress, will be pushed to upstream once CI passed): https://github.com/apache/ozone/compare/HDDS-4944master...smengcl:HDDS-4944


For a quick intro to the S3 multi-tenancy feature, here is an excerpt from the documentation:

...

To enable multi-tenancy with Ranger Java client (

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyHDDS-5836
), clear text Ranger admin user name and password will no longer be necessary. Rather it the Ranger Java client (re)uses the existing OM Kerberos principal and keytab config when enabling Ozone security with Kerberos auth. Therefore, only two extra config keys are necessary to enable the feature:

...

`ozone.om.kerberos.principal` and `ozone.om.kerberos.keytab.file` should have been configured already.

NOTE: Ranger Java client patch is merged. BUT the authorizer implementation switch hasn't happened. Partially due to Ranger 2.3.0 hasn't been released yet. Therefore, as of now it can only use the Ranger Basic HTTP authentication approach. Further patch will be done to complete the switch.


1. builds/intermittent test failures

...