All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabio M. Di Nitto <fdinitto@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] fence-agents 3.1.3 stable release
Date: Mon, 04 Apr 2011 17:35:45 +0200	[thread overview]
Message-ID: <4D99E551.9050605@redhat.com> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Welcome to the fence-agents 3.1.3 release.

This release contains a few bug fixes and a new fence_vmware_soap that
integrates and supports everything supported by the SOAP API v4.1
(including vSphere).

NOTE the new vmware agent requires python-suds.

The new source tarball can be downloaded here:

https://fedorahosted.org/releases/f/e/fence-agents/fence-agents-3.1.3.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.

Happy clustering,
Fabio

Under the hood (from 3.1.2):

Arnaud Quette (1):
      eaton_snmp: fix list offset

Brandon Perkins (1):
      Fence_rhevm needs to change "RUNNING" status to "UP" status as the
REST-AP

Jim Ramsay (1):
      Allow fence_scsi to use any valid hexadecimal key

Lon Hohberger (1):
      fence-agents: Accept other values for "true"

Marek 'marx' Grac (10):
      fence_rhevm: Update URL to RHEV-M REST API
      fence_cisco_ucs: Support for sub-organization
      fence_cisco_ucs: Fix for support for sub-organization
      library: Add support for UUID (-U / --uuid / uuid)
      fence_vmware_soap: New fence agent for VMWare using SOAP API
      fence_cisco_ucs, fence_rhevm: Problems with SSL support
      fence_ipmilan: returns incorrect status on monitor op if chassis
is powere
      fence_ipmilan: Correct return code for diag operation
      library: Add support for URL session instead of hostname
      bugfix uuid

Ryan O'Hara (2):
      fence_scsi: fix typo when opening logfile
      fence_scsi: grep for keys should be case insensitive

 configure.ac                                  |    1 +
 fence/agents/Makefile.am                      |    1 +
 fence/agents/cisco_ucs/fence_cisco_ucs.py     |   15 ++-
 fence/agents/eaton_snmp/fence_eaton_snmp.py   |    8 +-
 fence/agents/ipmilan/ipmilan.c                |   13 ++
 fence/agents/lib/fencing.py.py                |   32 ++++-
 fence/agents/rhevm/fence_rhevm.py             |    5 +-
 fence/agents/scsi/fence_scsi.pl               |   12 +-
 fence/agents/vmware_soap/Makefile.am          |   17 +++
 fence/agents/vmware_soap/fence_vmware_soap.py |  175
+++++++++++++++++++++++++
 10 files changed, 261 insertions(+), 18 deletions(-)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBCAAGBQJNmeVQAAoJEFA6oBJjVJ+O0mMP+wdZLnYAWRKhFFm8pdllvbbw
ZndPK13Xg/DtH5MkKiSjEl/aAmz7HwPW3Ml5XY5hlC6T6kE9V1nlA5/rfvU+2LQP
IjDDCr9RiEMmsqJOxhNjzyPX38k5HyasEnpRdPfrW7yPwOg4KuWiqTaxGJzN6mKa
/5OoXOKH1oadYUDcWGOT4ffYIo8ZlTAcpJmE1qp7ZP0h3w/o5XuFjCDRdMMJJc0Z
VvYpAlfRYEvZy5pAYyEaMGpPv+Yw6PsOR2pFAwi75I9diTuwVqqyrnyPU8XZgTvB
vMgY5OvbQcIwu9nXATH9QmAtvY805CyQmHVJHC56nUsNT1QzuW1AId63V0jUr6+F
kkUyzerjN3nta41HAWEHdP0LY8F+0kNRQ5zPbwzvL9/mxqnOTz6MgxYy5lVJvMSh
llIfsGZp+ZqmMbQw3ZXpAUT1lDibybhLlLvrTNF0iE6Am1gEMUmgJ0tCuzUG5H6K
6vbisPrv0ZT0IdQBZ3DPDuRH1VpmQ6gvUHd2pFkF+qKTKEzdL4Ns51X/lFXYPrU5
R2TQyr3alO0YKyIkDeDRJmHNYo6hDNjpe8lF9OTUu2Cw+Vih2W6FJ7m5SkcmFeGq
Wu8v3/D56yvP9RVzSNobu1Z7NsTMYLuPEqHuvRQugtB3x+uFdCyNy+tV5jfyRb0W
jJL7y9/UAcT+r05+Mdwe
=kYZf
-----END PGP SIGNATURE-----



                 reply	other threads:[~2011-04-04 15:35 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=4D99E551.9050605@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.