Hi all,
After adding the LINSTOR driver to OpenStack Cinder, three separate cinder-volume services were created (one per controller node).
When I create a volume using a LINSTOR volume type, the volume is assigned to one specific cinder-volume host.
The problem is that when the related cinder-volume service fails, I am no longer able to manage the volume lifecycle operations such as: attach ,detach, resize , . . . .
After extensive testing and research, I tried the following:
1. Setting the backend_host option in cinder.conf for the LINSTOR backend
2. Testing the cluster configuration option in cinder.conf
However, neither approach worked, and the volumes remain tied to a specific cinder-volume host.
My question is:
Does the LINSTOR Cinder driver support solution such as Active-Active operation at the Cinder service layer?
If not, what is the recommended High Availability design for cinder-volume when using LINSTOR as a backend?
Thank you in advance for your guidance
