cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Alan Evangelista <alanoe@linux.vnet.ibm.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] fence-agents integration with Cobbler
Date: Thu, 23 Oct 2014 16:56:06 -0200	[thread overview]
Message-ID: <54494F46.70605@linux.vnet.ibm.com> (raw)

Hi.

I'm a Cobbler developer. Cobbler uses fence-agents to perform power 
management in systems
and it currently supports fence-agents 4.0.4. I want to make Cobbler 
compatible with
latest fence-agents code. Cobbler may run in RHEL 6+ and thus we expect 
fence-agents
to also do it. I'm doing tests with the lpar fence agent.

First, I found out the master branch requires Python 2.7. Using master 
code in a RHEL 6.5
threw an exception in the creation of a StreamHandler object (stream 
argument name in StreamHandler
constructor changed from Python 2.6, available on RHEL 6, to Python 2.7, 
available on RHEL 7).

Then, I found out that there is a RHEL6 branch and tried to use it. 
However, some fence
agents (eg lpar) uses different input parameters names in RHEL6 and 
master branches.
This would force me to check RHEL version before generating fence agents 
input in Cobbler.

Would it be possible to either

(1) backport input parameters names changes to RHEL6 branch? afaik input 
parameters names are independent of RHEL version.
(2) support Python 2.6 in master branch


I'm also open to other alternatives.


Regards,
Alan Evangelista



             reply	other threads:[~2014-10-23 18:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-23 18:56 Alan Evangelista [this message]
2014-10-27  9:13 ` [Cluster-devel] fence-agents integration with Cobbler Marek marx 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=54494F46.70605@linux.vnet.ibm.com \
    --to=alanoe@linux.vnet.ibm.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).