Does that mean that we will add to driver functionality doc table miltipathing or A/A explicitly in the future? From: Jay Bryant <jsbryant@electronicjungle.net> Sent: Thursday, March 28, 2019 11:16 AM To: openstack-discuss@lists.openstack.org Subject: Re: [cinder] Cinder Volume Active/Active Support [EXTERNAL EMAIL] This is something I will add to PTG discussion. We need to come up with what certifying really means and push people to work on this. Jay On Thu, Mar 28, 2019, 10:45 AM Sean McGinnis <sean.mcginnis@gmx.com<mailto:sean.mcginnis@gmx.com>> wrote: On Thu, Mar 28, 2019 at 08:56:25AM -0500, Ben Nemec wrote:
Fixed the cinder tag so this should show up for people who filter on it.
On 3/28/19 3:18 AM, vkalaitzis wrote:
I would like to ask if cinder-volume supports active/active setups. I found that there was a blueprint for adding support (https://blueprints.launchpad.net/cinder/+spec/cinder-volume-active-active-su...), but as far as I am concerned, no official documentation of such feature exists so far.
My understanding is that Cinder does support active-active configuration now, but someone from the Cinder team will have to provide details.
The support is merged in Cinder for active/active, but the hold up now has been getting Cinder driver maintainers to certify their drivers and storage devices will work correctly when running in that configuration. I seem to recall some work being done with the Ceph/RBD driver, but I don't believe anything has merged for any drivers to enable that.