[HDDS-4440] Design Doc: Use per-request authentication and persistent connections between S3g and OM - ASF JIRA

XML

Word

Printable

JSON

is duplicated by

HDDS-5630 S3G keep connections to OM around leading to slowness

is related to

HDDS-5630 S3G keep connections to OM around leading to slowness

HDDS-5881 Change S3G to OM RPC framework to keep persistent connection across multiple users

links to

GitHub Pull Request #1562

(2 links to)

1.	Create GRPC service definition and for existing Om protocol	Resolved	Neil Joshi
2.	Create and a specific OmTransportFactory for GrpcOmTransport	Resolved	Neil Joshi
3.	Start OM Grpc server as part of the OM bootstrap	Resolved	Neil Joshi
4.	Create implementation of OmTransport which uses Grpc	Resolved	Neil Joshi
5.	Client side unit test	Resolved	Unassigned
6.	Create Ozone s3 authentication token and client authentication transport	Resolved	Neil Joshi
7.	Support s3 authentication on a per request basis	Resolved	Neil Joshi
8.	Enable ACLs and support for all s3 file operations.	Resolved	Neil Joshi
9.	Client side unit tests	Resolved	George Jahad
10.	Update GRPC OmTransport implementation for HA	Resolved	Neil Joshi
11.	Merge master branch including s3g persistent connection changes into feature branch	Resolved	Neil Joshi
12.	Merge from master to resolve CI workflow issues & hrpcOmTransport support	Resolved	Neil Joshi
13.	Enable TLS for GRPC OmTransport implementation	Resolved	Neil Joshi
14.	Track CI workflow tests temporarily disabled for feature branch	Resolved	Neil Joshi
15.	Support hadoop rpc ozone client (non persistent connection)	Resolved	Neil Joshi
16.	Rebase s3g Grpc feature branch to Master through merge.	Resolved	Neil Joshi
17.	Restore S3 Gateway config key check in TestOzoneConfigurationFields	Resolved	Attila Doroszlai
18.	Re-enable s3gateway checks in TestOzoneConfigurationFields int test	Resolved	Unassigned