On 2008-01-30T20:30:44, Tadashiro Yoshida <[EMAIL PROTECTED]> wrote:
> I understand that each project, PaceMaker and narrowly-defined Heartbeat,
> maintains own package.
>
> We then need an integrator to package those into broadly-defined Heartbeat.
No, this is not correct.
You do not need an integrator. You simply install both packages, and all
will be well, just as before.
> In my understanding, two broadly-defined Heartbeat packages will be released
> separately after this, one for openSUSE from SUSE and one for other Linux
> distribution from Alan. Is it right?
I hope not! That would be bad.
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 ;-)
I don't understand what you mean by "broadly defined packages".
PaceMaker will be released by Andrew, and no longer be part of heartbeat
itself. Anyone wishing to run (or test) PaceMaker on top of heartbeat
will have to install both packages.
Of course, part of the PaceMaker release process will be testing
PaceMaker on top of heartbeat.
> I am worried that the power of the community will be dispersed and
> weakened. Some trouble may be found in only one package because of
> different combination of the version of PaceMaker and narrowly-defined
> Heartbeat.
The usual response to any bug report by the community is to update all
components to their latest versions, as always ;-) So this problem is
unlikely to occur. (Such packages will be readily available from many
sources, too.)
> I strongly hope that Heartbeat community maintains same latest
> broadly-defined Heartbeat package on diversified Linux distributions.
The PaceMaker packages (the former CRM) will state which version of the
underlying infrastructure they were tested with, possibly even as a
package requirement.
This is the usual way how certification and testing works in software
stacks: higher levels certify the lower ones.
I expect that of course heartbeat releases will continue to be tested
with PaceMaker as a payload as well, possibly others. openAIS, the other
cluster infrastructure we're interested in, has their own testing as
well.
In fact, testing the layers independently - in addition to testing the
whole stack - is likley to yield higher quality results, also because it
will help improve the interfaces.
Dividing the community will only occur if people release competing
packages which include incomplete or outdated versions of the
CRM/PaceMaker code; the very thing this proposal was intended to avoid.
Regards,
Lars
--
Teamlead Kernel, SuSE Labs, Research and Development
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde
_______________________________________________________
Linux-HA-Dev: [email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/
