[Pacemaker] Avoid monitoring of resources on nodes

[Daniel Dehennin]

Hello,

I have a 4 nodes cluster and some resources are only installed on 2 of
them.

I set cluster asymmetry and infinity location:

    primitive Mysqld upstart:mysql \
    	op monitor interval="60"
    primitive OpenNebula-Sunstone-Sysv lsb:opennebula-sunstone \
    	op monitor interval="60"
    primitive OpenNebula-Sysv lsb:opennebula \
    	op monitor interval="60"
    group OpenNebula Mysqld OpenNebula-Sysv OpenNebula-Sunstone-Sysv \
    	meta target-role="Started"
    location OpenNebula-runs-on-Frontend OpenNebula inf: one-frontend
    property $id="cib-bootstrap-options" \
    	dc-version="1.1.10-42f2063" \
    	cluster-infrastructure="corosync" \
    	symmetric-cluster="false" \
    	stonith-enabled="true" \
    	stonith-timeout="30" \
    	last-lrm-refresh="1416817941" \
    	no-quorum-policy="stop" \
    	stop-all-resources="off"

But I have a lot of failing monitoring on other nodes of these resources
because they are not installed on them.

Is there a way to completely exclude the resources from nodes, even the
monitoring?

Regards.

Ubuntu Trusty Tahr (amd64):
- corosync 2.3.3-1ubuntu1
- pacemaker 1.1.10+git20130802-1ubuntu2.1

-- 
Daniel Dehennin
Récupérer ma clef GPG: gpg --recv-keys 0xCC1E9E5B7A6FE2DF
Fingerprint: 3E69 014E 5C23 50E8 9ED6  2AAD CC1E 9E5B 7A6F E2DF
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 342 bytes
Desc: not available
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20141125/0975e3e1/attachment-0003.sig>