From: Fabio M. Di Nitto <fdinitto@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Cluster 3.0.13 stable release
Date: Tue, 08 Jun 2010 06:01:03 +0200 [thread overview]
Message-ID: <4C0DC07F.3030704@redhat.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
The cluster team and its community are proud to announce the 3.0.13
stable release from the STABLE3 branch.
This release contains a few major bug fixes. We strongly recommend
people to update their clusters.
In order to build/run the 3.0.13 release you will need:
- - corosync 1.2.3
- - openais 1.1.3
- - linux kernel 2.6.31 (only for GFS1 users)
The new source tarball can be downloaded here:
https://fedorahosted.org/releases/c/l/cluster/cluster-3.0.13.tar.bz2
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.
Happy clustering,
Fabio
Under the hood (from 3.0.12):
Bob Peterson (1):
Fix device name and mount point in utils
Christine Caulfield (2):
config: Fix ccs_tool create -n
cman: fix quorum recalculation when a node is externally killed
David Teigland (2):
dlm_controld: wrong fencing time comparison
dlm_controld: wrong fencing time comparison (2)
Fabio M. Di Nitto (2):
cman init: wait for corosync daemon to exit on stop
add missing man pages
Jonathan Brassow (1):
halvm: Fix bug 506587: lvm agent incorrectly reports vg is in
volume_list
Lon Hohberger (1):
resource-agents: Resolve incorrect default
Marek 'marx' Grac (1):
fence_wti: Add direct support for WTI VMR
cman/daemon/commands.c | 6 +++---
cman/init.d/cman.in | 7 +++++++
cman/man/Makefile | 3 ++-
cman/man/cman_notify.8 | 17 +++++++++++++++++
config/tools/ccs_tool/editconf.c | 2 +-
fence/agents/wti/fence_wti.py | 2 +-
gfs2/libgfs2/misc.c | 27 +++++++++++++++------------
group/dlm_controld/cpg.c | 23 +++++++++++++++++------
group/man/Makefile | 2 ++
group/man/dlm_controld.pcmk.8 | 1 +
group/man/gfs_controld.pcmk.8 | 1 +
rgmanager/src/resources/lvm.sh | 2 +-
rgmanager/src/resources/vm.sh | 2 +-
13 files changed, 69 insertions(+), 26 deletions(-)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBCAAGBQJMDcB9AAoJEFA6oBJjVJ+O1CYP/2ACxWh9jqKGK3PLogZo1ICA
RkkCFu9qGT3bd16xz+38XRUp62Wgwos/TsBiJoiQnjC9275HcWvV2Vye+OIRaGsU
yCo4Rk9bTX0o534yMEh/sijApJjKrhD3uzw4Ed15alfy/8q+7uSUs7m/mi+LsKc3
SJ2UxHJ9I4KUVmtHn8e49dDS8L/0ybwyQCq32pzvsnPJy1XiJObMbfVbcU9+2yPj
dt3C5R0J+/P7mASZdHfIsMvMj0/cpssZnWcJjK1F8pbIEJyBNC6TbYeIo37euD8L
T1mrLkGSx+Z9Lwzct4sq+DaebMXVZEXO9Q63NzpMfrbG1unoQrZDGpTtEI3qVHCp
/pvCYaGtuFpiqyAQpbQnNAWpv4gVP7KKhAdRdaJJ7FpPgQ7Ir/+Cvh5XRz/6dLw5
CL4nhjVciAOyqQs3CUoTd8TnoQmWMZjMwKnWYyiPXlWookzLfhfNYsHyWLbP0MxJ
6W/wR6E0jSVxCrb4tsqfEL2gUWoMaeHitUSNAf+l4cjZp6WVuVBIL+RPya/UOUmE
c+nmkUCkLJs9/aiEdzt2s7hKToOgUbQFcq6fV8MZxC9jYj2rpxypDFLDolB/LYPj
YXtzRfSedrj3U+zxRJRddEZa0/DQcZz2c5ERthQhE7yeNgk6uwiozzfMGh/6g2+y
7vfO0A1fJgb/zqdXQRgj
=9hrR
-----END PGP SIGNATURE-----
reply other threads:[~2010-06-08 4:01 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=4C0DC07F.3030704@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).