Re: [libvirt] rbd storage pool support for libvirt

On Wed, 3 Nov 2010, Daniel P. Berrange wrote: > > Something along the lines of > > > > <pool type="rbd"> > > <name>virtimages</name> > > <source mode="kernel"> > > <host monitor="ceph-mon1.domain.com:6789"/> > > <host monitor="ceph-mon2.domain.com:6789"/> > > <host monitor="ceph-mon3.domain.com:6789"/> > > <pool name="rbd"/> > > </source> > > </pool> > > What do the 3 hostnames represent in this context ? They're the host(s) that RBD needs to be fed to talk to the storage cluster. Ideally there's more than one for redundancy. Does the above syntax look reasonable, or is there something you would propose instead? From the RBD side of things, the key parameters are - pool name - monitor address(es) - user and secret key to authenticate with If the 'rbd' command line tool is used for this, everything but the pool can come out of the default /etc/ceph/ceph.conf config file, or we could have a way to specify a config path in the XML.

> > In any case, before someone goes off and implements something, does this > > look like the right general approach to adding rbd support to libvirt? > > I think this looks reasonable. I'd be inclined to get the storage pool > stuff working with the kernel RBD driver & UDEV rules for stable path > names, since that avoids needing to make any changes to guest XML > format. Support for QEMU with the native librados CEPH driver could > be added as a second patch. Okay, that sounds reasonable. Supporting the QEMU librados driver is definitely something we want to target, though, and seems to be route that more users are interested in. Is defining the XML syntax for a guest VM something we can discuss now as well? (BTW this is biting NBD users too. Presumably the guest VM XML should look similar?