rgw/cloud-transition: Include LocationConstraint while transitioning data to AWS non-default regions#66038
Conversation
|
jenkins test windows |
|
should we plan for backports? would this go all the way to squid? |
That's right. Will update tracker |
81bc4d7 to
ed98301
Compare
|
jenkins test docs |
cbodley
left a comment
There was a problem hiding this comment.
tier config changes look great 👍
ed98301 to
7860811
Compare
Add a new tier-config option "location_constraint" to be configured while using AWS non-default regions. Signed-off-by: Soumya Koduri <skoduri@redhat.com>
if the host_style is set to "Virtual", the endpoint URL and host should be set to "<bucket_name>.host" while sending requests. Signed-off-by: Soumya Koduri <skoduri@redhat.com>
7860811 to
a3cba03
Compare
|
@anrao19 the tetuhology failures reported above doesn't seem related to this PR. But to be sure, please include this PR too in your next teuthology run and share the results. |
|
Pr testing completed , Approved by @ivancich details are in :https://tracker.ceph.com/issues/73724, |
|
This is an automated message by src/script/redmine-upkeep.py. I have resolved the following tracker ticket due to the merge of this PR: No backports are pending for the ticket. If this is incorrect, please update the tracker Update Log: https://github.com/ceph/ceph/actions/runs/19259685396 |
AWS expects
LocationConstraintto be passed as an additional parameter while creating bucket to non-default region which is currently missing in the cloud-transition code,From https://docs.aws.amazon.com/cli/latest/reference/s3api/create-bucket.html,
"Regions outside of us-east-1 require the appropriate LocationConstraint to be specified in order to create the bucket in the desired region."A new tier-config option
location_constraintis added to be configured while transitioning data to AWS non-default regions.Also fixed minor issues with using virtual-hosted style URLs in REST client code.
Fixes: https://tracker.ceph.com/issues/73626
Signed-off-by: Soumya Koduri skoduri@redhat.com
Contribution Guidelines
To sign and title your commits, please refer to Submitting Patches to Ceph.
If you are submitting a fix for a stable branch (e.g. "quincy"), please refer to Submitting Patches to Ceph - Backports for the proper workflow.
When filling out the below checklist, you may click boxes directly in the GitHub web UI. When entering or editing the entire PR message in the GitHub web UI editor, you may also select a checklist item by adding an
xbetween the brackets:[x]. Spaces and capitalization matter when checking off items this way.Checklist
Show available Jenkins commands
jenkins test classic perfJenkins Job | Jenkins Job Definitionjenkins test crimson perfJenkins Job | Jenkins Job Definitionjenkins test signedJenkins Job | Jenkins Job Definitionjenkins test make checkJenkins Job | Jenkins Job Definitionjenkins test make check arm64Jenkins Job | Jenkins Job Definitionjenkins test submodulesJenkins Job | Jenkins Job Definitionjenkins test dashboardJenkins Job | Jenkins Job Definitionjenkins test dashboard cephadmJenkins Job | Jenkins Job Definitionjenkins test apiJenkins Job | Jenkins Job Definitionjenkins test docsReadTheDocs | Github Workflow Definitionjenkins test ceph-volume allJenkins Jobs | Jenkins Jobs Definitionjenkins test windowsJenkins Job | Jenkins Job Definitionjenkins test rook e2eJenkins Job | Jenkins Job DefinitionYou must only issue one Jenkins command per-comment. Jenkins does not understand
comments with more than one command.