Tools » teuthology

(Probably it is could be interpreted as a request to good documentation but I believe code fix also needed.)

Now, in teuthology, fields 'up' (in pulpito/paddles) is used as two different signs

- (1) node is could be achieved via a network (docs/_statis/create_nodes.py line 59 )

- (2) node is disabled/enabled for usage (paddles/blob/master/paddles/models/nodes.py , "t9y-lock --lock-many" operation )

- (3) just ignored ( "t9y-lock --lock" event with multilock usage with target.yaml file )

I suppose, there is the inconsistency of usage, and inconsistency of logic.

It will be pretty useful to somewhere describe the logic of field 'up' and probably do changes of (1) to avoid automatically set the field or
set it automatically after provisioning in (2,3) and probably take care about the field in "lock --lock" in (3) and/or update it when node is available (2,3) and/or
add new field 'enabled' which shows a node availability for automated operation.

I have a feeling that the best is adding a new filed which logically separated availability via network and availability for automated usage,
but, probably, it could be somehow problematic for current already used instances in lab.

is it any other ideas about how it should be solved?