Hi Ulrich,
On Wed, Jul 03, 2013 at 11:50:59AM +0200, Ulrich Windl wrote:
> >>> Dejan Muhamedagic <[email protected]> schrieb am 03.07.2013 um 10:29 in
> Nachricht <[email protected]>:
> [...]
> > New resources can also be tested on all nodes by crm configure
> > rsctest. The test is completely driven by crmsh and won't disturb
> > the cluster in any way.
>
> Can you sketch the workflow? How are the tests done? Starting or stopping
> resources can disturb the cluster, BTW.
The resource shouldn't be committed yet. Or, otherwise, it should
be unmanaged. At any rate, not controlled by the cluster.
Here the help text:
$ crm configure help rsctest
Test resources with current resource configuration. If no nodes
are specified, tests are run on all known nodes.
The order of resources is significant: it is assumed that later
resources depend on earlier ones.
If a resource is multi-state, it is assumed that the role on
which later resources depend is master.
Tests are run sequentially to prevent running the same resource
on two or more nodes. Tests are carried out only if none of the
specified nodes currently run any of the specified resources.
However, it won't verify whether resources run on the other
nodes.
Superuser privileges are obviously required: either run this as
root or setup the `sudoers` file appropriately.
Note that resource testing may take some time.
Usage:
...............
rsctest <rsc_id> [<rsc_id> ...] [<node_id> ...]
...............
Examples:
...............
rsctest my_ip websvc
rsctest websvc nodeB
...............
Thanks,
Dejan
> Regards,
> Ulrich
>
>
> _______________________________________________
> Linux-HA mailing list
> [email protected]
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
