cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Fabio M. Di Nitto <fdinitto@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Eaton fence agent and more power devices support
Date: Mon, 24 Jan 2011 14:31:30 +0100	[thread overview]
Message-ID: <4D3D7F32.9090902@redhat.com> (raw)
In-Reply-To: <AANLkTimRcajPLf37fes9-=REu6o+0=U-uaVnxW-6Aize@mail.gmail.com>

On 1/24/2011 2:19 PM, Arnaud Quette wrote:
> Hi Fabio,
> 
> 2011/1/24 Fabio M. Di Nitto <fdinitto@redhat.com
> <mailto:fdinitto@redhat.com>>
> 
>     On 1/24/2011 1:18 PM, Arnaud Quette wrote:
>     > Hi Marek,
>     >
>     > 2011/1/20 Marek 'marx' Gr?c
>     >
>     >     Hi,
>     >
>     >
>     >     Arnaud Quette wrote:
>     >
>     >         Hi Marek and the list,
>     >
>     >         First of all, happy new year to you all: health, happiness and
>     >         ... high availability ;-)
>     >
>     >         I've just derived a fence_eaton_snmp script, based on
>     >         fence_apc_snmp.
>     >         You'll find attached the diff against the latest fence-agents
>     >         repository.
>     >
>     >         This has been tested with the suitable hardware (Eaton Managed
>     >         ePDU): http://www.epdu.com
>     >         Can you please merge this for the next cman releases.
>     >
>     >     Finally, I was able to review your code. I have few minor
>     >     suggestions how to make code be better but we can solve that
>     later.
>     >     But I can do that later when we will have an access to this
>     device.
>     >     Fence agent will be part of the next fence-agents package.
>     >
>     >
>     > excellent, thanks.
>     > Do you have any idea about the next official release date?
> 
>     It won?t be too long before I?ll cut another upstream release. I am
>     waiting for Marek to push some last fixes and we should be good to go.
> 
>  
> perfect timing.
> is an RPM update also scheduled?
> 

Yes, they always come together.

>     > I'm still checking with Fabio to provide a suitable device for
>     Denmark.
> 
>     Ok perfect, let me know how the search goes. I sent the plug spec in
>     another email. Shouldn?t be too hard to get it. Worst case, send me
>     something that supports 220v/50hz and I?ll do some surgery on other
>     cables :)
> 
> 
> well, the voltage and ouput plugs are not the issue.
> but the input seems to be. I've just got in touch with our Danish
> representative to finalize this.

If it?s a problem, as long as voltage and output plugs do match, I can
handmade a cable. Let?s not make it too complicated.

> I should be able to send you an update around tomorrow.

Ok perfect.

thanks
Fabio



      reply	other threads:[~2011-01-24 13:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-11 15:53 [Cluster-devel] Eaton fence agent and more power devices support Arnaud Quette
2011-01-20 12:35 ` Marek 'marx' Grác
2011-01-24 12:18   ` Arnaud Quette
2011-01-24 12:47     ` Fabio M. Di Nitto
2011-01-24 13:19       ` Arnaud Quette
2011-01-24 13:31         ` Fabio M. Di Nitto [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=4D3D7F32.9090902@redhat.com \
    --to=fdinitto@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).