[Linux-ha-dev] Re: RFC: Roadmap for 2.2.0

[Andrew Beekhof]

On Jan 31, 2008, at 12:38 AM, Lars Marowsky-Bree wrote:

> On 2008-01-31T08:24:08, Tadashiro Yoshida <yoshida.tadashiro at oss.ntt.co.jp 
> > wrote:
>
>> But from our experiences, it is not enough for enterprise use from  
>> the view of quality. Someone should integrate plural packages and  
>> test it intensively.

It would be incredibly difficult to do release testing for a cluster  
manager _without_ doing integration testing with the underlying  
cluster stacks.

>> It is efficient if all of community member can test one integrated  
>> package, like PostgreSQL project.

Should we also include libnet, libxml2, glib, et al. in the Heartbeat  
package?  Clearly not.
Does X11 bundle KDE in its packages?  Does the kernel bundle iputils?  
Again, no.

If one followed your scenario to it's logical conclusion, then the  
SUSE and Red Hat DVD's would contain a single rpm package containing  
the complete distribution.
Clearly this is not the case and for good reason.

What we are doing here is hardly without precedent.  You may have  
heard of the X11 project that did a similar thing.
If they can get by without a monolithic package, then I'm sure we can  
too.


Pacemaker does not belong to or in Heartbeat.  Neither is Heartbeat  
the only cluster stack that will be using Pacemaker.

A combined package is not only unnecessary but also utterly  
inappropriate.


> Right; of course the overall combination needs to be tested as well.
> Again, this happens naturally when PaceMaker is tested in combination
> with heartbeat as the membership layer, which is of course part of the
> PaceMaker release process.
>
> Distributors such as Red Hat, SUSE/Novell, Ubuntu etcetera will of
> course continue to also perform their own tests of their packages.
>
> Testing the full stack is important; it does not matter whether this
> stack has been installed from one or two packages.

Lars is completely correct

>
> For Enterprise use, I cannot resist to add an advertisement for SLES,
> where we of course support heartbeat+PaceMaker/CRM for Enterprise  
> usage
> and will even accept money for it ;-)
>
>
>
>>> openSUSE's Build Service is just that: it provides a build  
>>> environment
>>> for all distributions, not just openSUSE. RedHat, RHEL, CentOS,  
>>> Debian,
>>> Ubuntu, Fedora, and by coincidence openSUSE/SLES as well ;-)
>> Do you mean you could accept any modification even if some troubles  
>> are found in another distribution other than openSUSE?
>
> Certainly! We already do that today; always have, always will. I don't
> think we have ever refused a bug on any distribution.

Just to emphasis this point, if one looks through the mail archives,  
you will find we have a long history of going out of our way to  
accommodate not only other Linux distributions, but other  
_operating_systems_ as well.  I for one do most of my development work  
on Darwin.

The fact that we have non-SUSE packages for OpenAIS, Heartbeat and  
Pacemaker on the build service should underline our commitment to  
supporting those parts of the community that do not run SUSE products.