Another idea is to create a pacemaker:HealthCPU resource that updates
the #health-cpu attribute.
Now you can add a location constraint to your resource to migrate away
if #health-cpu is, lets say 'red'.
# pcs resource describe ocf:pacemaker:HealthCPU
Resource options for:
On 2014-02-21T13:02:23, Vladislav Bogdanov bub...@hoster-ok.com wrote:
It could be nice feature to have kind of general SLA concept (it could
be very similar to the utilization one from the resource configuration
perspective), so resources try to move or live migrate out of nodes
which have
21.02.2014 13:45, Lars Marowsky-Bree wrote:
On 2014-02-21T13:02:23, Vladislav Bogdanov bub...@hoster-ok.com wrote:
It could be nice feature to have kind of general SLA concept (it could
be very similar to the utilization one from the resource configuration
perspective), so resources try to
Hi,
I am wondering if it is possible to configure complex/custom migration
rules, so resources would migrate in case there is a problem with the
current node it is running on.
i.e.
If the node has a bad disk, or high load, the resource should be migrated
to a different node.
I didn't find any
On 20 Feb 2014, at 7:34 pm, Dan Markhasin minimi...@gmail.com wrote:
Hi,
I am wondering if it is possible to configure complex/custom migration rules,
so resources would migrate in case there is a problem with the current node
it is running on.
i.e.
If the node has a bad disk, or
Good idea, thanks. :-)
On Fri, Feb 21, 2014 at 1:58 AM, Andrew Beekhof and...@beekhof.net wrote:
On 20 Feb 2014, at 7:34 pm, Dan Markhasin minimi...@gmail.com wrote:
Hi,
I am wondering if it is possible to configure complex/custom migration
rules, so resources would migrate in case
