Patrick can correct me if I'm wrong, but you don't need clvmd at all.
You could 'tag' your volume groups with the machine name. No-one would
be able to manipulate those volume groups except the machine whose tag
matches. If it is a virtual machine, it doesn't matter where it goes,
it will still be able to manipulate the volume group with the
appropriate tag.
This adds a little complexity to the lvm.conf file - so it's really a
trade-off in terms of where you put your effort (better understanding
of lesser-used features of LVM vs. coming up to speed on cluster
infrastructure).
brassow
On Nov 17, 2006, at 1:54 PM, Nate Carlson wrote:
Hey all,
I'm building a new system with shared FC storage primarily to allow
Xen virtual machines to be migrated between host systems. I'd like to
be able to use LVM or some similar system that allows me to name my
own volumes, but don't need shared storage, rgmanager, etc. What are
the minimum requirements to just get clvm working? I'm assuming I
don't need fence devices and such for this, as those are primarily
used to ensure that a system is writing to a filesystem when it's not
supposed to? Also, are there any alternatives to clvm that may be
better suited for this case?
Thanks!
-----------------------------------------------------------------------
-
| nate carlson | natecars@xxxxxxxxxxxxxxx | http://www.natecarlson.com
|
| depriving some poor village of its idiot since 1981
|
-----------------------------------------------------------------------
-
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
