errose28 opened a new pull request #2924:
URL: https://github.com/apache/ozone/pull/2924
## What changes were proposed in this pull request?
Use changes from HDDS-5881 to have the access ID passed to the OM to
determine which tenant volume to use for S3 requests. This is a much cleaner
solution than the temporary workaround implemented in HDDS-5645.
This PR deletes many changes from HDDS-5645. It also reverts HDDS-5476,
since the principal of incoming requests will always be that of the s3 gateway,
and access IDs are now carried in a proto field.
Under this PR, we will adopt similar OM <-> S3g compatibility requirements
as HDDS-5881:
- A newer s3g cannot talk to an older OM, since the new s3g will always
use its kerberos principal, not a principal the same as the calling user's
access ID.
- An older s3g can talk to a newer OM, because if the s3 auth fields of
the proto are not set, the OM will default to using the principal used by s3g
as the access ID.
## What is the link to the Apache JIRA
HDDS-6004
## How was this patch tested?
- Existing integration and acceptance tests that were used to test the
original implementation in HDDS-5645.
- The acceptance tests failing after the recent merge with master to the
feature branch should pass after this PR.
- Cross compatibility testing and client versioning is a longer poll item
that is being addressed separately as an upgrade task for all features that may
need it, like EC, FSO, S3 gateway changes, etc.
- It is beyond the scope of this PR, which just uses existing changes.
**Leaving as draft until acc test failures are fixed:
https://github.com/errose28/hadoop-ozone/runs/4528103422**
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
