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
mgr/rgw: adding support for rgw multisite #47708
Conversation
4808d24
to
fb334a5
Compare
d5c780f
to
5afd564
Compare
5afd564
to
883f305
Compare
|
jenkins retest this please |
|
cc @yehudasa revisiting the description from #42710, i think we need to run the additional zones need to use the this workflow is necessary to support deployments that span ceph clusters |
a76c3d7
to
ef19265
Compare
Signed-off-by: Redouane Kachach <rkachach@redhat.com>
Signed-off-by: Redouane Kachach <rkachach@redhat.com>
96d1575
to
34ebd7c
Compare
Signed-off-by: Redouane Kachach <rkachach@redhat.com>
Signed-off-by: Redouane Kachach <rkachach@redhat.com>
Signed-off-by: Redouane Kachach <rkachach@redhat.com>
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.
looks like all of my comments have been addressed pending any potential continuing discussions on the endpoints. Will do another in depth look over around when we start testing this but it seems to generally look good.
Adding logic to modify the master zonegroup endpoints Do no call pull realm when modifying zone Only update the endpoints if the modified zone is master Adding support to set custom endpoints when creating realm or zone Signed-off-by: Redouane Kachach <rkachach@redhat.com>
d49588d
to
5b6e99d
Compare
|
jenkins test make check |
|
jenkins test make check arm64 |
Signed-off-by: Redouane Kachach <rkachach@redhat.com>
|
jenkins test make check |
|
jenkins test make check arm64 |
|
jenkins test windows |
|
jenkins test make check arm64 |
|
jenkins test dashboard cephadm |
Signed-off-by: Redouane Kachach <rkachach@redhat.com>
|
Failures tracked by:
It's a lot of failures, but other than the the last one, they are all things we were aware of before the run (even the dead mgr-nfs-upgrade job had a |
|
jenkins retest this please |
|
jenkins test make check |
|
jenkins test dashboard cephadm |
Fixes: https://tracker.ceph.com/issues/57160
Related PRs:
#50237
#50020
#50275
#48552
This effort builds on top of #42710 to add support for an easy RGW multi-site deployment and configuration. User should be able to create the corresponding RGW entities (realm, zonegroup and zone) and control the rgw daemons deployment by using a simple spec such as the following:
Where the user in addition to specifying the the
realm/zonegroup/zoneto be created, also can control the details of RGW daemons deployments such as placement, port, etc. The RGW spec format is the same as used by cephadm so the user can provide advanced options already supported by cephadm RGW configuration such as SSL configuration.Once deployed, the user can get the corresponding tokens for the available realms by using the command
ceph rgw realm tokenswhich print the corresponding token for each realm.Following is an example of this command output:
By using the token, the user can create and sync new zones on the secondary cluster easily by providing a spec such as the following (please, notice the usage of the token as part of the spec). Again, the format of this spec is the same used by cephadm so the user can use all the options already supported by the orchestrator.
This spec is used to create the secondary zone by running the command:
ceph rgw zone create -i <spec-file>.yamlThis should create the secondary zone by using the provided token and start the RGW synchronization process. Following is an example of the sync status of the new created zone.
Note:
In both specs batch mode is supported so the user can provide multiple specs separated by
---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. "pacific"), please refer to Submitting Patches to Ceph - Backports for the proper workflow.
Checklist
Show available Jenkins commands
jenkins retest this pleasejenkins test classic perfjenkins test crimson perfjenkins test signedjenkins test make checkjenkins test make check arm64jenkins test submodulesjenkins test dashboardjenkins test dashboard cephadmjenkins test apijenkins test docsjenkins render docsjenkins test ceph-volume alljenkins test ceph-volume toxjenkins test windows