[Pacemaker] Clone config question

[Andrew Beekhof]

On Tue, May 19, 2009 at 10:24 AM, Mark Schenk <M.M.A.Schenk at tudelft.nl> wrote:
> Hi,
>
>   I am trying to run cloned resources on part of my cluster, however I must
> be mistaken on how to use the location-directive. This is the relevant part
> of my config:
>
> node $id="8ce10d28-174c-4fc3-bac4-b2bf21ef6a38" apa1
> node $id="09c41339-21db-4250-83b9-bac11a6c25de" apa2
> node $id="ea3da999-829d-4042-a5d5-9ee0ad27f989" mysql1
> node $id="23f84b10-ad8c-43a9-ab23-344d06254948" mysql2
> node $id="47c29bf2-ac4a-4873-9b91-f05b8e41af2d" nfs1
> node $id="e588fc86-92d8-4658-a394-3e031171bcd0" nfs2
> primitive apachefs ocf:heartbeat:Filesystem \
>         params device="192.168.202.47:/data/export" directory="/data"
> fstype="nfs"
> primitive apacheserver ocf:heartbeat:Dummy
> group apacheservice apachefs apacheserver
> clone apache apacheservice \
>         meta clone-max="2"
> location apaapa1 apache 100: apa1
> location apaapa2 apache 100: apa2
> property $id="cib-bootstrap-options" \
>         dc-version="1.0.3-b133b3f19797c00f9189f4b66b513963f9d25db9" \
>         symmetric-cluster="false" \
>         last-lrm-refresh="1242719884"
>
>
> What I thought this would do was: start (cloned) resources apachefs and
> apacheserver only on nodes apa1 and apa2 (since symmetric-cluster=false and
> having the two location directives). What I can see happening is that the
> apachefs resource is tried on other nodes as well, most importantly also on
> nfs1 and nfs2, which causes these to crash :-(.  Could someone point out how
> I can get this working the way I want?

It shouldn't be starting apache anywhere except apa1 & 2, but we do
check _every_ node to see if its running (so that we can satisfy the
constraints by stopping apache if we find it running somewhere it
shouldn't be).