I have actually a question on unrelated topic, but related to the active/standby of cinder-volume.

Is there any way to explicitly tell to the backend that it should be active? As well as would it restore active mode if at some point become unreachable and then restore? Recently I tried to look through docs and config options, but was not able to find an answer.

вс, 7 авг. 2022 г., 17:09 Takashi Kajinami <tkajinam@redhat.com>:

- Usually you need to deploy cinder-volume as an act/sby process. Your cinder-volume would run
on only one of the controller nodes managed by a cluster technology like pacemaker.
You can split cinder-volume per backend but in such case you'd run each c-vol in act/sby mode.