Ironic Conductor

Learn about configurations >

• action-managed-upgrade | boolean

  If True enables openstack upgrades for this charm via juju actions. You will still need to set openstack-origin to the new repository but instead of an upgrade running automatically across all units, it will wait for you to execute the openstack-upgrade action for this charm on each unit. If False it will revert to existing behavior of upgrading all units on config change.

• automated-cleaning | boolean

  Default: True

  Globally enables automated cleaning of nodes. This is run when setting a node to available state, or when deleting an instance. Cleaning will bring the node in a baseline state. You can safely disable this feature if all tenants of your OpenStack deployment are trusted, or if you have a single tenant.

  Note: Automated cleaning can be toggled on a per node basis, via node properties. Note: node cleaning may take a long time, especially if secure erase is enabled.

• cleaning-network | string

  The name or ID of the cleaning network. This network is used to clean bare metal nodes after they have been releases. This option is mandatory to allow Neutron network interfaces. The same network may be used for both cleaning and provisioning.

• database | string

  Default: ironic

  Database name for Ironic

• database-user | string

  Default: ironic

  Username for Ironic database access

• debug | boolean

  Enable debug logging

• default-deploy-interface | string

  Default: direct

  The default deploy interface to use for nodes that do not explicitly set a deploy interface.

• default-network-interface | string

  Default: flat

  The default network interface to use for nodes that do not explicitly set a network interface type. The default network interface specified here, must also exist in the list of enabled-network-interfaces.

• disable-secure-erase | boolean

  This will disable secure erase in Ironic, when releasing a node. An ATA Secure Erase will be attempted. If it's not supported, the disks will be shreaded by writting random data to them once, then overwriting that data with zeros.

  Enabling this option will preserve the data on disk after release (not recommended for production).

• enabled-deploy-interfaces | string

  Default: direct

  Comma separated list of deploy interfaces to use. Valid options are:

  • direct
  • iscsi

  Note: To enable the direct deploy interface, the following conditions must be met in your deployment of OpenStack:

  • ceph-radosgw or swift is deployed and available
  • glance is deployed and has a relation set to ceph-radosgw or swift
  • You ran the set-temp-url-secret action of this charm If any of these conditions are not met, the direct deploy interface will not be enabled in the config, and the charm will go into blocked state.

  Note: The iscsi deploy mode requires that ironic-conductor be deployed on a VM or a bare metal machine. That is because the iscsi kernel module is not namespaced, and the ironic-conductor will not be able to log into any iscsi target.

  Note: The iscsi deploy interface is removed from the Ironic project in OpenStack Xena. Support for the iscsi deploy interface is therefore removed from the charm For OpenStack Xena and later releases.

• enabled-hw-types | string

  Default: ipmi

  Comma separated list of hardware types to enable. Valid options are:

  • ipmi
  • redfish
  • idrac

• enabled-network-interfaces | string

  Default: flat, neutron, noop

  Comma separated list of network interfaces to be enabled in the Ironic config. Valid options are:

  • flat
  • neutron
  • noop

  Note: When enabling "neutron", you will also have to set the provisioning-network and the cleaning-network options. The settings for these networks can be overwritten per node, but they need to be set globally for ironic to start. The "neutron" network interface is needed if you require additional enablement from a ml2 driver you may have enabled in your deployment, such as switch configuration.

• hardware-enablement-options | string

  Options passed to the managed service to set configuration keys that enable the use of specific hardware.

• ipxe-http-port | string

  Default: 8080

  The port used for the HTTP server used to serve iPXE resources.

• max-tftp-block-size | int

  Force TFTP server maximum block size. Setting this option to anything other than 0, will force the block size sent over TFTP to the value specified here. Valid range is 512-65535. By default, clients will negotiate the block size.

  Use this option if you're running ironic in a network with lower MTU. The value of this option should be 32 bits less than the MTU. If your MTU is 1450, the value for this option should be 1418.

• openstack-origin | string

  Default: yoga

  Repository from which to install. May be one of the following: distro (default), ppa:somecustom/ppa, a deb url sources entry, or a supported Ubuntu Cloud Archive e.g. . cloud:<series>-<openstack-release> cloud:<series>-<openstack-release>/updates cloud:<series>-<openstack-release>/staging cloud:<series>-<openstack-release>/proposed . See https://wiki.ubuntu.com/OpenStack/CloudArchive for info on which cloud archives are available and supported.

• provisioning-network | string

  The name or ID of the provisioning network. This network is used to deploy bare metal nodes. This option is mandatory to allow Neutron network interfaces.

• pxe-append-params | string

  Default: nofb nomodeset vga=normal console=tty0 console=ttyS0,115200n8

  Kernel command line parameters to pass to the deployment kernel. Options must be space delimited and will be passed as is to the deployment image. Aside from regular linux kernel command line parameters, you can also configure the ironic python agent (IPA) from within the deployment image. See the IPA documentation for a list of command line parameters which can be passed via pxe_append_params.

• rabbit-user | string

  Default: ironic

  Username used to access rabbitmq queue

• rabbit-vhost | string

  Default: openstack

  Rabbitmq vhost

• region | string

  Default: RegionOne

  OpenStack Region

• ssl_ca | string

  TLS CA to use to communicate with other components in a deployment. . NOTE: This configuration option will take precedence over any certificates received over the certificates relation.

• ssl_cert | string

  TLS certificate to install and use for any listening services. . NOTE: This configuration option will take precedence over any certificates received over the certificates relation.

• ssl_key | string

  TLS key to use with certificate specified as ssl_cert. . NOTE: This configuration option will take precedence over any certificates received over the certificates relation.

• swift-temp-url-duration | int

  The length of time (in seconds) that the temporary URL will be valid for. Defaults to 20 minutes. If some deploys get a 401 response code when trying to download from the temporary URL, try raising this duration.

• use-internal-endpoints | boolean

  Openstack mostly defaults to using public endpoints for internal communication between services. If set to True this option will configure services to use internal endpoints where possible.

• use-ipmitool-retries | boolean

  Use ipmitool to do the retries by passing relevant parameters. By default the option is set to False and in this case Ironic will do the retries by re-running ipmi commands.

• use-ipxe | boolean

  Default: True

  Use iPXE instead of PXE. This option will install an aditional HTTP server with a root in /httpboot.

• use-syslog | boolean

  Setting this to True will allow supporting services to log to syslog.

• verbose | boolean

  Enable verbose logging