This repository has been archived by the owner on Jan 20, 2022. It is now read-only.
BUG: OpenStack ignore AvailabilityZone in discovery #351
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
zetaab
changed the title
|
Sorry for the delay ... this makes sense to me. I think that @olemarkus mentioned that there are different ways to set up OpenStack, so I'd like to get his OK as well... |
|
This looks good to me. Thanks @zetaab |
|
Awesome - thanks @zetaab, and @olemarkus for confirming! /approve |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
BUG:
If we have openstack region which do have multiple AZs in computes AND volumes, this whole discovery mechanism does not work at all (similar setup that AWS region has). When doing discovery it should ignore the AZ, no matter what - when mounting volumes it should instead use zones
@justinsb could you check this