What about labels <http://autotest.kernel.org/wiki/ConfiguringHosts>? You can assign arbitrary labels to hosts, and then select hosts based on these labels. E.g.
atest host list --label=1u,fast,storage selects hosts with labels "1u", "fast" and "storage". From the web frontend you can also select multiple labels. >From within the test, given a set of machines, you could query each machine (e.g. host.run() to get the amount of storage attached) to further determine which should be the server and which the clients. -Jongki On Thu, Jan 13, 2011 at 11:11 AM, Tommi Virtanen <[email protected]> wrote: > Hi. We're trying to use Autotest for the Ceph cluster filesystem > (http://ceph.newdream.net/) and are running out of good examples. > > Say we have two kinds of machines: 4U beefy servers to use as storage > nodes, and 1U machines that are just fast enough to act as clients. > We'd want to run tests that need e.g. 1 server and 2 client machines > to complete. Or 7 servers and 20 clients. > > Even better would be to have Autotest understand which machines are in > which rack/row, so we could have the test network traffic never > traverse between two rows in the data center -- we don't want the > central switches to be the bottleneck. > > I'm looking at ACLs, metahosts, atomic groups, host_group_name, > --execution-tag= but just can't figure out if something already allows > me to do this. Right now ACLs seem the most promising approach.. > > Worst case, I write my own resource allocation, call autoserv with a > pre-picked -m argument, and use extra knowledge about hostnames to > decide what machine does what. > > Any ideas? > > -- > :(){ :|:&};: > _______________________________________________ > Autotest mailing list > [email protected] > http://test.kernel.org/cgi-bin/mailman/listinfo/autotest >
_______________________________________________ Autotest mailing list [email protected] http://test.kernel.org/cgi-bin/mailman/listinfo/autotest
