UPSTREAM: 44798: Cinder: Automatically Generate Zone if Availability in Storage Class is not Configured #14159
+80
−37
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.
Backport of Kubernetes PR kubernetes/kubernetes#44798.
In case the
availability
parameter is not configured in a cinder Storage Class the cinder volume is always provisioned in thenova
availability zone. That is incorrect.Now, the cinder volume is provisioned in a zone that is generated by an algorithm from the set of zones available in the cluster.
Positive side-effect: cinder volumes for individual pods in a StatefulSet are provisioned in unique zones. This increases the StatefulSet resilience.
IMPORTANT: the backport was NOT tested. Testing requires an OpenStack cluster with at least 2 availability zones.
This PR resolves this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1447568
Corresponding documentation PR: openshift/openshift-docs#4409
@jsafrane @rootfs PTAL
@childsb @eparis please, merge.