Hi,
Am Dienstag, 31. Januar 2006 14:18 schrieb Pasi Kärkkäinen:
> On Tue, Jan 31, 2006 at 01:45:15PM +0100, Markus Hochholdinger wrote:
> > Am Sonntag, 29. Januar 2006 13:06 schrieb Pasi Kärkkäinen:
> > But if anyone knows for real, let us know?
> CLVM makes it possible to have /dev/vg-shared/domU1-lv volume available in
> both xen hosts.. so you can migrate domU's easily between xen hosts.
so clvm is a replacement for gnbd but not for network block device?
i.g.:
(storage server, lvm2, lv -> gnbd) -> (Xen host1, gnbd -> hda1 for domU)
 \> (Xen host2, gnbd -> hda1 for domU)
(storage server, iscsi) -> (Xen host, iscsi -> clvm -> hda1 for domU)
 \> (Xen host, iscsi -> clvm -> hda1 for domU)
So clvm takes the lvm part from the storage server to the Xen hosts? Are i am 
right?
> Basicly you set up only one block device (over iSCSI or gnbd) for each
> xen host (dom0), and then use CLVM with that device.. really easy & simple
> to share all the logical volumes between xen hosts.
And how complicated ist the management of clvm?
> If you don't use CLVM, you need to set up separate iSCSI/gnbd device in xen
> host/dom0 for yeach domU.. much harder to manage & setup.
Hm, what i see from gnbd it's very easy! You don't need to have a config on 
the gnbd client. Only on the gnbd server. But also have all the gnbd volumes 
available.
With clvm you have to run some sort of cluster management on each client which 
distribute the config for the clvm (as i read in the docs). Sounds to me 
complicated. Or i am wrong?
-- 
greetings
eMHa

Attachment: pgpY5bDNWcVhx.pgp
Description: PGP signature

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users