On Thu, Mar 18, 2010 at 1:16 PM, Andreas Mock <andreas.m...@web.de> wrote: > -----Ursprüngliche Nachricht----- > Von: Andrew Beekhof <and...@beekhof.net> > Gesendet: 18.03.2010 09:48:23 > An: General Linux-HA mailing list <linux-ha@lists.linux-ha.org> > Betreff: Re: [Linux-HA] Usage of Cluster-Testsuite > >>Its actually pretty easy now (we've dropped the requirement for remote >>logging). >>Just install pacemaker-devel on a test "master" and make sure you can >>ssh (as root with no password*) to all of the cluster nodes from it. >> >>Define your cluster nodes: >> export cluster_hosts="a b c d" >> >>Tell CTS if the nodes are configured to start the cluster when they >>boot (0 for no, 1 for yes): >> export at_boot=0 >> >>Then just run: >> python ./CTSlab.py --nodes "$cluster_hosts" --at-boot $at_boot >>--stack corosync --stonith no 500 >> >> >>"--stonith no" disables the stonithd test. >> > > > Hi Andrew, > > thanks for giving a point to start from. I'll try it. > What kind of logging would you recommend (e.g. config snippet) to > get meaningful informations about the cluster test? >
You mean when there is a problem? Just run hb_report from the test master as you would normally except use -f cts:N , where N is a test that failed _______________________________________________ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
