Cinder volume service and high availability question
Hello, I am trying to figure out how to get cinder volume service to use a virtual name for the cinder volume host. We have three controllers that are setup with keepalived and haproxy with a virtualized servername that is used in the various openstack .conf files. This allows either server to shutdown and we can still access the web interface, create vms and volumes, etc. because the virtual hostname is used in all the configurations. However, for cinder volumes, it puts the hostname of the server in os-vol-host-attr:host rather than my virtual name. This causes issues if the controller that was used to create the volume is down, we can't easily manage the volume without modifying that field in the cinder database. If the virtual name could be used, either server could manage the volume with the backend, with no manual changes to the db. The only server related setting in my cinder.conf is my_ip, and that is the ip of the actual server, not the virtual ip Is active/active cluster not supported with cinder?
Hi, take a look at [0], and I also had a brief conversation about cinder active/active on this list [1]. But in my test environment it was sufficient to set the "cluster" value in cinder.conf: [DEFAULT] # Name of this cluster. Used to group volume hosts that share the same backend # configurations to work in HA Active-Active mode. (string value) cluster = <CLUSTER_NAME> In my lab, I also used zookeeper, and it worked as expected. I just didn't have the chance to use it in production anywhere (yet). But if my notes are correct, those two things suffice to make it work (coordination service and "cluster" name). Read through Gorka's notes, I think they're important. And I'll also mention again that we use our own deployment method based on package installs, so I can't comment on kolla, devstack etc. Regards, Eugen [0] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.... [1] https://lists.openstack.org/pipermail/openstack-discuss/2022-September/03055... Zitat von Jim Kilborn <jim@kilborns.com>:
Hello,
I am trying to figure out how to get cinder volume service to use a virtual name for the cinder volume host.
We have three controllers that are setup with keepalived and haproxy with a virtualized servername that is used in the various openstack .conf files.
This allows either server to shutdown and we can still access the web interface, create vms and volumes, etc. because the virtual hostname is used in all the configurations.
However, for cinder volumes, it puts the hostname of the server in os-vol-host-attr:host rather than my virtual name. This causes issues if the controller that was used to create the volume is down, we can't easily manage the volume without modifying that field in the cinder database.
If the virtual name could be used, either server could manage the volume with the backend, with no manual changes to the db.
The only server related setting in my cinder.conf is my_ip, and that is the ip of the actual server, not the virtual ip
Is active/active cluster not supported with cinder?
participants (2)
-
Eugen Block
-
Jim Kilborn