Create a DUT inventory command |
||||||
Issue descriptionIt would be occasionally be handy to have dut-status just output the hostname as a way to query what duts exist for a given board/pool. This can be done by post-processing the output, but a command line option would be easier.
,
Aug 23 2016
That new command an extending atest both sound very similar, but I like the approach better that what I suggested.
,
Aug 23 2016
,
Sep 1 2016
OK. Broadening the proposed specification. We'd like
a single command that make is easy to describe the
inventory either by listing or counting DUTs meeting
specified criteria. The criteria should include:
* By specifically named boards.
* By specifically named pools.
* By a combined boards+pools specification.
* Restricted to just DUTs in specific categories of pool:
* "managed" - (including bvt, cq, and suites).
* "critical" - (all managed pools except for suites).
* "spare" - suites pool.
* For all DUTs *except for* one of the criteria above.
,
Sep 1 2016
,
Dec 6 2016
Do the various viceroy dashboards now cover this desire?
,
Dec 6 2016
I originally filed it wanting a way to pipe the list of dut names into new commands, so viceroy doesn't help.
,
May 3 2017
The following revision refers to this bug: https://chrome-internal.googlesource.com/chromeos/chromeos-admin/+/0eb3796dd36a40428c2b2b7c354a16980ac6a28e commit 0eb3796dd36a40428c2b2b7c354a16980ac6a28e Author: Richard Barnette <jrbarnette@google.com> Date: Wed May 03 03:48:59 2017
,
Jul 10 2017
,
Jun 8 2018
Hi, this bug has not been updated recently. Please acknowledge the bug and provide status within two weeks (6/22/2018), or the bug will be archived. Thank you.
,
Jul 18
We want to move in the direction of Swarming backed dashboards of DUT history. There is no plan to add specialized tooling for this atm. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by jrbarnette@chromium.org
, Aug 23 2016This will work: dut-status -nw -p $POOL -b $BOARD However, that's a pretty expensive way to do it; the command will determine the running/not running status of each DUT. It might also make sense to have more dut-status options to control which host fields get printed (cf. the -o options for 'ps'). However, the main purpose of dut-status is not really to list hosts, but to check the DUT repair status, which is expensive. So, it might make more sense to enhance the 'atest' command, instead. Alternatively, we could make a new command for querying the inventory in a way that's customized to know about things like boards and pools. That could also make it easy to query for things like counts instead of host names, which is another feature that we need.