[cinder] setting `rbd_exclusive_cinder_pool = True` with multiple cinder-volume writing to the same pool

Krzysztof Klimonda kklimonda at syntaxhighlighted.com
Mon Mar 18 18:10:08 UTC 2019

Thanks guys,

@Gorka, Is the recommendation one ceph pool per cinder-volume or rather one cinder-volume (in active/passive HA) per ceph cluster? It seems Active/Active HA hasn’t been finished (looking at https://blueprints.launchpad.net/cinder/+spec/cinder-volume-active-active-support <https://blueprints.launchpad.net/cinder/+spec/cinder-volume-active-active-support>) so one cinder-volume would probably become a bottle neck at some point? Or is it going to be mostly idle anyway now that I’ve toggled `rbd_exclusive_cinder_pool = True`?


> On 18 Mar 2019, at 19:00, Gorka Eguileor <geguileo at redhat.com> wrote:
> On 13/03, Krzysztof Klimonda wrote:
>> Hi,
>> Just doing a quick sanity check - I can set `rbd_exclusive_cinder_pool = True` (in pike, where the change landed first) even if more than one cinder-volume is writing to the same Ceph pool, right? Assuming nothing writes to the pool outside of cinder, we should be good as far as I understand the code.
>> -Chris
> Hi Chris,
> It's best not to share your pools, but your assessment is correct
> regarding the rbd_exclusive_cinder_pool configuration option.  The code
> ruled by that option will work as expected even when sharing the pool
> between different cinder-volume services.
> Cheers,
> Gorka.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20190318/14aecb89/attachment.html>

More information about the openstack-discuss mailing list