Cinder: Downstream only describe single backend #446
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When adopting the Cinder volume service in an openstack-operator deployment we can include all backends in a single pod or having a pod for each backend. This is a system administrator preference and both options will work, but we consider that the 1 backend per pod option is considerably superior, so for the downstream documentation we want it to be the only option. This patch makes a couple of small conditional changes so that the quick and dirty solution of creating the cinder configuration is not mentioned downstream.
klgill
approved these changes
May 9, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When adopting the Cinder volume service in an openstack-operator deployment we can include all backends in a single pod or having a pod for each backend.
This is a system administrator preference and both options will work, but we consider that the 1 backend per pod option is considerably superior, so for the downstream documentation we want it to be the only option.
This patch makes a couple of small conditional changes so that the quick and dirty solution of creating the cinder configuration is not mentioned downstream.