From: Marek Grac <mgrac@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] fence-agents 3.1.11 stable release
Date: Mon, 05 Nov 2012 12:00:27 +0100 [thread overview]
Message-ID: <50979C4B.8020605@redhat.com> (raw)
Welcome to the fence-agents 3.1.11 release.
This release includes these updates:
* support new API used in RHEV-M 3.1
* fence_cisco_ucs incorrect timeout value was used during login operation
* support on/off also for fabric fence agents (which do not have
'reboot'). Support for enable/disable was not removed.
* fence_na support XML metadata output
* manual page for ipmilan was fixed to contain correct information about
usage for HP iLO3, iLO4
The new source tarball can be downloaded here:
https://fedorahosted.org/releases/f/e/fence-agents/fence-agents-3.1.11.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
milestone.
m,
reply other threads:[~2012-11-05 11:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=50979C4B.8020605@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 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).