From: David Teigland <teigland@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] RFC: generic improvement to fence agents api
Date: Mon, 21 Mar 2011 13:07:02 -0400 [thread overview]
Message-ID: <20110321170702.GA4306@redhat.com> (raw)
In-Reply-To: <4D844E8F.1050608@redhat.com>
On Sat, Mar 19, 2011 at 07:34:55AM +0100, Fabio M. Di Nitto wrote:
> My suggestion would be to allow to specify a list of ports instead.
This comes up now and then. The current rule of one action per agent
execution is a tried and true, fundamental property of the agent api.
It should not be changed IMO. I'll need some time to come up with the
various specific reasons against it, but at least one of them (a big
one) is partial failure/success.
Dave
next prev parent reply other threads:[~2011-03-21 17:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-19 6:34 [Cluster-devel] RFC: generic improvement to fence agents api Fabio M. Di Nitto
2011-03-19 17:14 ` Digimer
2011-03-19 17:32 ` Fabio M. Di Nitto
2011-03-19 18:44 ` Digimer
2011-03-21 8:40 ` Marek Grac
2011-03-21 10:44 ` Fabio M. Di Nitto
2011-03-21 17:07 ` David Teigland [this message]
2011-03-21 17:09 ` Digimer
2011-03-21 17:16 ` Fabio M. Di Nitto
2011-03-21 17:37 ` 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=20110321170702.GA4306@redhat.com \
--to=teigland@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).