Add dt-sharded-compact reproducer scenario#3907
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Build failed (check pipeline). Post ✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 03m 09s |
|
recheck |
|
Build failed (check pipeline). Post ✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 21m 46s |
New reproducer for the dt-sharded deployment topology which uses per-service dedicated galera, rabbitmq and mamcached clusters. Based on dt-vhosts-compact with designateext network removed (not used by dt-sharded) and ceph/service-values paths adjusted. Signed-Off-By: Luca Miccini <lmiccini@redhat.com> Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
Do we have any testproject running this new scenario? |
openshift-merge-bot
Bot
merged commit a74a0d2
into
openstack-k8s-operators:main
Add dt-sharded deployment topology with per-service galera, rabbitmq and memcached New deployment topology for testing per-service database, message bus, and cache sharding. Each OpenStack service gets a dedicated galera cluster, a dedicated rabbitmq cluster, and a dedicated memcached instance, all with replicas:1. Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com Depends-on: openstack-k8s-operators/ci-framework#3907 Reviewed-by: Andrew Bays <andrew.bays@gmail.com> Reviewed-by: John Fulton <johfulto@redhat.com> Reviewed-by: Luca Miccini
4 participants
New reproducer for the dt-sharded deployment topology which uses per-service dedicated galera, rabbitmq and memcached clusters.
Replicas are initially set to 1 for these services to allow deploying it on small compact clusters, can (should) be scaled to 3 and have proper anti-affinity if deployed on properly sized openshift clusters.
Related: openstack-k8s-operators/architecture#752