Skip to content
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

Set Cinder customServiceConfig globally in DCN DT #2582

Merged

Conversation

fultonj
Copy link
Contributor

@fultonj fultonj commented Dec 3, 2024

The customServiceConfig for cinder in the DCN DT is used to set the storage_availability_zone. We wish to do this for all Cinder services in the default site (az0), not just for cinderAPI or cinderBackup as the AZ was missing from the cinder-scheduler. Thus, we will move it to the global section under the cinder template and out of the cinderAPI and cinderBackup since they will inherit it. The backend_availability_zone is kept inside of the cinderVolumes loop since it needs to be set for other AZs. There's no harm in letting the loop set it for az0 and it's simpler to do that than add a conditional.

Jira: https://issues.redhat.com/browse/OSPRH-11915

@github-actions github-actions bot marked this pull request as draft December 3, 2024 13:49
Copy link

github-actions bot commented Dec 3, 2024

Thanks for the PR! ❤️
I'm marking it as a draft, once your happy with it merging and the PR is passing CI, click the "Ready for review" button below.

The customServiceConfig for cinder in the DCN DT is used
to set the storage_availability_zone. We wish to do this
for all Cinder services in the default site (`az0`), not
just for cinderAPI or cinderBackup as the AZ was missing
from the cinder-scheduler. Thus, we will move it to the
global section under the cinder template and out of the
cinderAPI and cinderBackup since they will inherit it.
The backend_availability_zone is kept inside of the
cinderVolumes loop since it needs to be set for other
AZs. There's no harm in letting the loop set it for az0
and it's simpler to do that than add a conditional.

Jira: https://issues.redhat.com/browse/OSPRH-11915

Signed-off-by: John Fulton <[email protected]>
@fultonj fultonj marked this pull request as ready for review December 5, 2024 11:35
Copy link
Contributor

@hjensas hjensas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@pablintino
Copy link
Collaborator

/approve

Copy link
Contributor

openshift-ci bot commented Dec 10, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: pablintino

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-bot openshift-merge-bot bot merged commit 9c95009 into openstack-k8s-operators:main Dec 10, 2024
5 checks passed
@fultonj
Copy link
Contributor Author

fultonj commented Dec 12, 2024

/cherry-pick 18.0-fr1

@openshift-cherrypick-robot

@fultonj: new pull request created: #2599

In response to this:

/cherry-pick 18.0-fr1

Instructions 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants