Since LP:1883333 landed on 2.7, 2.8, and master you can use any field which starts with system_, mainboard_, mainboard_firmware_, or chassis_. The full list is available over the API
maas maas machine read tmynb8 | jq '.hardware_info'
{
"system_vendor": "QEMU",
"system_product": "Standard PC (Q35 + ICH9, 2009)",
"system_family": "Unknown",
"system_version": "pc-q35-4.0",
"system_sku": "Unknown",
"system_serial": "Unknown",
"cpu_model": "Intel Core Processor (Skylake, IBRS)",
"mainboard_vendor": "Unknown",
"mainboard_product": "Unknown",
"mainboard_serial": "Unknown",
"mainboard_version": "Unknown",
"mainboard_firmware_vendor": "SeaBIOS",
"mainboard_firmware_date": "04/01/2014",
"mainboard_firmware_version": "1.13.0-1ubuntu1",
"chassis_vendor": "QEMU",
"chassis_type": "Other",
"chassis_serial": "Unknown",
"chassis_version": "pc-q35-4.0"
}
There are also two tags which scripts can be applied to scripts which have special meaning
- commissioning - Any testing script which is tagged “commissioning” will be automatically selected during testing if no user input is given. By default the smartctl-validate test is tagged “commissioning” which is why it runs by default. Removing that tag will result in that script not being automatically run.
- noauto - Commissioning scripts which are tagged “noauto” won’t be automatically selected when commissioning is run. This was done to solve LP:1881919 and is only available in MAAS 2.7, 2.8, and master.