From: Marek Grac <mgrac@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Fence agent for Tripplite PDU
Date: Mon, 06 Jan 2014 14:01:16 +0100 [thread overview]
Message-ID: <52CAA91C.8030001@redhat.com> (raw)
In-Reply-To: <52B98DE8.1090803@mirantis.com>
Hi,
On 12/24/2013 02:36 PM, Bogdan Dobrelya wrote:
>> 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...
>
Thanks for patch, I have no objection and patch is now included in the
upstream.
m,
next prev parent reply other threads:[~2014-01-06 13:01 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
2014-01-06 13:01 ` Marek Grac [this message]
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=52CAA91C.8030001@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.