Versions Compared

Key

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

...

Git branch: https://github.com/apache/ozone/tree/HDDS-4944

Compare (feature branch rebase in-progress): https://github.com/apache/ozone/compare/master...HDDS-4944

Compare with my fork (rebased, CI in progress): https://github.com/apache/ozone/compare/HDDS-4944...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 Basic HTTP authentication), in addition to the requirements above, the following configs need to be added to Ozone Manager's ozone-site.xml, as documented here in the doc as well:

Code Block
languagexml
<property>
   <name>ozone.om.multitenancy.enabled</name>
   <value>true</value>
</property>
<property>
	<name>ozone.om.ranger.https-address</name>
	<value>https://RANGER_HOST:6182</value>
</property>
<property>
	<name>ozone.om.ranger.https.admin.api.user</name>
	<value>RANGER_ADMIN_USERNAME</value>
</property>
<property>
	<name>ozone.om.ranger.https.admin.api.passwd</name>
	<value>RANGER_ADMIN_PASSWORD</value>
</property>


With To enable multi-tenancy with Ranger Java client (pending

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyHDDS-5836
merge), clear text Ranger admin user name and password will no longer be necessary. Rather it the Ranger Java client uses the existing OM Kerberos keytab and 

Code Block
languagexml
<property>
   <name>ozone.om.multitenancy.enabled</name>
   <value>true</value>
</property>
<property>
	<name>ozone.om.ranger.https-address</name>
	<value>https://RANGER_HOST:6182</value>
</property>
<property>
	<name>ozone.om.ranger.https.admin.api.user</name>
	<value>RANGER_ADMIN_USERNAME</value>
</property>
<property>
	<name>ozone.om.ranger.https.admin.api.passwd</name>
	<value>RANGER_ADMIN_PASSWORD</value>
</property>

1. builds/intermittent test failures

...