-
Notifications
You must be signed in to change notification settings - Fork 9.1k
HDDS-1972. Provide example ha proxy with multiple s3 servers back end. #1304
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
💔 -1 overall
This message was automatically generated. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for working on this @bharatviswa504. The setup looks good, but there are a few small changes needed for the acceptance test to pass. S3 tests use http://s3g:9878 as endpoint. To allow it to run unmodified, the proxy service should be named s3g and it should listen on port 9878.
hadoop-ozone/dist/src/main/compose/ozones3-haproxy/docker-compose.yaml
Outdated
Show resolved
Hide resolved
hadoop-ozone/dist/src/main/compose/ozones3-haproxy/docker-compose.yaml
Outdated
Show resolved
Hide resolved
hadoop-ozone/dist/src/main/compose/ozones3-haproxy/haproxy-conf/haproxy.cfg
Outdated
Show resolved
Hide resolved
hadoop-ozone/dist/src/main/compose/ozones3-haproxy/haproxy-conf/haproxy.cfg
Outdated
Show resolved
Hide resolved
|
💔 -1 overall
This message was automatically generated. |
Co-Authored-By: Doroszlai, Attila <[email protected]>
As s3g port is used for s3 proxy.
|
Thank You @adoroszlai for the review. |
|
On my desktop I see tests are passing. |
|
Posted empty commit, to trigger Jenkins run. |
|
/retest |
|
Not sure why test is failing in Jenkins run, but passing locally. |
|
💔 -1 overall
This message was automatically generated. |
|
💔 -1 overall
This message was automatically generated. |
|
💔 -1 overall
This message was automatically generated. |
|
/retest |
hadoop-ozone/dist/src/main/compose/ozones3-haproxy/docker-compose.yaml
Outdated
Show resolved
Hide resolved
…ose.yaml Co-Authored-By: Doroszlai, Attila <[email protected]>
|
/retest |
|
💔 -1 overall
This message was automatically generated. |
|
I see tests are passing locally on my laptop. I was able to test ha-proxy with aws cli. Not able to figure out why on jenkins it is showing not able to connect to http://s3g:9878. For now, I have disabled the test. But this will give an example for users to use ha-proxy setup with S3Gateway Server. (I will open a new Jira(https://issues.apache.org/jira/browse/HDDS-1983) to enable s3 test suite for s3 proxy) |
|
💔 -1 overall
This message was automatically generated. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1
@adoroszlai are you okay to commit this?
| environment: | ||
| ENSURE_SCM_INITIALIZED: /data/metadata/scm/current/VERSION | ||
| command: ["ozone","scm"] | ||
| s3g1: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These can be collapsed into one entry, then we can use scale option. Not a blocker to commit.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, we can do that, but we need to have ha-proxy image which can have some configuration, where we can dynamically configure s3proxy and start/stop.
|
Thank You @arp7 and @adoroszlai for the review. |
Got a +1 from @adoroszlai already, so committed this change. |
Tested it on my laptop:
docker logs: