To manage a machine, MAAS must be able to power cycle it, usually through the machine’s BMC card. Until you configure the power type, a newly-added machine can’t be enlisted and used by MAAS.
To configure a machine’s power type, click on the machine from the ‘Machines’ page of the web UI, then select its ‘Configuration’ tab. Scroll down until you find the Power configuration. If the power type is undefined, the following will be displayed:
Choose a type in the dropdown menu that corresponds to the machine’s underlying machine’s BMC card.
Fill in the resulting form; the information required will depends on the power type.
Click ‘Save changes’ to finish. Once that’s done, MAAS performs a power check on the machine. A successful power check is a good indication that MAAS can properly communicate with the machine, that is, it should quickly result in a power status of “Power off”. A failed attempt will show:
If you see this error, double-check your entered values by editing the power type, or consider another power type altogether.
Another possible cause for this error may be the networking: traffic may be getting filtered between the rack controller and the BMC card.
Consider a machine backed by VM. Below, a ‘Power type’ of
Virsh has been selected, and the ‘Power address’ of
qemu+ssh://email@example.com/system has been entered (replace values as appropriate). The value of ‘Power ID’ is the VM domain (guest) name, here
The machine’s hostname – according to MAAS – is a randomly chosen string (here
dear.ant). You should change this hostname to something descriptive, that helps you remember why this machine is in your MAAS network.
MAAS supports many types of BMC hardware, though not all the drivers have the same capabilities. See the below table for a feature comparison of the BMC drivers currently supported by MAAS.
Tell me about BMC
BMC, or “Baseboard Management Controller,” is an extra microcontroller on the motherboard of a server which forms the interface between system-management software and the device’s hardware. The BMC can collect data from attached sensors, alert administrators to issues, and respond to remote-control commands to control system operation or power state, independent of the system’s CPU.
In the context of MAAS, the BMC is generally controlled by SNMP commands. Any given BMC will function in the context of one or more “power types,” which are physical interfaces that permit use of the IPMI (“Intelligent Platform Management Interface”) protocol. Each power type has a different set of expected parameters required to access and command the BMC.
|Power Driver (X=supported)||PXE Next Boot||Power Querying||Chassis/Pod Configuration||Enhanced UI Error Reporting||BMC Enlistment|
|American Power Conversion (APC) - PDU|
|Cisco UCS Manager||X||X||X|
|Digital Loggers, Inc. - PDU|
|HP Moonshot - iLO Chassis Manager||X||X||X|
|HP Moonshot - iLO4 (IPMI)||X||X||X|
|IBM Hardware Management Console (HMC)||X||X|
|Microsoft OCS - Chassis Manager||X||X||X|
|Rack Scale Design||X||X||X|
|Sentry Switch CDU - PDU|
|Virsh (virtual systems)||X||X||X|
* The ‘Facebook’s Wedge’ OpenBMC power driver is considered experimental at this time.