cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Marek Grac <mgrac@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Fence agents - breaking compatibility
Date: Sun, 25 Nov 2012 14:41:11 +0100	[thread overview]
Message-ID: <50B21FF7.5000404@redhat.com> (raw)

Hi,

In last few weeks there were a lot of internal changed in source code of 
fence agents to make code more readable, clean and adaptable. In order 
to clean up code a bit more and remove historical burden, we would like 
to remove/replace some options (details are in 7 patches at cluster-devel).

These changes will be part of next major version of fence agents. There 
will be at least one upstream release (3.1.12) without these changes.

Brief overview:

* most of the fence agents:
     * removed option -T / test (command line / STDIN) --> you can use 
-o monitor / action to test if fence device is working
     * removed option -q / quiet --> fence agents are quiet enough by 
default
     * replaced --udpport / udpport --> use --ipport / ipport
     * on STDIN we also supported these options (this transition was 
done automatically in code) which are now replaced
         blade -> port
         option -> action
         fm -> port
         hostname -> ippaddr

* (fence_drac5) removed  -m / modulename / module_name --> replaced by 
standard -n / --plug / port
     this affect only Dell Drac CMC as other Drac devices do not use 
machine specification at all
* (fence_lpar) removed -n / partition --> replaced by standard -n / 
--plug / port

* (fence_rsb) removed -n / telnet_port --> replaced by --ipport / ipport

m,



                 reply	other threads:[~2012-11-25 13:41 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=50B21FF7.5000404@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 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).