From: Marek Grac <mgrac@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] joining the gitfence-agents group
Date: Fri, 21 Mar 2014 11:50:59 +0100 [thread overview]
Message-ID: <532C1993.70503@redhat.com> (raw)
In-Reply-To: <CAMKtzE8CdzZVVYQ49qUhsRonkggL64_5FNd28kFN5tRy7eJAqg@mail.gmail.com>
Hi,
On 03/19/2014 10:26 PM, David Smith wrote:
> Hi marek, sure, no problem, here's the changes; also sent to
> cluster-devel.
thanks, for next time it will be easier to you and other reviewers if
you will sent a patch in a standard format. Take a look at
http://alblue.bandlem.com/2011/12/git-tip-of-week-patches-by-email.html
> I've already tested by manually running the fence-raritan agent that
> this is working and functional
>
code looks pretty good and after few minor changes it can be accepted.
These are my comments:
* please remove commented line of source code
* exception checking 'Due to limitations ...' is not required any
more because we have subpackage for every fence-agent so dependencies
can be solved properly
* default value can be now set more easier (--ipport in this case)
all_opt["ipport"]["default"] = "23"
* please add support also for delay before login which is very
useful for 2-node clusters
if options["--action"] in ["off", "reboot"]:
time.sleep(int(options["--delay"]))
m,
next prev parent reply other threads:[~2014-03-21 10:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMKtzE9pjic-cXah9_wKbEhxVmcQj+K4fH88voSdfKP4dPjLfw@mail.gmail.com>
[not found] ` <5329ABBE.70304@redhat.com>
2014-03-19 21:26 ` [Cluster-devel] joining the gitfence-agents group David Smith
2014-03-21 10:50 ` Marek Grac [this message]
2014-03-21 14:29 ` David Smith
2014-03-25 21:56 ` David Smith
2014-04-02 1:31 ` David Smith
2014-04-02 13:12 ` Marek Grac
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=532C1993.70503@redhat.com \
--to=mgrac@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 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.