Labelling devices for MAAS

Tagging the untaggable: labelling MAAS devices

Errors or typos? Topics missing? Hard to read? Let us know!

Tagging in MAAS isn’t just a matter of slapdash annotations; it’s the art of precise identification for network configurations and hardware attributes. Utilising XPath functions such as contains, starts-with, and ends-with, you can streamline your MAAS setup. Check out these real-world examples that unleash the power of tagging. For an even deeper dive, explore more examples here^.

Hypervisor tags

Identify and categorise machines primed for hypervisor roles. This example scours for machines with at least 40 cores and 256 GB of RAM. The cherry on top? It filters machines with specific CPU features for both Intel and AMD.

Hypervisor Definition

Tailor the core and RAM requirements to your specific environment.

And for the CLI magicians:

maas ${MAAS_PROFILE} tags create name=hypervisor \


Isolate UEFI-enabled KVM virtual machines running on AMD servers. Streamline your hardware filtering for a smoother operation.


And the CLI version:

maas ${MAAS_PROFILE} tags create \

NVME servers

Instantly tag servers sporting NVME controllers for high-speed data storage.

NVME Servers

CLI code:

maas ${MAAS_PROFILE} tags create ...

Mellanox ConnectX-5

Identify servers featuring the highly sought-after Mellanox ConnectX-5 network cards.

ConnectX-5 NICs

The CLI rendition:

maas ${MAAS_PROFILE} tags create \

GPU passthrough

When you want to crunch graphical data on AMD processors, enable GPU passthrough for Nvidia Quadro K series GPUs.

Nvidia Quadro K Series

And yes, there’s a CLI for that:

maas ${MAAS_PROFILE} tags create \

Dive in and start optimising your MAAS setup with these tagging tips and tricks. Define, refine, and align your network configuration to make the most of your hardware.

Last updated a month ago.