[Linux-HA] Monitor only resource
Simon Rowe
srowe at cambridgebroadband.com
Tue Oct 18 06:47:08 MDT 2005
On Tuesday 18 Oct 2005 13:42, Simon Rowe wrote:
> I thought the following would force my resource group to be co-located with
> my cloned resource
Bah, would help if I included the CIB
<cib>
<configuration>
<crm_config>
<nvpair id="symmetric_cluster" name="symetric_cluster" value="true"/>
<nvpair id="suppress_cib_writes" name="suppress_cib_writes"
value="true"/>
<nvpair id="default_resource_stickiness"
name="default_resource_stickiness" value="INFINITY"/>
<nvpair id="no_quorum_policy" name="no_quorum_policy" value="ignore"/>
</crm_config>
<nodes/>
<resources>
<clone id="sonetlinkup_clone">
<instance_attributes>
<attributes>
<nvpair name="clone_max" value="2"/>
<nvpair name="clone_node_max" value="1"/>
</attributes>
</instance_attributes>
<primitive id="sonetlinkup" class="heartbeat" type="sonetlinkup">
<operations>
<op id="sonetlinkup1" name="monitor" interval="30s"
timeout="5s"/>
</operations>
</primitive>
</clone>
<group id="vectastar_group">
<primitive id="vsmgmtbridge" class="heartbeat" type="vsmgmtbridge">
</primitive>
<primitive id="vectastar" class="heartbeat" type="vectastar">
<operations>
<op id="vectstar1" name="monitor" interval="30s" timeout="5s"/>
</operations>
</primitive>
</group>
</resources>
<constraints>
<rsc_colocation id="glue" from="sonetlinkup_clone" to="vectastar_group"
score="INFINITY">
</rsc_colocation>
</constraints>
</configuration>
<status/>
</cib>
> However I see
>
> Oct 18 13:30:49 B local7.warn pengine: [5505]: WARN:
> mask(incarnation.c:clone_rsc_colocation_lh): Co-location scores other than
> "-INFINITY" are not allowed for non-clone resources
>
> which I did see in the docs. How do I make a non-cloned resource group only
> run where an instance of a cloned resource is running?
More information about the Linux-HA
mailing list