Appendix A. Power management drivers
Although IPMI is the main method that director uses for power management control, director also supports other power management types. This appendix contains a list of the power management features that director supports. Use these power management settings when you register nodes for the overcloud. For more information, see Registering nodes for the overcloud.
A.1. Intelligent Platform Management Interface (IPMI)
The standard power management method when you use a baseboard management controller (BMC).
- pm_type
-
Set this option to
ipmi. - pm_user; pm_password
- The IPMI username and password.
- pm_addr
- The IP address of the IPMI controller.
- pm_port (Optional)
- The port to connect to the IPMI controller.
A.2. Redfish
A standard RESTful API for IT infrastructure developed by the Distributed Management Task Force (DMTF)
- pm_type
-
Set this option to
redfish. - pm_user; pm_password
- The Redfish username and password.
- pm_addr
- The IP address of the Redfish controller.
- pm_system_id
-
The canonical path to the system resource. This path must include the root service, version, and the path/unqiue ID for the system. For example:
/redfish/v1/Systems/CX34R87. - redfish_verify_ca
-
If the Redfish service in your baseboard management controller (BMC) is not configured to use a valid TLS certificate signed by a recognized certificate authority (CA), the Redfish client in ironic fails to connect to the BMC. Set the
redfish_verify_caoption tofalseto mute the error. However, be aware that disabling BMC authentication compromises the access security of your BMC.
A.3. Dell Remote Access Controller (DRAC)
DRAC is an interface that provides out-of-band remote management features including power management and server monitoring.
- pm_type
-
Set this option to
idrac. - pm_user; pm_password
- The DRAC username and password.
- pm_addr
- The IP address of the DRAC host.
A.4. Integrated Lights-Out (iLO)
iLO from Hewlett-Packard is an interface that provides out-of-band remote management features including power management and server monitoring.
- pm_type
-
Set this option to
ilo. - pm_user; pm_password
- The iLO username and password.
- pm_addr
The IP address of the iLO interface.
-
To enable this driver, add
iloto theenabled_hardware_typesoption in yourundercloud.confand rerunopenstack undercloud install. Director also requires an additional set of utilities for iLo. Install the
python3-proliantutilspackage and restart theopenstack-ironic-conductorservice:$ sudo dnf install python3-proliantutils $ sudo systemctl restart openstack-ironic-conductor.service
- HP nodes must have a minimum ILO firmware version of 1.85 (May 13 2015) for successful introspection. Director has been successfully tested with nodes using this ILO firmware version.
- Using a shared iLO port is not supported.
-
To enable this driver, add
A.5. Fujitsu Integrated Remote Management Controller (iRMC)
Fujitsu iRMC is a Baseboard Management Controller (BMC) with integrated LAN connection and extended functionality. This driver focuses on the power management for bare metal systems connected to the iRMC.
iRMC S4 or higher is required.
- pm_type
-
Set this option to
irmc. - pm_user; pm_password
- The username and password for the iRMC interface.
- pm_addr
- The IP address of the iRMC interface.
- pm_port (Optional)
- The port to use for iRMC operations. The default is 443.
- pm_auth_method (Optional)
-
The authentication method for iRMC operations. Use either
basicordigest. The default isbasic - pm_client_timeout (Optional)
- Timeout (in seconds) for iRMC operations. The default is 60 seconds.
- pm_sensor_method (Optional)
Sensor data retrieval method. Use either
ipmitoolorscci. The default isipmitool.-
To enable this driver, add
irmcto theenabled_hardware_typesoption in yourundercloud.confand rerun theopenstack undercloud installcommand. If you enable SCCI as the sensor method, you must also install an additional set of utilities. Install the
python3-scciclientpackage and restart theopenstack-ironic-conductorservice:$ dnf install python3-scciclient $ sudo systemctl restart openstack-ironic-conductor.service
-
To enable this driver, add
A.6. Red Hat Virtualization
This driver provides control over virtual machines in Red Hat Virtualization (RHV) through its RESTful API.
- pm_type
-
Set this option to
staging-ovirt. - pm_user; pm_password
-
The username and password for your RHV environment. The username also includes the authentication provider. For example:
admin@internal. - pm_addr
- The IP address of the RHV REST API.
- pm_vm_name
- The name of the virtual machine to control.
- mac
A list of MAC addresses for the network interfaces on the node. Use only the MAC address for the Provisioning NIC of each system.
-
To enable this driver, add
staging-ovirtto theenabled_hardware_typesoption in yourundercloud.confand rerun theopenstack undercloud installcommand.
-
To enable this driver, add
A.7. manual-management Driver
Use the manual-management driver to control bare metal devices that do not have power management. Director does not control the registered bare metal devices, and you must perform manual power operations at certain points in the introspection and deployment processes.
This option is available only for testing and evaluation purposes. It is not recommended for Red Hat OpenStack Platform enterprise environments.
- pm_type
Set this option to
manual-management.- This driver does not use any authentication details because it does not control power management.
-
To enable this driver, add
manual-managementto theenabled_hardware_typesoption in yourundercloud.confand rerun theopenstack undercloud installcommand. -
In your
instackenv.jsonnode inventory file, set thepm_typetomanual-managementfor the nodes that you want to manage manually. -
When performing introspection on nodes, manually start the nodes after running the
openstack overcloud node introspectcommand. -
When performing overcloud deployment, check the node status with the
openstack baremetal node listcommand. Wait until the node status changes fromdeployingtodeploy wait-callbackand then manually start the nodes. -
After the overcloud provisioning process completes, reboot the nodes. To check the completion of provisioning, check the node status with the
openstack baremetal node listcommand, wait until the node status changes toactive, then manually reboot all overcloud nodes.
