On Feb 4, 2008, at 6:23 AM, Tadashiro Yoshida wrote:
At Sun, 3 Feb 2008 18:51:26 +0100, [EMAIL PROTECTED] wrote in <[EMAIL PROTECTED]
>:
--------------------
On 2008-02-01T09:00:23, Tadashiro Yoshida <[EMAIL PROTECTED]
> wrote:
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.
What I would like to say is that we might have another target of
package for testing. ;-)
I'm not quite sure that I understand what you are saying here, I
have to
apologize. What do you mean?
I am confused completely. I have thought integrated product of
Heartbeat and PaceMaker will be tested and released in the SUSE's
Build Service.
The integrated product in the SUSE's Build Service could be one of
targets for testing in the community.
Do you mean PaceMaker only will be released, although SUSE will test
it with Heartbeat module in the Building Service?
And Alan will integrate Heartbeat and PaceMaker,
That would require an understanding of Pacemaker that Alan simply does
not have.
and release the integrated package, or integration should be done by
users???
Let me be very clear about a two of things:
1) There will never be a single package that combines Heartbeat
+Pacemaker. Ever.
2) Not having a combined package does not imply a need for
integration.
There is a need for integration _testing_ (which occurs normally as a
result of testing and releasing Pacemaker) but that is a validation
activity and not the same thing.
Integration is required when two components are developed in isolation
and later are required to work together.
This is clearly not the case for Pacemaker as it was designed for use
with Heartbeat from the beginning.
Perhaps things will be a little clearer if I explain how we use the
build service.
The build service is hosted by SUSE but, for the purposes of this
conversation, please try to ignore that... nothing I, Lars or Dejan
have done (or will do) on Pacemaker or Heartbeat is intended to be
only for SUSE's benefit.
The first step is that Alan releases a version of Heartbeat that is
presumably well tested and stable.
We then take that release and make it available on the build service
(so that it is also available for the distributions and architectures
he doesn't build for).
Some time later it is time to do a Pacemaker release...
We now take the current version of Heartbeat and begin testing
Pacemaker (http://www.clusterlabs.org/mw/Release_Testing).
Once testing is complete, we tag it in Mercurial, write the changelogs
and upload everything to the build service.
Think of the build service as our download page.
The resulting Pacemaker packages are built with the current Heartbeat
ones and require that exact version in order to be installed.
In this way we ensure that the two package versions will work together
and, since both are available from the same place, users are not
inconvenienced.
For those people not using the build service packages, we also update
the changelog and our releases page to indicate which Heartbeat
version testing was performed with.
http://www.clusterlabs.org/mw/Releases
You can of course use whatever combination of versions you like - it
just may be more work to choose a non-tested combination.
Chances are everything will work fine, since Heartbeat APIs do not
(and should not) change very often, but you would be advised to do
your own testing to be sure.
Does this help at all?
_______________________________________________________
Linux-HA-Dev: [email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/
