>>> On Sat, Jul 14, 2007 at 8:52 PM, in message <[EMAIL PROTECTED]>, Alan Robertson <[EMAIL PROTECTED]> wrote: > Hi,
[...] > To summarize: > > Every official project release passes through these two clusters > > Any major set of changes which hasn't done so probably > has undiscovered timing problems in it. > Of course, we don't claim to find them all. > So far this seems to have been very effective at > keeping them out of _your_ clusters ;- ). > > When a project partner works with us on their release schedule, > we try hard to put out a project release just before > their release - that's been tested by these two > cantankerous clusters. Of course, all developers > have access to this cluster on their own. > > Hope this background helps people understand a little better about how > we test. Also to recap, for the LinuxHA release shipped by a major SLES release, Novell pushes the code through its automated cluster testing process. Iirc, ship criteria for SLES10 was something like an 8 node cluster, running in a lab with hundreds of client desktops, reconnecting to e.g. a Samba service intentionally failing over from one server to another continuously for many days. This was one of a few large scale tests, in addition to various functional tests that exercise LinuxHA integration with e.g. OCFS2, iSCSI etc, on smaller clusters run by feature teams who test additional services in HA clusters. Jfyi fwiw ;-) Hth, RObert _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
