Hey Adrian,
I'm jumping in now because you haven't had any nibbles yet, not because I know
for sure I'm right. I only have something to say about the 3rd part of your
email:
> 3) Mount dns resolution
> If you check Jason Brooks howto you will see that it uses a hostname
> for refering to nfs mount. If you want to perform HA you need your
> storage to be mounted and if the server1 host is down it doesn't
> help that the nfs mount point associated to the storage is
> server1:/vms/ and not server2:/vms/. Checking Middleswarth howto I
> think that he does the same thing.
>
> Let's explain a bit more so that understand. My example setup is the
> one where you have two host machines where you run a set of virtual
> machines on one and the other one doesn't have any virtual machine
> running. Where is the virtual machines storage located? It's located
> at the glusterfs volume.
>
> So the first one of the machines mounts the glusterfs volume as nfs
> (It's an example).
> If it uses its own hostname for the nfs mount then if itself goes
> down the second host isn't going to mount it when it's restarted in
> the HA mode.
>
> So the first one of the machines mounts the glusterfs volume as nfs
> (It's an example).
> If it uses the second host hostname for the nfs mount then if the
> second host goes down the virtual machine cannot access its virtual
> disks.
From what I can tell, you are asking about using storage local to hypervisors,
combined into a gluster volume, and used as a POSIX data center.
I don't think anyone would disagree about that being a bad idea. In the RHEV
documentation, we try and make it clear that one of the weaknesses of using
storage that is local to they hypervisors is that when something happens, you
lose two pieces of infrastructure in one shot, rather than one. I think that
for the availability you are talking about, you'll want at least three nodes.
I've cc'd John Walker, the Gluster Community Guy (whom I met recently at LCA,
g'day John!), he can probably say something specific.
Tim Hildred, RHCE
Content Author II - Engineering Content Services, Red Hat, Inc.
Brisbane, Australia
Email: thild...@redhat.com
Internal: 8588287
Mobile: +61 4 666 25242
IRC: thildred
- Original Message -
> From: "Adrian Gibanel"
> To: "users"
> Sent: Friday, January 25, 2013 9:35:42 PM
> Subject: [Users] Glusterfs HA doubts
>
> In oVirt 3.1 GlusterFS support was added. It was an easy way to
> replicate your virtual machine storage without too much hassle.
> There are two main howtos:
> *
> http://www.middleswarth.net/content/installing-ovirt-31-and-glusterfs-using-either-nfs-or-posix-native-file-system-engine
> (Robert Middleswarth)
> * http://blog.jebpages.com/archives/ovirt-3-1-glusterized/ (Jason
> Brooks).
>
> 1) What about performance?
> I've done some tests with rsync backups (even using the suggested
> --inplace rsync switch) that implies small files. These backups were
> done into local mounted glusterfs volumes. Backups instead of
> lasting about 2 hours they lasted like 15 hours long.
>
> Is there maybe something that only happens with small files and with
> big files performance is ok?
>
> 2) How to know the current status?
> In DRBD you know it checking a proc file if I remember it well. I
> remember too that GlusterFS doesn't have an equivalent thing and
> there's no evident way to know if all the files are synced.
>
> If you have tried it how do you know if both sets of virtual disks
> images are synced?
>
> 3) Mount dns resolution
> If you check Jason Brooks howto you will see that it uses a hostname
> for refering to nfs mount. If you want to perform HA you need your
> storage to be mounted and if the server1 host is down it doesn't
> help that the nfs mount point associated to the storage is
> server1:/vms/ and not server2:/vms/. Checking Middleswarth howto I
> think that he does the same thing.
>
> Let's explain a bit more so that understand. My example setup is the
> one where you have two host machines where you run a set of virtual
> machines on one and the other one doesn't have any virtual machine
> running. Where is the virtual machines storage located? It's located
> at the glusterfs volume.
>
> So the first one of the machines mounts the glusterfs volume as nfs
> (It's an example).
> If it uses its own hostname for the nfs mount then if itself goes
> down the second host isn't going to mount it when it's restarted in
> the HA mode.
>
> So the first one of the machines mounts the glusterfs volume as nfs
> (It's an example).
> If it uses the second host hostname
