Acquiring a specific node can be accomplished via the cmdline or api via hostname
maas-cli maaslocal nodes acquire name=$host
However, then after acquiring the node if I want to start it I have to do:
maas-cli maaslocal node start $SYSTEM_ID
The two separate pieces of information needed is annoying.
Things I'd like improved:
* ability to acquire a specific node by its node id:
maas-cli maaslocal nodes acquire system_id=$SYSTEM_ID
* ability to start a node by its hostname. Since hostname is valid for acquire, it would be useful to suffice for start also. Although if I can use system_id in both cases, this is less important.
* api or cmdline failure or complaint based on invalid input
Currently if I try to acquire a system and pass data like:
acquire frobnicator=19 flex_capacitor=true
Maas will happily return me a system. I'd like it complain that it doesn't know what a fronicator is. I found this when trying to use 'system_id='
Acquiring a specific node can be accomplished via the cmdline or api via hostname
maas-cli maaslocal nodes acquire name=$host
However, then after acquiring the node if I want to start it I have to do:
maas-cli maaslocal node start $SYSTEM_ID
The two separate pieces of information needed is annoying.
Things I'd like improved: id=$SYSTEM_ ID
* ability to acquire a specific node by its node id:
maas-cli maaslocal nodes acquire system_
* ability to start a node by its hostname. Since hostname is valid for acquire, it would be useful to suffice for start also. Although if I can use system_id in both cases, this is less important.
* api or cmdline failure or complaint based on invalid input
Currently if I try to acquire a system and pass data like:
acquire frobnicator=19 flex_capacitor=true
Maas will happily return me a system. I'd like it complain that it doesn't know what a fronicator is. I found this when trying to use 'system_id='