Comment 12 for bug 1945239
Revision history for this message
| Rodrigo Barbieri (rodrigo-barbieri2010) wrote | #12 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
2eb648a
demo site
(Get the code!)
@Freyes: I am not sure I understand your comment, because in my understanding it contradicts it self:
a) host=<value> (or not setting it at all) is for active-passive
b) (the behavior until 21.04) is host=<same_value>.
host=<same_value> is when we want to cluster the cinder-volume services in the way that is not supported/
If you are saying that we *should* be using host=<same_value> for purestorage <= Ussuri,>=Pike, this is incorrect in case of new deployments. For existing deployments sure something should be done to be able to maintain the existing config (host=<same_value>) so the flag doesn't flip and doesn't cause issues (mentioned below)
@Nobuto: that patch is good workaround to achieve a way to maintain the existing config for purestorage. I will further develop this in the other LP.