All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Grac <mgrac@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 1/3] fencing: new option --method
Date: Thu, 19 Dec 2013 16:28:53 +0100	[thread overview]
Message-ID: <52B310B5.3080306@redhat.com> (raw)
In-Reply-To: <467334290.3048666.1385742734730.JavaMail.root@redhat.com>

Hi Ondrej,

I have several comments:

* please include patches so they depends only on upstream or posted 
series (2/3 can depend on 1/3)
     [ e.g. problem with -EC_TOOL_FAIL ]

On 11/29/2013 05:32 PM, Ondrej Mular wrote:
> Add new option method --method for cycle reboot
>
> ---
>   fence/agents/lib/fencing.py.py | 80 ++++++++++++++++++++++++++++++------------
>   1 file changed, 57 insertions(+), 23 deletions(-)
>
...
>   
> +def multi_reboot_cycle_fn(tn, options, reboot_cycle_fn):
> +	success = False;
> +	if options.has_key("--plugs"):
> +		for plug in options["--plugs"]:
> +			try:
> +				options["--uuid"] = str(uuid.UUID(plug))
> +			except ValueError:
> +				pass
> +			except KeyError:
> +				pass
> +			options["--plug"] = plug
> +			plug_status = reboot_cycle_fn(tn, options)
> +			if plug_status:
> +				success = plug_status
> +	else:
> +		success = reboot_cycle_fn(tn, options)
> +	return success
Although we support multiple ports (--plugs) it is possible only when 
using 'method=offon' because otherwise we will just reboot port #1, 
reboot port #2, ... so the machine with redundant power supply will not 
be rebooted. We should end with a failure message when users attempts to 
do this combination. imho it will be best to include this constrain 
directly to do it in check_input() in fencing library

m,



      reply	other threads:[~2013-12-19 15:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1894241096.3047584.1385741994148.JavaMail.root@redhat.com>
2013-11-29 16:32 ` [Cluster-devel] [PATCH 1/3] fencing: new option --method Ondrej Mular
2013-12-19 15:28   ` Marek Grac [this message]

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=52B310B5.3080306@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.