All of lore.kernel.org
 help / color / mirror / Atom feed
From: Digimer <lists@alteeve.ca>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] fence-agents-4.0.2 stable release
Date: Tue, 30 Jul 2013 09:55:42 -0400	[thread overview]
Message-ID: <51F7C5DE.7040509@alteeve.ca> (raw)
In-Reply-To: <51F79CE1.3040707@redhat.com>

On 30/07/13 07:00, Marek Grac wrote:
> Welcome to the fence-agents 4.0.2 release.
>
> This release includes a minor bug fix, invalid names in fence_eps,
> fence_rhevm and fence_xenapi.
>
> In this release you can also find a new fence agent for OVH
> (http://www.ovh.com) and symbolic link fence_ilo4 which runs
> fence_ipmilan with required arguments.
>
> For the 4.0.x series, I plan to release a new version on at least
> monthly basis.
>
> The new source tarball can be downloaded here:
>
> https://fedorahosted.org/releases/f/e/fence-agents/fence-agents-4.0.1.tar.xz
>
>
> To report bugs or issues:
>
> https://bugzilla.redhat.com/
>
> Would you like to meet the cluster team or members of its community?
>
>     Join us on IRC (irc.freenode.net #linux-cluster) and share your
>     experience  with other sysadministrators or power users.
>
> Thanks/congratulations to all people that contributed to achieve this
> great milestone.
>
> m,

Yet another release goes by and I didn't get around to asking for a new 
agent to be added. :) I've got a fence agent for TrippLite switched PDUs;

https://github.com/digimer/fence_tripplite_snmp

They're hardly ideal as fence devices because they are slow, but they do 
work reliably and their cost makes them very common in DCs.

Also, \o/ new release!

-- 
Digimer
Papers and Projects: https://alteeve.ca/w/
What if the cure for cancer is trapped in the mind of a person without 
access to education?



      reply	other threads:[~2013-07-30 13:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-30 11:00 [Cluster-devel] fence-agents-4.0.2 stable release Marek Grac
2013-07-30 13:55 ` Digimer [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=51F7C5DE.7040509@alteeve.ca \
    --to=lists@alteeve.ca \
    /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.