Xena Series Release Notes

19.4.0-15

New Features

  • The ironic::conductor class now supports the following two new parameters.

    • heartbeat_interval

    • heartbeat_timeout

  • The new ironic::disk_utils class has been added.

  • The new ironic::pxe::tftp_use_xinetd parameter has been added. When this parameter is set to false, the ironic-dnsmasq-tftp-server service, which actually manages a dnsmasq process, is used instead of xinetd, to implement TFTP server. Note that the dnsmasq service is currently available only in RDO.

Bug Fixes

  • Fixed an issue where dnsmasq DHCP configuration for ironic- inspector would point to the wrong UEFI iPXE bootfile. See bug: 1952652.

  • Now the tftpd-hap package is installed insted of the tftpd package in Debian and Ubuntu.

19.4.0

New Features

  • The new ironic::logging::watch_log_file parameter has been added. The new ironic::inspector::logging::watch_log_file parameter has been added.

  • It is now possible to disable sequential ip addressing in the ironic inspector dnsmasq service. The ironic::inspector class has the new parameter dnsmasq_dhcp_sequential_ip (defaults to: true). Set it to false to disable sequential ip addressing.

  • The new ironic::inspector::healthcheck class has been added.

  • Adds new purge_config parameter. When set to true, the policy file is cleared during configuration process. This allows to remove any existing rules before applying them or clean the file when all policies got removed.

Deprecation Notes

  • The ironic::drivers::pxe::pxe_append_params parameter has been deprecated in favor of the new kernel_append_params parameter.

19.3.0

New Features

  • Expose the sync_power_state_workers in ironic::conductor.

  • The new ironic::inspector::policy class has been added to support policy settings for ironic-inspector.

  • New class ironic::json_rpc to set parameters for configuring json-rpc has been added. Please set credentials for json-rpc using this class.

  • The new ironic::pxe::uefi_ipxe_bootfile_name parameter has been added. This parameter is used to determine name of the efi file used to boot nodes with UEFI + iPXE.

Upgrade Notes

  • An explict ironic enabled_hardware_types setting has been removed from puppet-ironic as it matches the Ironic default and the default override prohibits inclusion of additional default enabled hardware types the OpenStack Ironic project may choose to ship in the future.

Deprecation Notes

  • The ironic_api_paste_ini resource type has been deprecated and will be removed in a future release.

  • The ironic::config::ironic_api_paste_ini parameter has been deprecated and has no effect now. This parameter will be removed in a future release.

  • Deprecates integration for Ironic’s Bifrost sub-project.

    Bifrost serves a similar purpose as puppet-ironic, in so much as the embedded configuration lags behind and ultimately is no longer appropriate for a bifrost deployment. If you wish to deploy bifrost, please make use of the bifrost-cli tool or Ansible playbooks noted in Bifrost’s documentation.

Bug Fixes

  • Fixes support for ppc64le to allow its operation to co-exist with pxe_transfer_protocol being set to http. This is because the ppc64le archtecture does not use an intermediate boot loader to perform PXE operations, and only supports use of TFTP based transfers.

19.1.0

New Features

  • Adds support for the ironic.conf parameters [pxe]ipxe_bootfile_name and [pxe]ipxe_config_template which are utilized by the ipxe boot interface in Ironic. These settings use the manifest parameters ironic::drivers::pxe::ipxe_bootfile_name and ironic::drivers::pxe::ipxe_config_template respectively.

  • Adds support for the ironic.conf parameter [pxe]uefi_ipxe_bootfile_name to be explicitly set using the ironic::drivers::pxe::uefi_ipxe_bootfile_name manifest parameter, however this value is defaulted to snponly.efi which is anticipated to become the default in Ironic sometime in the Xena development cycle.

Upgrade Notes

  • Fedora is no longer supported.

  • The Ironic project has in elevated support for ipxe to a top level node boot_interface, and removed support for it’s [pxe]ipxe_enabled option as this is settable per node. Removal of this option has allowed for the manifest to be cleaned up.

  • The manifest now no longer applies override defaults for a number of ironic.conf settings, as they match the default settings the project utilizes. These manifest parameters are ironic::drivers::pxe::pxe_bootfile_name, ironic::drivers::pxe::pxe_config_template, ironic::drivers::pxe::tftp_root, ironic::drivers::pxe::tftp_master_path.

Deprecation Notes

  • The ironic::drivers::pxe::ipxe_enabled parameter has been deprecated and has no effect moving forward. This is a result of the underlying Ironic project deprecating and removing. Use of this option will raise a warning.

  • The ironic::drivers::pxe::ip_version parameter has been deprecated for removal. Please anticipate this option to be removed in a future release. This option has been redundant since the Ussuri release of Ironic. Use of this option raises a warning.

Bug Fixes

  • Fixes a potential issue where use of the ironic::drivers::pxe::ipxe_enabled parameter would cause settings specific to ipxe to be set overriding the pxe boot interface’s defaults in Ironic. This resulted in operators being unable to choose to boot a node from pxe and not ipxe. Now the settings are not overriden as the ironic::drivers::pxe::ipxe_enabled parameter for the manifest has no effect, and raises a warning if used.

19.0.0

New Features

  • Support for the audit middleware options has been added.

  • There is now a new policy_dirs parameter in the ironic::policy class, so one can set a custom path.

Bug Fixes

  • Removing max_time_interval because it’s been deprecated for a year now and it’s not used in any projects since 2013.