[Gluster-devel] Fwd: [ovirt-devel] Using libgfapi on Gluster Storage Domains
bengland at redhat.com
Mon Oct 27 13:00:49 UTC 2014
The year-old BZ 1016886 describes three problems that any libgfapi application would have, not just KVM.
As for the rpc-auth-allow-insecure=on setting, has any progress been made in this area? I think this setting should be unnecessary, and it's really important in general that Gluster have some way of optionally authenticating clients other than by client port number. Do SSL sockets solve this problem of authenticating in the control plane?
Two of these problems can be fixed by just altering the virt "group" -- the settings that you get with the gluster command
- gluster volume set your-volume group virt
And then just document that when you configure a volume for KVM virtualization, use the above command, right? This is why we have volume "group" feature, right?
In /var/lib/glusterd/groups/virt file, it has this:
[root at g60ds-1 groups]# more virt
Just add 1 lines to it:
And change stat-prefetch to "on", and you'll have eliminated 2 of the 3 things that every KVM user has to do to Gluster. eager-lock is the default now so that can be removed.
----- Original Message -----
> From: "Vijay Bellur" <vbellur at redhat.com>
> To: "Gluster Devel" <gluster-devel at gluster.org>
> Sent: Monday, October 27, 2014 5:38:24 AM
> Subject: [Gluster-devel] Fwd: [ovirt-devel] Using libgfapi on Gluster Storage Domains
> FYI - if you are interested in trying out libgfapi support with oVirt.
> ---------- Forwarded message ----------
> From: Federico Simoncelli < fsimonce at redhat.com >
> Date: Fri, Oct 24, 2014 at 12:06 AM
> Subject: [ovirt-devel] Using libgfapi on Gluster Storage Domains
> To: oVirt Development < devel at ovirt.org >
> Hi everyone, if you want to try and use the libgfapi support included
> in qemu when accessing volumes on gluster storage domains you can try
> to apply this patch:
> As far as I know Jason Brooks already tried it and he reported a
> positive feedback.
> What has been tested so far is:
> - qemu uses libgfapi to access the disks on gluster storage domains
> - hotplug of disks on gluster storage domains works as expected (libgfapi)
> - hotunplug works as expected (no failure when removing a disk that is
> using libgfapi)
> - live snpashots work as expected
> - disks of vms started before this patch are not affected (they won't
> use libgfapi since there's no way to do an hot swap)
> One major flow that is yet untested is live storage migration.
> Remember that you may need to do some special configuration on your
> gluster volumes (most notably the allow-insecure ports option) as
> described here:
> Please try and test the patch if you're interested and report your
> Devel mailing list
> Devel at ovirt.org
> Gluster-devel mailing list
> Gluster-devel at gluster.org
More information about the Gluster-devel