Chapter 11. Bare Metal (ironic) Parameters
Parameter | Description |
---|---|
| List of additional architectures to enable. |
| IPA image URLs, the format should be ["http://path/to/kernel", "http://path/to/ramdisk"]. |
|
Enables or disables automated cleaning. Disabling automated cleaning might result in security problems and deployment failures on rebuilds. Do not set to |
|
Type of disk cleaning before and between deployments. |
|
Name or UUID of the overcloud network used for cleaning bare metal nodes. Set to |
| The name of an OpenStack Bare Metal (ironic) Conductor Group. |
|
Whether to configure Swift temporary URLs for use with the "direct" and "ansible" deploy interfaces. The default value is |
| Indicate whether this resource may be shared with the domain received in the request "origin" header. |
|
How to boot the bare metal instances. Set to |
| Deploy interface implementation to use by default. Leave empty to use the hardware type default. |
| Inspect interface implementation to use by default. Leave empty to use the hardware type default. |
|
Network interface implementation to use by default. Set to |
|
Default rescue implementation to use. The "agent" rescue requires a compatible ramdisk to be used. The default value is |
| Default resource class to use for new nodes. |
|
Backend to use to store ramdisk logs, either "local" or "swift". The default value is |
|
Number of IPv6 addresses to allocate for ports created for provisioning, cleaning, rescue or inspection on DHCPv6-stateful networks. Different stages of the chain-loading process will request addresses with different CLID/IAID. Due to non- identical identifiers multiple addresses must be reserved for the host to ensure each step of the boot process can successfully lease addresses. The default value is |
|
Whether to enable use of staging drivers. The default value is |
|
Enabled BIOS interface implementations. Each hardware type must have at least one valid implementation enabled. The default value is |
|
Enabled boot interface implementations. Each hardware type must have at least one valid implementation enabled. The default value is |
|
Enabled console interface implementations. Each hardware type must have at least one valid implementation enabled. The default value is |
|
Enabled deploy interface implementations. Each hardware type must have at least one valid implementation enabled. The default value is |
|
Enabled OpenStack Bare Metal (ironic) hardware types. The default value is |
|
Enabled inspect interface implementations. Each hardware type must have at least one valid implementation enabled. The default value is |
|
Enabled management interface implementations. Each hardware type must have at least one valid implementation enabled. The default value is |
|
Enabled network interface implementations. Each hardware type must have at least one valid implementation enabled. The default value is |
|
Enabled power interface implementations. Each hardware type must have at least one valid implementation enabled. The default value is |
|
Enabled RAID interface implementations. Each hardware type must have at least one valid implementation enabled. The default value is |
|
Enabled rescue interface implementations. Each hardware type must have at least one valid implementation enabled. The default value is |
|
Enabled storage interface implementations. Each hardware type must have at least one valid implementation enabled. The default value is |
|
Enabled vendor interface implementations. Each hardware type must have at least one valid implementation enabled. The default value is |
|
Whether to force power state during sync. The default value is |
|
Whether to use iPXE instead of PXE for deployment. The default value is |
|
Port to use for serving images when iPXE is used. The default value is |
|
IPXE timeout in second. Set to 0 for infinite timeout. The default value is |
|
Image delivery method for the "direct" deploy interface. Use "swift" for the Object Storage temporary URLs, use "http" for the local HTTP server (the same as for iPXE). The default value is |
|
Comma-separated list of IPA inspection collectors. The default value is |
|
The default driver to use for newly discovered nodes (requires IronicInspectorEnableNodeDiscovery set to True). This driver is automatically added to enabled_drivers. The default value is |
|
Makes ironic-inspector enroll any unknown node that PXE-boots introspection ramdisk in OpenStack Bare Metal (ironic). The default driver to use for new nodes is specified by the IronicInspectorDiscoveryDefaultDriver parameter. Introspection rules can also be used to specify it. The default value is |
|
Comma-separated list of processing hooks to append to the default list. The default value is |
|
Whether to use iPXE for inspection. The default value is |
|
Network interface on which inspection dnsmasq will listen. The default value is |
|
Temporary IP range that will be given to nodes during the inspection process. This should not overlap with any range that OpenStack Networking (neutron) DHCP allocates, but it has to be routeable back to |
|
Kernel args for the OpenStack Bare Metal (ironic) inspector. The default value is |
|
Temporary IP ranges that will be given to nodes during the inspection process. These ranges should not overlap with any range that OpenStack Networking (neutron) DHCP provides, but they need to be routeable back to the |
|
Whether to use Swift for storing introspection data. The default value is |
|
The IP version that will be used for PXE booting. The default value is |
| The password for the Bare Metal service and database account. |
|
Name or UUID of the overcloud network used for provisioning of bare metal nodes if |
|
Name or UUID of the overcloud network used for resucing of bare metal nodes, if IronicDefaultRescueInterface is not set to "no-rescue". The default value of "provisioning" can be left during the initial deployment (when no networks are created yet) and should be changed to an actual UUID in a post-deployment stack update. The default value is |
| The remote procedure call transport between conductor and API processes, such as a messaging broker or JSON RPC. |