BMC Power Types

In order for MAAS to fully manage a node it must be able to power cycle it. This is done via a communication channel with the BMC card of the node's underlying system. A newly added node is therefore incomplete until its power type has been configured. Since each BMC card is different, the required information to provide MAAS will vary.

To configure a power type, visit the 'Nodes' page, select the node in question and scroll down to the 'Power' section. There, you should see MAAS prompting you to set up the power type:

power types section

Choosing the 'Edit' button will reveal a list of available power types:

power types selection

Example: Virsh (KVM) power type

Consider a node backed by KVM. Below, a 'Power type' of Virsh has been selected and the 'Power address' of qemu+ssh://ubuntu@ has been entered (replace values as appropriate). Finally, and out of necessity for virsh, the value of 'Power ID' is the KVM domain (guest) name, here node.

power types example: virsh

See MAAS CLI for an example of how to edit a power type with the CLI.

See Add nodes for help in setting up MAAS and KVM to work together.

BMC driver support

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.

BMC driver feature table
Power Driver (X=supported)PXE Next BootPower QueryingChassis ConfigurationEnhanced UI Error ReportingBMC Enlistment
American Power Conversion (APC) - PDU
Cisco UCS ManagerXXX
Digital Loggers, Inc. - PDU
HP Moonshot - iLO Chassis ManagerXXX
HP Moonshot - iLO4 (IPMI)XXX
IBM Hardware Management Console (HMC)XX
Microsoft OCS - Chassis ManagerXXX
OpenStack NovaX
SeaMicro 15000XXX
Sentry Switch CDU - PDU
Virsh (virtual systems)XXX

© 2018 Canonical Ltd. Ubuntu and Canonical are registered trademarks of Canonical Ltd.