[Ovirt-devel] GlusterFS patches for ovirt-server, ovirt-node, ovirt-node-image

Harshavardhana harsha at gluster.com
Thu Jul 9 11:30:50 UTC 2009


Patches coming through a Brief overview of the same below. Patches are
rebased against
current "master" branch for each projects.

--------------------------------------------------------------------------
Packages with versions.

GlusterFS - 2.0.2 (in house repository)
Fuse - 2.8.0 (in house repository)
libvirt - 0.6.4 (in house repository)
ovirt-server - 0.99 (in house repository)
ovirt-node-image - 1.0.1 (in house repository)

all present at http://ftp.gluster.com/pub/gluster/glusterfs/ovirt

With a brief Installation document at

http://ftp.gluster.com/pub/gluster/glusterfs/ovirt/INSTALL.txt

A wiki document at

http://www.gluster.org/docs/index.php/GlusterFS_oVirt_Setup_Guide

Where we fit in?

1. Libvirt
No modifications for libvirt we use the same framework given by libvirt, but
modify out own mount.glusterfs to handle the ways of NFS parameters.

mount -t glusterfs <glusterfs-server>:<volume-name> <MOUNTPATH>

2. Ovirt

Technical Details:

"GlusterfsStoragePool" a new class added in support of Glusterfs for
task-omatic daemon. Now with this Ovirt server can generate same
task events like start_vm, migrate_vm, refresh_storage_pool etc., with
glusterfs too.

Glusterfs awareness were added into files inside app/views/, app/controller/,
app/models/ which contain code for frontend UI.

New rpms for glusterfs-common, glusterfs-client version 2.0.2, libvirt 0.6.4
were added into the automated build system for bootable ovirt-node-image using
local "yum" repositories.

I have few queries too regarding Selinux which i had to disable for the case of
using to get ovirt-node-image working with kvm. I would like to know how to add
Selinux support in meantime for the extra apps which i have added?

VM image format used is "qcow2" for the reason that "raw" format with a request
of volume creations above 4GB-10GB taskomatic daemon used to timeout waiting
for libvirt to return back as unconditionally large file writes used
to take long
time. This case is reproducible using NFS also, increasing timeout
doesn't help.

-----------------------------------------------------------------------------------
Thanks Comments Welcome!

--
Harshavardhana
Z Research Inc http://www.zresearch.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/ovirt-devel/attachments/20090709/c490b97b/attachment.htm>


More information about the ovirt-devel mailing list