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-su... <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`? Regards, Chris
On 18 Mar 2019, at 19:00, Gorka Eguileor <geguileo@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.