maas-devel team mailing list archive
-
maas-devel team
-
Mailing list archive
-
Message #01691
Re: Allow API to use <system_id | hostname> for all operations that currently require the system_id
> More precisely, it would make it very easy to get the system id of a node
> whose hostname you know; I'm thinking about something along the lines of:
>
> $ maas <profile> nodes list hostname=<hostname> *limit=1
> get-field=system_id* → system_id
>
> The main functionality already exists (getting the filtered list of
> nodes); the part the we would need to add would be the limitation and the
> field extraction.
>
> @Andres & al. don't you think that, if you had access (through a very
> clear call to the CLI) to the system_id of a node using its hostname, this
> would solve your usability problem?
>
>
This would indeed partially solve the usability problem, however, this
still does not completely solve it because there's still some overhead. We
would still (and always) have to get the system_id of a node or all nodes.
In our day to day operations we experience the issue of having to do this
for every single system we want to make changes to, say its tags or any
other operation. Having to get the system_id for each of the system it
really has translated into a lack of better usability in our particular
case escenario.
>
> R.
>
> --
> Mailing list: https://launchpad.net/~maas-devel
> Post to : maas-devel@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~maas-devel
> More help : https://help.launchpad.net/ListHelp
>
--
Andres Rodriguez
Engineering Manager, HWE Team
Canonical USA, Inc.
Follow ups
References