[Pacemaker] Resource capacity limit
Yan Gao
ygao at novell.com
Fri Nov 6 07:27:47 UTC 2009
Hi Andrew,
Andrew Beekhof wrote:
> On Tue, Nov 3, 2009 at 12:15 PM, Yan Gao <ygao at novell.com> wrote:
>> Hi again,
>>
>> Yan Gao wrote:
>>
>> XML sample:
>> ..
>> <nodes>
>> <node id="yingying" type="normal" uname="yingying">
>> <utilization id="nodes-yingying-utilization">
>> <nvpair id="nodes-yingying-memory" name="memory" value="150"/>
>> <nvpair id="nodes-yingying-cpu" name="cpu" value="1"/>
>> </utilization>
>> </node>
>> </nodes>
>> ..
>> <resources>
>> <primitive class="ocf" id="Dummy0" provider="heartbeat" type="Dummy">
>> <utilization id="Dummy0-utilization">
>> <nvpair id="Dummy0-utilization-memory" name="memory" value="90"/>
>> <nvpair id="Dummy0-utilization-cpu" name="cpu" value="1"/>
>> </utilization>
>> </primitive>
>> <primitive class="ocf" id="Dummy1" provider="heartbeat" type="Dummy">
>> <utilization id="Dummy1-utilization">
>> <nvpair id="Dummy1-utilization-memory" name="memory" value="60"/>
>> <nvpair id="Dummy1-utilization-cpu" name="cpu" value="1"/>
>> </utilization>
>> </primitive>
>> </resources>
>> ..
>>
>> Please kindly review it...
>> Any suggestions are appreciated!
>
> Whats the behavior if a node has either no utilization block or no
> value for that attribute?
If so, it would be regarded that the node has no any capacity or no that
specific capacity.
> Can a resource with a utilization block still be placed there?
No, unless the utilization block is blank. As long as any attribute is set
in resource utilization, which means the resource requests some kind of
capacity, while a node has no that capacity, the node would not be considered.
A interesting case is, if a resource has no utilization block, it would be regarded
that the resource doesn't consume any capacity. so it could be placed on any node,
even the node has no utilization block (no any capacity).
Do you think the behavior is reasonable?
Thanks,
Yan
--
ygao at novell.com
Software Engineer
China Server Team, OPS Engineering
Novell, Inc.
Making IT Work As One™
More information about the Pacemaker
mailing list