From: Fabio M. Di Nitto <fdinitto@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [Linux-cluster] fence-agents-4.0.16 stable release
Date: Thu, 05 Mar 2015 20:23:25 +0100 [thread overview]
Message-ID: <54F8AD2D.7050604@redhat.com> (raw)
In-Reply-To: <54F8426E.4080500@redhat.com>
On 3/5/2015 12:47 PM, Marek "marx" Grac wrote:
> Welcome to the fence-agents 4.0.16 release
>
> This release includes several bugfixes and features:
> * fence_kdump has implemented 'monitor' action that check if local node
> is capable of working with kdump
> * path to smnp(walk|get|set) can be set at runtime
> * new operation 'validate-all' for majority of agents that checks if
> entered parameters are sufficient without connecting to fence
> device. Be aware that some checks can be done only after we receive
> information
> from fence device, so these are not tested.
> * new operation 'list-status' that present CSV output (plug_number,
> plug_alias, plug_status) where status
> is ON/OFF/UNKNOWN
>
> Git repository was moved to https://github.com/ClusterLabs/fence-agents/
> so this is last
> release made from fedorahosted.
>
> The new source tarball can be downloaded here:
>
> https://fedorahosted.org/releases/f/e/fence-agents/fence-agents-4.0.16.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.
There is a new IRC channel in use now. #clusterlabs on Freenode. We are
slowly dismissing #linux-cluster and centralize all cluster related
activities on the new channel.
Fabio
parent reply other threads:[~2015-03-05 19:23 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <54F8426E.4080500@redhat.com>]
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=54F8AD2D.7050604@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 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.