Open Stack

On 17 June 2015 at 00:21, Matt Riedemann <mriedem at linux.vnet.ibm.com> wrote:

> The NFS, GlusterFS, SMBFS, and Quobyte libvirt volume drivers are all very
> similar.
>
> I want to extract a common base class that abstracts some of the common
> code and then let the sub-classes provide overrides where necessary.
>
> As part of this, I'm wondering if we could just have a single
> 'mount_point_base' config option rather than one per backend like we have
> today:
>
> nfs_mount_point_base
> glusterfs_mount_point_base
> smbfs_mount_point_base
> quobyte_mount_point_base
>
> With libvirt you can only have one of these drivers configured per compute
> host right?  So it seems to make sense that we could have one option used
> for all 4 different driver implementations and reduce some of the config
> option noise.


I can't claim to have tried it, but from a cinder PoV there is nothing
stopping you having both e.g. an NFS and a gluster backend at the same
time, and I'd expect nova to work with it. If it doesn't, I'd consider it a
bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150617/e23d4278/attachment.html>