[Pacemaker] [Question:crmsh] About a setting method of seuquential=true in crmsh.

renayama19661014 at ybb.ne.jp renayama19661014 at ybb.ne.jp
Wed Feb 5 01:55:42 EST 2014


Hi All,

We tried to set sequential attribute of resource_set of colocation in true in crmsh.

We tried the next method, but true was not able to set it well.

---------------------
[pengine]# crm --version
2.0 (Build 7cd5688c164d2949009accc7f172ce559cadbc4b)

- Pattern 1 - 
colocation rsc_colocation-grpPg-clnPing INFINITY: msPostgresql:Master vip-master vip-rep sequential=true 

      <rsc_colocation id="rsc_colocation-grpPg-clnPing" score="INFINITY">
        <resource_set id="rsc_colocation-grpPg-clnPing-0" role="Master">
          <resource_ref id="msPostgresql"/>
        </resource_set>
        <resource_set id="rsc_colocation-grpPg-clnPing-1">
          <resource_ref id="vip-master"/>
          <resource_ref id="vip-rep"/>
        </resource_set>
      </rsc_colocation>

- Pattern 2 - 
colocation rsc_colocation-grpPg-clnPing INFINITY: msPostgresql:Master vip-master vip-rep sequential=false

      <rsc_colocation id="rsc_colocation-grpPg-clnPing" score="INFINITY">
        <resource_set id="rsc_colocation-grpPg-clnPing-0" role="Master">
          <resource_ref id="msPostgresql"/>
        </resource_set>
        <resource_set id="rsc_colocation-grpPg-clnPing-1" sequential="false">
          <resource_ref id="vip-master"/>
          <resource_ref id="vip-rep"/>
        </resource_set>
      </rsc_colocation>

- Pattern 3 - 
colocation rsc_colocation-grpPg-clnPing INFINITY: msPostgresql:Master sequential=true vip-master vip-rep sequential=true

      <rsc_colocation id="rsc_colocation-grpPg-clnPing" score="INFINITY">
        <resource_set id="rsc_colocation-grpPg-clnPing-0" role="Master">
          <resource_ref id="msPostgresql"/>
        </resource_set>
        <resource_set id="rsc_colocation-grpPg-clnPing-1">
          <resource_ref id="vip-master"/>
          <resource_ref id="vip-rep"/>
        </resource_set>
      </rsc_colocation>

- Pattern 4 - 
colocation rsc_colocation-grpPg-clnPing INFINITY: msPostgresql:Master sequential=false vip-master vip-rep sequential=false

      <rsc_colocation id="rsc_colocation-grpPg-clnPing" score="INFINITY">
        <!--#colocation rsc_colocation-grpPg-clnPing INFINITY: [ msPostgresql:Master sequential=true ]-->
        <resource_set id="rsc_colocation-grpPg-clnPing-0" sequential="false" role="Master">
          <resource_ref id="msPostgresql"/>
        </resource_set>
        <resource_set id="rsc_colocation-grpPg-clnPing-1" sequential="false">
          <resource_ref id="vip-master"/>
          <resource_ref id="vip-rep"/>
        </resource_set>
      </rsc_colocation>

- Pattern 5 - 
colocation rsc_colocation-grpPg-clnPing INFINITY: [ msPostgresql:Master ] [ vip-master vip-rep ]

      <rsc_colocation id="rsc_colocation-grpPg-clnPing" score="INFINITY">
        <resource_set id="rsc_colocation-grpPg-clnPing-0" require-all="false" sequential="false" role="Master">
          <resource_ref id="msPostgresql"/>
        </resource_set>
        <resource_set id="rsc_colocation-grpPg-clnPing-1" require-all="false" sequential="false">
          <resource_ref id="vip-master"/>
          <resource_ref id="vip-rep"/>
        </resource_set>
      </rsc_colocation>

- Pattern 6 - 
colocation rsc_colocation-grpPg-clnPing INFINITY: ( msPostgresql:Master ) ( vip-master vip-rep )

      <rsc_colocation id="rsc_colocation-grpPg-clnPing" score="INFINITY">
        <resource_set id="rsc_colocation-grpPg-clnPing-0" sequential="false" role="Master">
          <resource_ref id="msPostgresql"/>
        </resource_set>
        <resource_set id="rsc_colocation-grpPg-clnPing-1" sequential="false">
          <resource_ref id="vip-master"/>
          <resource_ref id="vip-rep"/>
        </resource_set>
      </rsc_colocation>

- Pattern 7 - 
colocation rsc_colocation-grpPg-clnPing INFINITY: [ msPostgresql:Master sequential=true ] [ vip-master vip-rep sequential=true ]

      <rsc_colocation id="rsc_colocation-grpPg-clnPing" score="INFINITY">
        <resource_set id="rsc_colocation-grpPg-clnPing-0" require-all="false" role="Master">
          <resource_ref id="msPostgresql"/>
        </resource_set>
        <resource_set id="rsc_colocation-grpPg-clnPing-1" require-all="false">
          <resource_ref id="vip-master"/>
          <resource_ref id="vip-rep"/>
        </resource_set>
      </rsc_colocation>

- Pattern 8 - 
colocation rsc_colocation-grpPg-clnPing INFINITY: ( msPostgresql:Master sequential=true ) ( vip-master vip-rep sequential=true )

      <rsc_colocation id="rsc_colocation-grpPg-clnPing" score="INFINITY">
        <resource_set id="rsc_colocation-grpPg-clnPing-0" role="Master">
          <resource_ref id="msPostgresql"/>
        </resource_set>
        <resource_set id="rsc_colocation-grpPg-clnPing-1">
          <resource_ref id="vip-master"/>
          <resource_ref id="vip-rep"/>
        </resource_set>
      </rsc_colocation>

---------------------

How can true set sequantial attribute if I operate it in crmsh?

Best Regards,
Hideo Yamauchi.






More information about the Pacemaker mailing list