[Pacemaker] Migrating resources on custom conditions

[Dan Markhasin]

Good idea, thanks. :-)


On Fri, Feb 21, 2014 at 1:58 AM, Andrew Beekhof <andrew at beekhof.net> wrote:

>
> On 20 Feb 2014, at 7:34 pm, Dan Markhasin <minimizer at 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 high load, the resource should be
> migrated to a different node.
>
> If you write a resource agent that monitors any or all of the above
> conditions and add it to the cluster as an unmanaged clone resource, then
> you can colocate things with it.
> At the point the disk goes bad, the resource appears to have stopped and
> the real resources will be moved somewhere else.
>
> > I didn't find any examples for such custom rules in the documentation.
> Is it possible ?
> >
> > Thanks,
> > Dan
> > _______________________________________________
> > Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> > http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> >
> > Project Home: http://www.clusterlabs.org
> > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> > Bugs: http://bugs.clusterlabs.org
>
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20140221/a6b0514a/attachment-0003.html>