On 2012-09-28 16:24, James Harper wrote:
I have two nodes running identical hardware which run Xen VM's, and want to add
a third node to the cluster which can access the same clvm and iscsi resources,
but it will not be identical hardware. The non-identical hardware means that to
move a VM to this third node it it must be stopped then started, a migration
will not work.
This situation may not really come up as in most cases I'll use location
resources to restrict VM's to only the first two nodes (third node will mostly
be for a different purpose), but just in case I want to do that for one or two
VMs, is it possible to come up with some sort of rule like:
A->B = migration allowed
B->A = migration allowed
A->C = no migration allowed
B->C = no migration allowed
create an asymmetrical cluster.
add a node property, e.g.
> node xxx attributes service="web"
create corresponding location rules, e.g.
location loc-web-fs-www web-fs-www \
rule $id="loc-web-webfs-www-rule" 100: service eq web
Cheers,
Raoul
--
____________________________________________________________________
DI (FH) Raoul Bhatia M.Sc. email. r.bha...@ipax.at
Technischer Leiter
IPAX - Aloy Bhatia Hava OG web. http://www.ipax.at
Barawitzkagasse 10/2/2/11 email. off...@ipax.at
1190 Wien tel. +43 1 3670030
FN 277995t HG Wien fax. +43 1 3670030 15
____________________________________________________________________
_______________________________________________
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org
