© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
@jameinel
Indeed OpenStack has AZ concept for VMs and an entirely different concept of AZs for Cinder.
Ceph as a backend is entirely different and we do not need to worry much about availability of data. This bug refers more to cases where cinder backend is NOT ceph. It can be for instance several storage arrays or LVM in each compute node.
In this case, one can define AZs for cinder-volume services and a default AZ for cinder-api.
If you don't define which zone a volume comes from, OpenStack will always go for cinder-api's default_
It means that, in practice, Juju is always deploying to the same zone, even if VMs themselves are sitting across AZs for HA. If we lose that storage array, we lose the entire cluster.
The solution I see is to have a "volume-zone" parameter where I can define from which AZ Juju should pick its disks. That parameter should be enabled on add-machine's constraints so we can also use it on bundles.