Glad to see Blake taking this on, it bites me every time I setup a MAAS with NUCs.
In summary, MAAS should check out what else is available, and maintain a flag for the JS to check if there might be a problem. So on startup MAAS might check for things like amtterm, and if they are not available, it would include a warning flag in a JSON that the UI has access to. The UI can then auto-warn whenever appropriate. For example:
* when adding a machine with AMT
* when looking at a machine with AMT
The equivalent tests / JSON flags would be done for each different set of tools.
Glad to see Blake taking this on, it bites me every time I setup a MAAS with NUCs.
In summary, MAAS should check out what else is available, and maintain a flag for the JS to check if there might be a problem. So on startup MAAS might check for things like amtterm, and if they are not available, it would include a warning flag in a JSON that the UI has access to. The UI can then auto-warn whenever appropriate. For example:
* when adding a machine with AMT
* when looking at a machine with AMT
The equivalent tests / JSON flags would be done for each different set of tools.