[Pacemaker] Resource capacity limit

[Lars Marowsky-Bree]

On 2009-11-03T19:15:59, Yan Gao <ygao at novell.com> 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!

I think this is exactly what we need. Great job!

Code looks good too.

Andrew?


For added kicks, which may be something Andrew can add more readily, I
wonder if utilization should also be subject to time-based evaluation.
Think of a database needing more horsepower on weekdays - but perhaps
that is something that should wait until dynamic load balancing
happens.


Regards,
    Lars

-- 
Architect Storage/HA, OPS Engineering, Novell, Inc.
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde