-
Notifications
You must be signed in to change notification settings - Fork 77
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
Add integration test for Ceph RGW multisite sync policies feature #1193
Add integration test for Ceph RGW multisite sync policies feature #1193
Conversation
5d96f9e
to
0ab575e
Compare
8994bad
to
fd2fec1
Compare
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.
one comment.
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.
LGTM
* Rename `test_004_migration_and_multisite_failover` to `test_100_migration_and_multisite_failover` * This will allow us to insert more multi-site tests after `test_003`, before scale-down scenario is run in `test_100_migration_and_multisite_failover`. * Rename `test_005_virtual_hosted_bucket` to `test_101_virtual_hosted_bucket`. * This was previously run after `test_004_migration_and_multisite_failover`. So, we rename the test case to `test_101` to keep the same order. Signed-off-by: Ionut Balutoiu <[email protected]>
9d2bfc7
to
c633240
Compare
I rebased this PR against latest upstream main branch. I noticed that a new test case ( Besides renaming See commit CephRGWTest: Reorder test cases from this PR. Besides the tests re-order, I also updated the new test case |
If `self.promote_rgw_to_primary(self.primary_rgw_app)` is executed before sites are syncronised, the sites will not be syncronised after. Signed-off-by: Ionut Balutoiu <[email protected]>
Signed-off-by: Ionut Balutoiu <[email protected]>
c633240
to
5054a79
Compare
Also, I included a small fix that might cause failures sometimes (it happened on my local Zaza env). |
Signed-off-by: Ionut Balutoiu <[email protected]>
a7cf06f
to
d2b38e6
Compare
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.
LGTM, Thanks for the tests @ionutbalutoiu
* Update charm-ceph-radosgw from branch 'master' to 1f33f800fbfe58279e4e01aed344aa788a2a683b - Merge "Add group policy configuration" - Add group policy configuration Allow configuration of a zone group default sync policy. This is useful in scenarios where we want to have selective buckets sync. Valuable especially with the new `cloud-sync` relation. This is based on Ceph multisite sync policy: https://docs.ceph.com/en/latest/radosgw/multisite-sync-policy/ Additionally, three more Juju actions are added to selectively enable, disable, or reset buckets sync: * `enable-buckets-sync` * `disable-buckets-sync` * `reset-buckets-sync` These new actions are meant to be used in conjunction with a default zone group sync policy that allows syncing, but it's disabled by default. Change-Id: I4a8076192269aaeaca50668ebcebc0a52c6d2c84 func-test-pr: openstack-charmers/zaza-openstack-tests#1193 Signed-off-by: Ionut Balutoiu <[email protected]>
Allow configuration of a zone group default sync policy. This is useful in scenarios where we want to have selective buckets sync. Valuable especially with the new `cloud-sync` relation. This is based on Ceph multisite sync policy: https://docs.ceph.com/en/latest/radosgw/multisite-sync-policy/ Additionally, three more Juju actions are added to selectively enable, disable, or reset buckets sync: * `enable-buckets-sync` * `disable-buckets-sync` * `reset-buckets-sync` These new actions are meant to be used in conjunction with a default zone group sync policy that allows syncing, but it's disabled by default. Change-Id: I4a8076192269aaeaca50668ebcebc0a52c6d2c84 func-test-pr: openstack-charmers/zaza-openstack-tests#1193 Signed-off-by: Ionut Balutoiu <[email protected]>
Thanks, lgtm! -- Merged |
Allow configuration of a zone group default sync policy. This is useful in scenarios where we want to have selective buckets sync. Valuable especially with the new `cloud-sync` relation. This is based on Ceph multisite sync policy: https://docs.ceph.com/en/latest/radosgw/multisite-sync-policy/ Additionally, three more Juju actions are added to selectively enable, disable, or reset buckets sync: * `enable-buckets-sync` * `disable-buckets-sync` * `reset-buckets-sync` These new actions are meant to be used in conjunction with a default zone group sync policy that allows syncing, but it's disabled by default. Change-Id: I4a8076192269aaeaca50668ebcebc0a52c6d2c84 func-test-pr: openstack-charmers/zaza-openstack-tests#1193 Signed-off-by: Ionut Balutoiu <[email protected]> (cherry picked from commit 4e608c1) Signed-off-by: Utkarsh Bhatt <[email protected]>
Add Ceph RGW multisite sync policies integration test.
Add integration test for the Multisite sync policies feature proposed to the
upstream
ceph-radosgw
Juju charm: