How to install GlusterFS file system in a OpenVZ VPS

[raskar]

Hi everybody,
I'm currently use Proxmox and OpenVZ to create a highly available web site with a hight work load.
I would like to use GlusterFS file system instead of the usual NFS sytem.

I see that I must install FUSE before. I'm using a CentOS 5 64 bits VPS grab from the community template of openvz website.

When I try to install fuse with rpm package, i have an error(the system search for the kernel header 2.6.18but i'm using 2.6.24.7-proxmox kernel) So I prefer to install from source, I download the FUSE tarball file provide by glusterFS (fuse-2.7.3glfs10.tar.gz).

When I run the configure script I have the following error:

checking kernel source directory... Not found
configure: error:
    *** Please specify the location of the kernel source with
    *** the '--with-kernel=SRCDIR' option
configure: error: ./configure failed for kernel

If someone have already try and/or succeed to install this file system or have an idea thanks

 

[tom]

Hi everybody,
I'm currently use Proxmox and OpenVZ to create a highly available web site with a hight work load.
I would like to use GlusterFS file system instead of the usual NFS sytem.

I see that I must install FUSE before. I'm using a CentOS 5 64 bits VPS grab from the community template of openvz website.

When I try to install fuse with rpm package, i have an error(the system search for the kernel header 2.6.18but i'm using 2.6.24.7-proxmox kernel) So I prefer to install from source, I download the FUSE tarball file provide by glusterFS (fuse-2.7.3glfs10.tar.gz).

When I run the configure script I have the following error:

checking kernel source directory... Not found
configure: error:
    *** Please specify the location of the kernel source with
    *** the '--with-kernel=SRCDIR' option
configure: error: ./configure failed for kernel

If someone have already try and/or succeed to install this file system or have an idea thanks

Proxmox VE uses ext3 on the host (the recommended by OpenVZ project).

OpenVZ is a container-based virtualization for Linux so you have no Kernel inside the container (maybe think of using KVM, install the OS from CentOS 5.2 64-bit DVD).

 

[andrewg]

It needs the kernel source code to compile against, which is normally located in /usr/src/ directory. I just looked and did not see the kernel sources in there, it is common for distributions not to include kernel sources though. If proxmox uses an unmodified kernel you can download the kernel sources via apt-get, but I would check first with the proxmox ve guys to make sure it is an unmodified kernel...
you can use uname -r to see what kernel is currently running.

 

[dietmar]

Fuse is already compiled for our kernel - just do

modprobe fuse

on the host to load the module.

 

[raskar]

I try to run "modprobe fuse" but I have the following error:

root@t2:~# modprobe fuse
FATAL: Could not load /lib/modules/2.6.24.7-proxmox/modules.dep: No such file or directory

If I install the kernel sources via apt, I will get the kernel header for the current distribution (etch) 2.6.18.
The only kernel available for proxmox is the 2.6.18 or 2.6.24(mine).
So what can I do ? Do I must use KVM ? No chance to run GlusterFS in a VPS ?

 

[dietmar]

Kernel "2.6.24.7-proxmox" is not the proxmox ve standard kernel - so what kernel do you use?

 

[raskar]

My dedicated server is hosted by OVH, a french hosting provider.
They offer the possibility to install Proxmox instead of a traditionnal Debian or other usual Linux distribution.

 

[dietmar]

Please ask OVH support - this forum is for Proxmox VE only. OVH provides a custom kernel, so you need to ask them.

- Dietmar

 

[raskar]

Ok, I'm now running on a normal kernel.
I think the problem is from openvz because I have other server with a normal install of openvz (without proxmox) and I have the same problems.

In fact I succeed to use fuse with the flag "no kernel module' but the server deamon doesn't work.
I tried the same install on a physical host and it worked very well.

I post on the openvz forum, but if anyone can give me some help

 

[dietmar]

You can try to mount on the host, then use bind mounts to use the filesystem inside containers.