On Tue, Feb 23, 2010 at 4:00 AM, Angus Salkeld <[email protected]> wrote:
> On Mon, 2010-02-22 at 15:23 -0700, Steven Dake wrote:
>> On Thu, 2010-02-18 at 11:17 +1100, Angus Salkeld wrote:
>> > Hi
>> >
>> > This adds a test harness to corosync. It reuses the
>> > Cluster Test System (CTS) from pacemaker. It also
>> > has a test agent that runs on the cluster node that
>> > can perform any necessary application interaction with
>> > corosync. I have added only a few test cases, but
>> > once the mechanism in committed to corosync I will
>> > work to add more test cases (and hopefully others
>> > will be able to contribute too).
>> >
>> > Have a look in the README file in cts/ to get started.
>> >
>>
>> I have taken a crack at rewriting the readme to be a little more clear.
>> Hope you like.  It is attached.
>>
>> Regards
>> -steve
> Hi
>
> Here is a new version of the test harness that uses the latest from
> pacemaker-devel.
>
> Note:
> 1) for all the tests to pass you will also need to patch
> /usr/lib/python/site-packages/cts/CTS.py with the cts.patch (attached).
>
> 2) CTS now will by default not use remote syslog, so you don't need the
> syslog config supplied in the README.

Its not the default yet, but I'll probably make it an automatic fallback option.

>
> 3) It incluses Steve's README
>
> Regards
> Angus
>
>
>
>
>
> _______________________________________________
> Openais mailing list
> [email protected]
> https://lists.linux-foundation.org/mailman/listinfo/openais
>
_______________________________________________
Openais mailing list
[email protected]
https://lists.linux-foundation.org/mailman/listinfo/openais

Reply via email to