From: Weiwei Jia <[email protected]> After discuss with my mentor Lance, Michele and other developers like Guido and such, GlusterFS Ganeti Support doc is updated as follows.
Signed-off-by: Weiwei Jia <[email protected]> --- doc/design-glusterfs-ganeti-support.rst | 28 ++++++++++++++++++++++------ 1 file changed, 22 insertions(+), 6 deletions(-) diff --git a/doc/design-glusterfs-ganeti-support.rst b/doc/design-glusterfs-ganeti-support.rst index 53bfb7a..c5b1bbc 100644 --- a/doc/design-glusterfs-ganeti-support.rst +++ b/doc/design-glusterfs-ganeti-support.rst @@ -73,13 +73,29 @@ Now, there are two specific enhancements: uses libgfapi and hence there is no FUSE overhead any longer when QEMU/KVM works with VM images on Gluster volumes. -There are two possible ways to implement "GlusterFS Ganeti Support" inside -Ganeti. One is based on libgfapi, which call APIs by libgfapi to realize -GlusterFS interfaces in bdev.py. The other way is based on QEMU/KVM. Since +Proposed implementation +----------------------- + QEMU/KVM has supported for GlusterFS and Ganeti could support for GlusterFS -by QEMU/KVM. However, the latter way can just let VMs of QEMU/KVM use GlusterFS -backend storage but other VMs like XEN and such. So the first way is more -suitable for us. +by QEMU/KVM. However, this way could just let VMs of QEMU/KVM use GlusterFS +backend storage but other VMs like XEN and such. Currently, there are two +possible parts to implement "GlusterFS Ganeti Support" inside Ganeti, which +could not only support for QEMU/KVM VMs but also for XEN VMs and such. One +part is GlusterFS for XEN VM, which is the same as sharedfile disk template. +The other part is GlusterFS for QEMU/KVM VM, which is by GlusterFS driver for +QEMU/KVM way (QEMU/KVM + GlusterFS way). + + ``gnt-instance add -t gluster xxx`` -> GlusterFS sharedfile way for XEN VMs + -> QEMU/KVM + GlusterFS way for QEMU/KVM VMs + +After ``gnt-instance add -t gluster xxx`` command is executed, the added instance +should be checked. If the instance is a XEN VM, it would run the GlusterFS +sharedfile way. However, if the instance is a QEMU/KVM VM, it would run the +QEMU/KVM + GlsuterFS way. For the first part (GlusterFS for XEN VMs), sharedfile +disk template would be a good reference. For the second part (GlusterFS for QEMU/KVM +VMs), RBD disk template would be a good reference. The first part would be finished +at first and then the second part would be completed, which is based on the first +part. .. vim: set textwidth=72 : .. Local Variables: -- 1.7.10.4
