----- Original Message ----- > Daniel Dehennin <daniel.dehen...@baby-gnu.org> writes: > > > Hello, > > 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?
actually, this is possible now. I am unaware of any configuration tools (pcs or crmsh) that support this feature yet though. You might have to edit the cib xml manually. There's a new 'resource-discovery' option you can set on a location constraint that help prevent resources from ever being started or monitored on a node. Example: never start or monitor the resource FAKE1 on 18node2. <rsc_location id="location-FAKE1-18node2" node="18node2" resource-discovery="never" rsc="FAKE1" score="-INFINITY"/> There are more examples in this regression test. https://github.com/ClusterLabs/pacemaker/blob/master/pengine/test10/resource-discovery.xml#L99 -- Vossel > This cause troubles on my setup, as resources fails, my nodes are all > fenced. > > Any hints? > > Regards. > -- > Daniel Dehennin > Récupérer ma clef GPG: gpg --recv-keys 0xCC1E9E5B7A6FE2DF > Fingerprint: 3E69 014E 5C23 50E8 9ED6 2AAD CC1E 9E5B 7A6F E2DF > > _______________________________________________ > 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 > _______________________________________________ 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
