Support single GlanceAPI StatefulSet with regular backends#748
Support single GlanceAPI StatefulSet with regular backends#748fmount wants to merge 1 commit intoopenstack-k8s-operators:mainfrom
Conversation
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fmount The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@fmount: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/4e516d1e477d4fceaa6f921a413a8632 ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 38m 22s |
d69e5aa to
cae4627
Compare
Starting with RHOSO 19, Nova and Cinder will adopt Glance's new location API, eliminating the need for default splitting. This change enables single GlanceAPI deployments with supported backends (S3, Ceph, Cinder, Swift) for both greenfield and existing environments. This enables a single Glance StatefulSet deployment with several benefits: - Reduces PVC resource requirements (e.g., halving staging area storage) - Simplify deployment topologies and use cases - Maintains split model for upgrade compatibility Existing split deployments cannot automatically migrate to single layout. Manual migration procedures will be documented separately. Signed-off-by: Francesco Pantano <fpantano@redhat.com>
Starting with
RHOSO 19,NovaandCinderwill adoptGlance's newlocation API,eliminating the need for default splitting.
This change enables
singleGlanceAPIdeployments with supportedbackends(
S3,Ceph,Cinder,Swift) for both greenfield and existing environments.This enables a single Glance
StatefulSetdeployment with several benefits:PVCresource requirements (e.g., halving staging area storage)Note: Existing split deployments cannot automatically migrate to single layout.
Manual migration procedures will be documented separately.
Jira: https://issues.redhat.com/browse/OSPRH-17562