Unleash the power of MAAS to create flexible, cohesive data centres
In this introduction, you'll get succinct answers to key questions:
MAAS, or "Metal As A Service," morphs your bare-metal servers into an agile cloud-like environment. Forget fussing over individual hardware; treat them as fluid resources similar to instances in AWS, GCE, or Azure. MAAS is adept as a standalone PXE/preseed service, but it truly shines when paired with Juju, streamlining both machine and service management. Network booting via PXE? Even virtual machines can join the MAAS ecosystem.
PXE, or "Preboot Execution Environment" (often called "pixie"), empowers machines to load OS images via network interfaces. This requires a PXE-compatible NIC, configurable through software switches.
MAAS transforms a vast collection of physical servers into flexible resource pools. It seamlessly provisions, repurposes, and deallocates resources, letting you focus on the bigger picture. Want to delve into hardware details before deployment? MAAS scrutinises attached USB and PCI devices, allowing optional exclusion.
[v3.4 and above] Full USB and PCI device discovery. [/] [v2.9] Feature unavailable in version 2.9. [/]
MAAS wraps 13 critical features into one cohesive interface:
Easily scale and manage your data centre with these integrated tools.
If CLI is your preference, here are 11 features you shouldn't overlook:
Note: Windows and RHEL compatibility may require Ubuntu Pro for seamless integration.
MAAS architecture comprises two linchpins: the region controller and the rack controller. The former orchestrates data centre-wide operations while the latter focuses on individual racks. For a streamlined setup, co-locating these controllers is advisable, and it's the default in MAAS installations. This config also brings DHCP into the mix.