-
Notifications
You must be signed in to change notification settings - Fork 619
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
[cinder-csi-plugin] support ignore-volume-az #1307
[cinder-csi-plugin] support ignore-volume-az #1307
Conversation
Build succeeded.
|
Build succeeded.
|
Build succeeded.
|
Build succeeded.
|
Build succeeded.
|
Build failed.
|
I have verified this PR against openstack which compute zones does not match to volume zone, and it works. However, I will still verify this in openstack which compute zones match to volume zones (and using topology). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/retest cloud-provider-openstack-multinode-csi-migration-test |
@zetaab: The
Use In response to this:
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/test-infra repository. |
how to restart that one failing test? |
/test pull-cloud-provider-openstack-test @zetaab due to theopenlab/openlab#603 , we are blocked now |
/retest |
Build succeeded.
|
Build succeeded.
|
Build succeeded.
|
we can try following to overwrite, but I am not sure it's a good way .. |
Build succeeded.
|
Build succeeded.
|
/lgtm |
Build failed.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve cancel
@@ -67,6 +67,8 @@ These configuration options pertain to block storage and should appear in the `[ | |||
Optional. To configure maximum volumes that can be attached to the node. Its default value is `256`. | |||
* `rescan-on-resize` | |||
Optional. Set to `true`, to rescan block device and verify its size before expanding the filesystem. Not all hypervizors have a /sys/class/block/XXX/device/rescan location, therefore if you enable this option and your hypervizor doesn't support this, you'll get a warning log on resize event. It is recommended to disable this option in this case. Defaults to `false` | |||
* `ignore-volume-az` | |||
Optional. Set to `true`, incase volume AZ is different from node AZ and to avoid populating accessible topologies to volume AZ. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we have a more detailed description of this option? I'm a little confused about how to configure this option properly, e.g. What's the default value? In which case it should be set to true?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@lingxiankong @zetaab updated. Let me know if its bit more clear now. Thanks.
@ramineni can you add more detailed description to documentation? You can perhaps take a look legacy cinder if that contains helpful information |
4575be7
to
06184a2
Compare
the wording looks good to me |
Build succeeded.
|
Build succeeded.
|
Build succeeded.
|
Build succeeded.
|
Build succeeded.
|
Build succeeded.
|
/lgtm @zetaab Please approve if it looks good to you as well. |
this has been here for a while and already tested works well |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jichenjc 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 |
* [cinder-csi-plugin] support ignore-volume-az * Update using-cinder-csi-plugin.md
What this PR does / why we need it:
Which issue this PR fixes(if applicable):
fixes #1300
Special notes for reviewers:
Release note: