[Cluster-devel] Cluster 3.0.0 final stable release

[Cluster-devel] Cluster 3.0.0 final stable release

[Fabio M. Di Nitto]

The cluster team and its community are proud to announce the 3.0.0 final
release from the STABLE3 branch.

"And now what?"

The STABLE3 branch will continue to receive bug fixes and improvements
as feedback from our community and users will flow in.
Regular update releases will be available to sync with corosync/openais
releases and new kernels (for gfs1-kernel module).

In order to build the 3.0.0 release you will need:

- corosync 1.0.0
- openais 1.0.0
- linux kernel 2.6.29

The new source tarball can be downloaded here:

ftp://sources.redhat.com/pub/cluster/releases/cluster-3.0.0.tar.gz
https://fedorahosted.org/releases/c/l/cluster/cluster-3.0.0.tar.gz

At the same location is now possible to find separated tarballs for
fence-agents and resource-agents as previously announced
(http://www.redhat.com/archives/cluster-devel/2009-February/msg00003.htm)

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.0.rc4):

David Teigland (1):
      gfs_controld: fix default plock_ownership in compat mode

Fabio M. Di Nitto (3):
      contrib: Remove askant
      contrib: fix build warnings in libaislock
      libccs: fix yet another uint -> hdb_handle_t conversion

Guido G?nther (1):
      init scripts: add force-reload targets

Lon Hohberger (4):
      config: Update relaxng schema for broadcast options
      config: Update cluster.rng with new RA params
      config: Update cluster.ldif
      config: Fix misnamed statusmax -> status_child_max

 cman/init.d/cman.in                        |    2 +-
 config/libs/libccsconfdb/libccs.c          |    9 +-
 config/plugins/ldap/99cluster.ldif         |   84 ++++--
 config/plugins/ldap/ldap-base.csv          |   18 +-
 config/tools/xml/cluster.rng               |   70 ++++--
 contrib/Makefile                           |    2 +-
 contrib/askant/INSTALL                     |   42 ---
 contrib/askant/Makefile                    |   24 --
 contrib/askant/PLUGINAPI                   |   65 -----
 contrib/askant/README                      |   74 -----
 contrib/askant/askant/about.py             |    5 -
 contrib/askant/askant/askant.py            |   24 --
 contrib/askant/askant/blktrace.py          |   93 -------
 contrib/askant/askant/commands.py          |  333
-----------------------
 contrib/askant/askant/sysfs.py             |   86 ------
 contrib/askant/fsplugins/gfs2/gfs2.c       |  404
----------------------------
 contrib/askant/fsplugins/gfs2/gfs2.h       |    3 -
 contrib/askant/fsplugins/gfs2/gfs2module.c |  104 -------
 contrib/askant/scripts/askant              |    6 -
 contrib/askant/setup.py                    |   16 --
 contrib/libaislock/libaislock.c            |   10 +-
 doc/COPYRIGHT                              |    3 -
 gfs/init.d/gfs.in                          |    2 +-
 gfs2/init.d/gfs2.in                        |    2 +-
 group/gfs_controld/config.c                |   10 +-
 group/gfs_controld/gfs_daemon.h            |    1 +
 group/gfs_controld/main.c                  |    6 +
 rgmanager/init.d/rgmanager.in              |    2 +-
 28 files changed, 148 insertions(+), 1352 deletions(-)

Funny stats (STABLE2 vs STABLE3):

- Over 10000 lines of code have been killed from the latest (now old)
stable release.

- Almost 56000 lines of code have been rewritten or changed.

- Changes spread across over 730 files.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20090708/e876dad3/attachment.sig>

[Cluster-devel] Cluster 3.0.0 final stable release

[Marc]

Hello Fabio,


Am Mittwoch, den 08.07.2009, 23:10 +0200 schrieb Fabio M. Di Nitto:
> The cluster team and its community are proud to announce the 3.0.0 final
> release from the STABLE3 branch.
> 
> "And now what?"
> 
> The STABLE3 branch will continue to receive bug fixes and improvements
> as feedback from our community and users will flow in.
> Regular update releases will be available to sync with corosync/openais
> releases and new kernels (for gfs1-kernel module).
> 
> In order to build the 3.0.0 release you will need:
> 
> - corosync 1.0.0
> - openais 1.0.0
> - linux kernel 2.6.29

are there any (even untested) patches for kernel 2.6.30 gfs1 out there?

We plan to move from stable2 to stable3 on our test-systems soonish and
want to move up to 2.6.30 for gfs2 fixes but still want use gfs1 for
performance comparsion...

thanks,


Marc

gfs1 for 2.6.30 (Was Re: [Cluster-devel] Cluster 3.0.0 final stable release)

[Fabio M. Di Nitto]

On Mon, 2009-07-13 at 19:44 +0200, Marc - A. Dahlhaus [ Administration |
Westermann GmbH ] wrote:
> Hello Fabio,
> 
> 
> Am Mittwoch, den 08.07.2009, 23:10 +0200 schrieb Fabio M. Di Nitto:
> > The cluster team and its community are proud to announce the 3.0.0 final
> > release from the STABLE3 branch.
> > 
> > "And now what?"
> > 
> > The STABLE3 branch will continue to receive bug fixes and improvements
> > as feedback from our community and users will flow in.
> > Regular update releases will be available to sync with corosync/openais
> > releases and new kernels (for gfs1-kernel module).
> > 
> > In order to build the 3.0.0 release you will need:
> > 
> > - corosync 1.0.0
> > - openais 1.0.0
> > - linux kernel 2.6.29
> 
> are there any (even untested) patches for kernel 2.6.30 gfs1 out there?

Not that I am aware of. The gfs team should know when it will be
available.

> 
> We plan to move from stable2 to stable3 on our test-systems soonish and
> want to move up to 2.6.30 for gfs2 fixes but still want use gfs1 for
> performance comparsion...

Understood. The gfs team did prefer to release gfs1 at 2.6.29 for 3.0.0
but there should be an update soon. I am not aware of a specific time
yet tho as I left for vacation shortly after 3.0 release ;)

Fabio

[Cluster-devel] Re: gfs1 for 2.6.30

[Marc]

Am Montag, den 13.07.2009, 20:38 +0200 schrieb Fabio M. Di Nitto:
> On Mon, 2009-07-13 at 19:44 +0200, Marc - A. Dahlhaus [ Administration |
> Westermann GmbH ] wrote:
> > Hello Fabio,
> > 
> > 
> > Am Mittwoch, den 08.07.2009, 23:10 +0200 schrieb Fabio M. Di Nitto:
> > > The cluster team and its community are proud to announce the 3.0.0 final
> > > release from the STABLE3 branch.
> > > 
> > > "And now what?"
> > > 
> > > The STABLE3 branch will continue to receive bug fixes and improvements
> > > as feedback from our community and users will flow in.
> > > Regular update releases will be available to sync with corosync/openais
> > > releases and new kernels (for gfs1-kernel module).
> > > 
> > > In order to build the 3.0.0 release you will need:
> > > 
> > > - corosync 1.0.0
> > > - openais 1.0.0
> > > - linux kernel 2.6.29
> > 
> > are there any (even untested) patches for kernel 2.6.30 gfs1 out there?
> 
> Not that I am aware of. The gfs team should know when it will be
> available.
> 
> > 
> > We plan to move from stable2 to stable3 on our test-systems soonish and
> > want to move up to 2.6.30 for gfs2 fixes but still want use gfs1 for
> > performance comparsion...
> 
> Understood. The gfs team did prefer to release gfs1 at 2.6.29 for 3.0.0
> but there should be an update soon. I am not aware of a specific time
> yet tho as I left for vacation shortly after 3.0 release ;)


Enjoy it. :)

Thanks for the clarification.


Marc

[Cluster-devel] Re: gfs1 for 2.6.30

[Marc]

Am Dienstag, den 14.07.2009, 09:26 +0200 schrieb Marc - A. Dahlhaus
[ Administration | Westermann GmbH ]:
> Am Montag, den 13.07.2009, 20:38 +0200 schrieb Fabio M. Di Nitto:
> > On Mon, 2009-07-13 at 19:44 +0200, Marc - A. Dahlhaus [ Administration |
> > Westermann GmbH ] wrote:
> > > Hello Fabio,
> > > 
> > > 
> > > Am Mittwoch, den 08.07.2009, 23:10 +0200 schrieb Fabio M. Di Nitto:
> > > > The cluster team and its community are proud to announce the 3.0.0 final
> > > > release from the STABLE3 branch.
> > > > 
> > > > "And now what?"
> > > > 
> > > > The STABLE3 branch will continue to receive bug fixes and improvements
> > > > as feedback from our community and users will flow in.
> > > > Regular update releases will be available to sync with corosync/openais
> > > > releases and new kernels (for gfs1-kernel module).
> > > > 
> > > > In order to build the 3.0.0 release you will need:
> > > > 
> > > > - corosync 1.0.0
> > > > - openais 1.0.0
> > > > - linux kernel 2.6.29
> > > 
> > > are there any (even untested) patches for kernel 2.6.30 gfs1 out there?
> > 
> > Not that I am aware of. The gfs team should know when it will be
> > available.
> > 
> > > 
> > > We plan to move from stable2 to stable3 on our test-systems soonish and
> > > want to move up to 2.6.30 for gfs2 fixes but still want use gfs1 for
> > > performance comparsion...
> > 
> > Understood. The gfs team did prefer to release gfs1 at 2.6.29 for 3.0.0
> > but there should be an update soon. I am not aware of a specific time
> > yet tho as I left for vacation shortly after 3.0 release ;)
> 
> 
> Enjoy it. :)
> 
> Thanks for the clarification.


FYI:

i used the attached patch (based on the 2.6.31-rc4 patch in gfs1-utils
from Steven Whitehouse) to build stable3 against 2.6.30...

Marc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gfs-2.6.30.patch
Type: text/x-patch
Size: 1057 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20090731/b2ed558a/attachment.bin>

[Cluster-devel] Re: gfs1 for 2.6.30

[Fabio M. Di Nitto]

hi Mark,

thanks I'll make sure it's part of the next point release for 3.0.1.

Fabio

On Fri, 2009-07-31 at 12:02 +0200, Marc - A. Dahlhaus [ Administration |
Westermann GmbH ] wrote:
> Am Dienstag, den 14.07.2009, 09:26 +0200 schrieb Marc - A. Dahlhaus
> [ Administration | Westermann GmbH ]:
> > Am Montag, den 13.07.2009, 20:38 +0200 schrieb Fabio M. Di Nitto:
> > > On Mon, 2009-07-13 at 19:44 +0200, Marc - A. Dahlhaus [ Administration |
> > > Westermann GmbH ] wrote:
> > > > Hello Fabio,
> > > > 
> > > > 
> > > > Am Mittwoch, den 08.07.2009, 23:10 +0200 schrieb Fabio M. Di Nitto:
> > > > > The cluster team and its community are proud to announce the 3.0.0 final
> > > > > release from the STABLE3 branch.
> > > > > 
> > > > > "And now what?"
> > > > > 
> > > > > The STABLE3 branch will continue to receive bug fixes and improvements
> > > > > as feedback from our community and users will flow in.
> > > > > Regular update releases will be available to sync with corosync/openais
> > > > > releases and new kernels (for gfs1-kernel module).
> > > > > 
> > > > > In order to build the 3.0.0 release you will need:
> > > > > 
> > > > > - corosync 1.0.0
> > > > > - openais 1.0.0
> > > > > - linux kernel 2.6.29
> > > > 
> > > > are there any (even untested) patches for kernel 2.6.30 gfs1 out there?
> > > 
> > > Not that I am aware of. The gfs team should know when it will be
> > > available.
> > > 
> > > > 
> > > > We plan to move from stable2 to stable3 on our test-systems soonish and
> > > > want to move up to 2.6.30 for gfs2 fixes but still want use gfs1 for
> > > > performance comparsion...
> > > 
> > > Understood. The gfs team did prefer to release gfs1 at 2.6.29 for 3.0.0
> > > but there should be an update soon. I am not aware of a specific time
> > > yet tho as I left for vacation shortly after 3.0 release ;)
> > 
> > 
> > Enjoy it. :)
> > 
> > Thanks for the clarification.
> 
> 
> FYI:
> 
> i used the attached patch (based on the 2.6.31-rc4 patch in gfs1-utils
> from Steven Whitehouse) to build stable3 against 2.6.30...
> 
> Marc