[Cinder][NFS][Openstack-Ansible] Cinder-Volume Mess - Containers and Metal by Accident

Dmitriy Rabotyagov noonedeadpunk at gmail.com
Sun Aug 7 15:47:20 UTC 2022


Another question - are features that tooz support with etcd enough for
cinder active/active to work?

IIRC, for NFS openstack-ansible deploy in active/standby mode by default.
Only ceph goes "active/active" but we don't define coordination url for
that - only define cluster_name...
Though, we do provide a role/way to get etcd, so no blocker to get
coordination_url for cinder if etcd covers all cinder needs

вс, 7 авг. 2022 г., 17:36 Dmitriy Rabotyagov <noonedeadpunk at gmail.com>:

> 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 at 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.
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.openstack.org/pipermail/openstack-discuss/attachments/20220807/7c3e5a6d/attachment.htm>


More information about the openstack-discuss mailing list