cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Bogdan Dobrelya <bdobrelia@mirantis.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Fence agent for Tripplite PDU
Date: Tue, 24 Dec 2013 15:36:40 +0200	[thread overview]
Message-ID: <52B98DE8.1090803@mirantis.com> (raw)
In-Reply-To: <52B2F537.8060002@redhat.com>

On 12/19/2013 03:31 PM, Marek Grac wrote:
> On 12/16/2013 05:10 PM, Bogdan Dobrelya wrote:
>>
>> As far as I was testing my Tripplite PDU device with standard fence
>> agents, I've tried to find any suitable agent for it (fence_apc,
>> fence_apc_snmp) but didn't succeed. That's why I've played with
>> cmd-prompt and ssh-options of fence_apc agent mentioned above.
>>
>> But I've managed to succeed with customized fence_pdu_snmp (not with
>> fence_pdu tho) agent I created from fence_apc_snmp with minimal
>> changes (fixed OIDs and that is almost all).
>> I'd like to propose this fence_pdu_snmp agent as well (tested with
>> PDUMH20HVNET 12.04.0055 (snmp v1,v2c,v3) device). See a patch in
>> attachement, targeted for RHEL6 branch. I believe, it might be
>> compatible with any switched PDU devices, if slightly modified.
>>
> If the only modification was done in OIDs, I will prefer to include it
> into fence_apc_snmp. We have already used a symlinks to run fence agents

Done. Here are 2 patches for master and RHEL6 branches for
fence_apc_snmp agent, with added Tripplite PDU support.

> with different default options and I believe we can use same approach
> there as well (e.g. fence_ilo3 / fence_ipmilan). Can you take a look at
> current upstream version and test it there? Ideally check if it will

I've tested the patch for RHEL6 branch with my Tripplite PDU. And as you
could have noticed, there is no difference between the patch for RHEL6
and one for master branch, thus, you can assume tests is OK for master
as well...

> work without additional switches or we should implement there a variable
> which will be set only for tripplite and not for apc.
> 
> m,

As you can see from fence_apc_snmp's original README, it doesn't support
ganged or 'daisy-chained' switches yet, thus nothing was changed here.


-- 
Best regards,
Bogdan Dobrelya,
Researcher TechLead, Mirantis, Inc.
+38 (066) 051 07 53
Skype bogdando_at_yahoo.com
Irc #bogdando
38, Lenina ave.
Kharkov, Ukraine
www.mirantis.com
www.mirantis.ru
bdobrelia at mirantis.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-MASTER-Add-Tripplite-PDU-support-to-fence_apc_snmp.patch
Type: text/x-patch
Size: 3044 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20131224/8f82e8e5/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-RHEL6-Add-Tripplite-PDU-support-to-fence_apc_snmp.patch
Type: text/x-patch
Size: 2807 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20131224/8f82e8e5/attachment-0001.bin>

  reply	other threads:[~2013-12-24 13:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <52A74740.8020904@redhat.com>
     [not found] ` <52A82671.1000604@mirantis.com>
2013-12-11  9:28   ` [Cluster-devel] Fwd: some fence_virsh, fene_apc patches for RHEL6 backports Bogdan Dobrelya
2013-12-16 15:14   ` [Cluster-devel] Fw: " Marek Grac
2013-12-16 16:10     ` Bogdan Dobrelya
2013-12-19 13:31       ` [Cluster-devel] Fence agent for Tripplite PDU Marek Grac
2013-12-24 13:36         ` Bogdan Dobrelya [this message]
2014-01-06 13:01           ` Marek Grac
2013-12-18 13:42     ` [Cluster-devel] Fw: some fence_virsh, fene_apc patches for RHEL6 backports Bogdan Dobrelya
2013-12-19 13:13       ` Marek Grac
2013-12-24 13:23         ` Bogdan Dobrelya

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=52B98DE8.1090803@mirantis.com \
    --to=bdobrelia@mirantis.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).