For MAAS to fully manage a machine, it must be able to power cycle it, usually through a communication channel with the BMC card of the machine’s underlying system. Until you configure the power type, a newly-added machine is considered incomplete.
Quick questions you may have:
- How do I configure a machine’s power type?
- Can you give me an example of the virsh power type?
- Which BMC drivers are supported?
Configure a machine's power type
To configure a machine’s power type, begin by clicking on the machine from the ‘Machines’ page of the web UI followed by its ‘Configuration’ tab. Scroll down for 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 requested will depend upon the power type chosen.
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. A successful power check will quickly result in a power status of “Power off”. A failed one will show:
If you get such an error, double-check your entered values by editing the power type. Also, consider another power type altogether. Another cause may be at the networking level; traffic may be getting filtered between the rack controller and the BMC card.
An example: the Virsh power type
Consider a machine backed by VM. Below, a ‘Power type’ of
Virsh has been selected, and the ‘Power address’ of
qemu+ssh://firstname.lastname@example.org/system has been entered (replace values as appropriate). Finally, and out of necessity for virsh, 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 edit this hostname would to reflect the hostname of the underlying machine.
Which BMC drivers are supported
MAAS supports many types of BMC hardware, yet 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.