Hello Andrew,

Sorry I do not understand your comment after "Please don't do this.", What I need to do ?

For my test system I have a cluster with 2 nodes and 4 resources group (named, dhcpd, named2, samba) with each group an ip resource, drbd resource, filesystem resource, start application resource (not on this test server). For each group I have a constraint to assignate named/dhcpd to noeud1 and named2/samba to noeud2

<rsc_location id="location-named-noeud1.apec.fr-50" node="noeud1.apec.fr" rsc="named" score="50"/> <rsc_location id="location-dhcpd-noeud1.apec.fr-50" node="noeud1.apec.fr" rsc="dhcpd" score="50"/> <rsc_location id="location-named2-noeud1.apec.fr-50" node="noeud1.apec.fr" rsc="named2" score="50"/> <rsc_location id="location-samba-noeud1.apec.fr-50" node="noeud1.apec.fr" rsc="samba" score="50"/>

I created a ping resource to "monitor" the network and when the network failed on one node I want the resources to migrate to other node.

Best Regards.

Francis

On 08/30/2013 05:26 AM, Andrew Beekhof wrote:

On 29/08/2013, at 5:36 PM, Francis SOUYRI <francis.sou...@apec.fr> wrote:

Hello,

I have a corosync/pacemaker with 2 nodes and 2 nets by nodes, 192.168.1.0/24 
for cluster access, 10.1.1.0/24 for drbd in bond, both used by corosync.
I try to used ocf:pacemaker:ping to monitor the 192.168.1.0/24 I have the 
configuration below, but when I remove the cable of the noeud1 the named group 
resource do not migrate to noeud2.

When I used these command "crm_attribute -G -t status -N  -n pingd" I have this.

Invalid command.  -N requires an argument.


Could not map uname=-n to a UUID: The object/attribute does not exist
scope=status   value=(null)
Error performing operation: cib object missing

##### CONFIG
...
      <clone id="ping-gateway-clone">
        <meta_attributes id="ping-gateway-clone-meta">
          <nvpair id="ping-gateway-interleave" name="interleave" value="true"/>
        </meta_attributes>
        <primitive class="ocf" id="ping-gateway" provider="pacemaker" 
type="ping">
          <instance_attributes id="ping-gateway-instance_attributes">
            <nvpair id="ping-gateway-instance_attributes-host_list" name="host_list" 
value="192.168.1.1"/>
            <nvpair id="ping-gateway-instance_attributes-multiplier" name="multiplier" 
value="100"/>
          </instance_attributes>
        </primitive>
      </clone>
    </resources>
    <constraints>
      <rsc_location id="location-named-noeud1.apec.fr-50" node="noeud1.apec.fr" rsc="named" 
score="50"/>
      <rsc_location id="location-dhcpd-noeud1.apec.fr-50" node="noeud1.apec.fr" rsc="dhcpd" 
score="50"/>
      <rsc_location id="location-named2-noeud1.apec.fr-50" node="noeud1.apec.fr" 
rsc="named2" score="50"/>
      <rsc_location id="location-samba-noeud1.apec.fr-50" node="noeud1.apec.fr" rsc="samba" 
score="50"/>
      <rsc_location id="pingnamed" rsc="named">
        <rule id="pingnamed-rule" score-attribute="pingd">
          <expression attribute="pingd" id="pingnamed-expression" 
operation="defined"/>
        </rule>
      </rsc_location>
    </constraints>
    <rsc_defaults>
      <meta_attributes id="rsc_defaults-options">
        <nvpair id="rsc_defaults-options-resource-stickiness" name="resource-stickiness" 
value="100"/>
      </meta_attributes>
    </rsc_defaults>
....

Please don't do this.

The contents of "...." might not seem relevant to you, but I assure you they 
are.  Particularly in this case.


##### END CONFIG

Best regards.

Francis

_______________________________________________
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

Reply via email to