New issue
Advanced search Search tips

Issue 782947 link

Starred by 2 users
Status: Available
Owner: ----
Cc:
pprabhu@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature



Sign in to add a comment

Restrict usage of `atest host create`

Project Member Reported by akes...@chromium.org, Nov 8 2017 
Per discussion with pprabhu@, `atest host create` is not the intended way to add a new DUT to production cautotest, and is only kept around for use in moblab.

Is this correct?

If so: 
 1) What is the preferred way to add a host
 2) `atest host create` should error out when run against cautotest.

Comment 1 by jrbarnette@chromium.org, Nov 27 2017 

>  1) What is the preferred way to add a host

For the test lab in Stierlin Ct, hosts are added by the deployment
script.

Comment 2 by akes...@chromium.org, Nov 27 2017 

Is it worth making atest host create fail against cautotest/ then?

Comment 3 by jrbarnette@chromium.org, Nov 27 2017 

> Is it worth making atest host create fail against cautotest/ then?

If we can find an easy way to enforce it, then it's a reasonable
restriction.  We'd probably need to provide some sort of override
feature for the restriction; I think there are cases where we need
to create hosts in the database that aren't regular CrOS DUTs, and
so have to be created with `atest host create`.

Comment 4 by jrbarnette@chromium.org, Dec 5 2017

Labels: -Type-Bug -Pri-2 Pri-3 Type-Feature
Owner: ----
Status: Available (was: Assigned)
Summary: Restrict usage of `atest host create` (was: `atest host create` not intended for use in cautotest/ ?)
Changing the subject to reflect the actual ask.

The `atest host create` command shouldn't be allowed for hosts being
installed Stierlin Ct.  The command should be restricted to these
conditions:
  * For Moblab.
  * For hosts not managed by englab-sys-cros@ (meaning, labs outside of
    Stierlin Ct).

Comment 5 by cindyb@chromium.org, 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.
►

Sign in to add a comment