[Pacemaker] Putting a node to standby stops resources on the other node

[Michael Schwartzkopff]

Am Mittwoch, 20. Februar 2013, 17:54:49 schrieb Thomas Lorenzen:
> Hi'
> 
> My setup is a simple two cluster solution intended for a "master" "backup"
> framework, where I would like to assign floating ip addresses on two
> network interfaces for both the master and the backup.
> 
> The most cricial part of the config is as follows.
> 
> group backup backup_ip_intern backup_ip_extern
> 
> group master master_ip_intern master_ip_extern
> colocation backupgroup_cannot_live_together_with_mastergroup -inf: master

better:

colocation backup_not_with_master -inf: backup master

> backup order backupgroup_start_after_mastergroup inf: master backup
> 
> 
> So, two groups are defined, each containing two primitives, which
> essentially just assigns floating ip addresses to two different network
> interfaces. The colocation rule is intended to make sure, that the groups
> does not end up on the same node. The order rule is intended to make sure,
> that the master group and not the backup group gets started, if only a
> single node is available.


Depeding on the verison of pacemaker you could also do this with utilizations 
and priorities. So you would not need the order and colocation constraint at 
all.

Greetings.

-- 
Mit freundlichen Grüßen,

Michael Schwartzkopff

-- 
[*] sys4 AG

http://sys4.de, +49 (89) 30 90 46 64
Franziskanerstraße 15, 81669 München

Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer
Aufsichtsratsvorsitzender: Joerg Heidrich
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20130220/27a55bc0/attachment-0003.html>