From: Marc Grimme <grimme@atix.de>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] rind-0.8.1 patch
Date: Thu, 7 Feb 2008 09:38:48 +0100 [thread overview]
Message-ID: <200802070938.48446.grimme@atix.de> (raw)
In-Reply-To: <1202317294.21504.50.camel@ayanami.boston.devel.redhat.com>
Something else I was thinking about when playing with those things:
1. Why are USER, CONFIG and MIGRATION events not yet being passed? It could be
quite interesting as well to trigger those.
2. And wouldn't it be a good idea to being able to call some kind of
higherlevel os-skript? I thought it might then be possible to generate a more
dynamic failoverdomain. For example one with the lowest loaded node being
lowest prioritized. That can be quite nice when having services or vms which
produce very high load.
Marc.
--
Gruss / Regards,
Marc Grimme
http://www.atix.de/ http://www.open-sharedroot.org/
next prev parent reply other threads:[~2008-02-07 8:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-30 16:49 [Cluster-devel] rind-0.8.1 patch Lon Hohberger
2008-02-04 17:41 ` Marc Grimme
2008-02-05 17:58 ` Lon Hohberger
2008-02-06 9:03 ` Marc Grimme
2008-02-06 17:01 ` Lon Hohberger
2008-02-06 17:22 ` Lon Hohberger
2008-02-06 19:18 ` Marc Grimme
2008-02-07 8:38 ` Marc Grimme [this message]
2008-02-08 20:56 ` Lon Hohberger
2008-02-14 21:56 ` Lon Hohberger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200802070938.48446.grimme@atix.de \
--to=grimme@atix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.