[HDDS-10390] MiniOzoneCluster to support S3G

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Implemented
• Fix Version/s: 2.0.0
• Labels: S3 pull-request-available
• Assignee: Ivan Andika
• Reporter: Duong
• Created: 16/Feb/24 19:09
• Updated: 07/Dec/24 08:40
• Resolved: 13/Oct/24 16:21

Description

MiniOzoneCluster should support creating S3G instances and provide access to S3G via an AWS S3 client (AWS Java SDK).

This will make it a lot easier to test and debug issues in S3G.

Issue Links

• causes: HDDS-11879 MiniKMS cannot be started due to ClassNotFoundException: com.sun.jersey....ServletContainer
• duplicates: HDDS-607 Support S3 testing via MiniOzoneCluster
• is a child of: HDDS-9931 Improve unit/integration tests
• is related to: HDDS-11539 OzoneClientCache @PreDestroy is never called
• relates to: HDDS-11574 Ozone client leak in TestS3SDKV1
• relates to: HDDS-1606 ozone s3g cannot started caused by NoInitialContextException: xxx java.naming.factory.initial
• relates to: HDDS-11575 Improve S3G integration tests
• relates to: HDDS-11738 Fix S3 ACL logic
• links to: GitHub Pull Request #7281
• links to: Github Pull Request #7281