Wallaby Series Release Notes

18.7.0-8

New Features

  • The pxe parameter uefi_pxe_bootfile_name is now managed by puppet, keeping the ironic default of bootx64.efi.

    The shim EFI binary is copied to the TFTP root directory, to a file named the value of uefi_pxe_bootfile_name. The grub EFI binary is copied to the TFTP root directory to a file named grubx64.efi.

    With these changes, using the pxe boot driver with UEFI boot will result in a grub network boot which is Secure Boot capable.

Bug Fixes

  • Now the ironic::pxe class properly installs the pxelinux.0 file using the separate pxelinux package in Debian and Ubuntu. The new pxelinux_file_path parameter can be used to determine the source path to locate the file. When this parameter is set to false then the class does not manage the file.

  • The wrong source directory to copy syslinux files in Debiand or Ubuntu has been fixed.

18.7.0

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.

Bug Fixes

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

18.6.0

New Features

  • 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::policy class has been added to support policy settings for ironic-inspector.

  • 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.

  • 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.

18.5.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.

  • 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

  • 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.

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.

18.4.0

New Features

  • The new ironic::healthcheck class has been added. This class manages parameters of healthcheck middlware in oslo.middleware.

  • The new ironic::policy::enforce_scope parameter has been added to support the corresponding parameter in oslo.policy library.

  • The new ironic::policy::enforce_new_defaults parameter has been added.

18.2.0

Upgrade Notes

  • Now policy.yaml is used by default instead of policy.json.

18.1.0

New Features

  • Adds db_sync_timeout parameter to db sync.

  • The following parameters have been added to the ironic::driver::ipmi class.

    • use_ipmitool_retries

    • kill_on_timeout

    • disable_boot_timeout

  • The following two parameters have been added to configure the service_type parameter in authtoken middlewae.

    • ironic::api::authtoken::service_type

    • ironic::inspector::authtoken::service_type

  • The ironic::driver::redfish class now supports the following two parameters to set the polling intervals for the firmware update feature in redfish driver.

    • firmware_update_status_interval

    • firmware_update_fail_interval

Deprecation Notes

  • allow_insecure_clients option is now deprecated for removal, the parameter has no effect.

  • The following options have been deprecated, as those options have been moved to ironic::db class.

    • ironic::database_connection

    • ironic::database_idle_timeout

    • ironic::database_max_overflow

    • ironic::database_max_pool_size

    • ironic::database_max_retries

    • ironic::database_retry_interval

  • The ironic::database_reconnect_interval parameter has been deprecated and now has no effect.

  • The ironic::inspector::db_connection parameter has been deprecated. Use the ironic::inspector::db::database_connection parameter instead.

18.0.0

Upgrade Notes

  • Compatibility with el7 (RHEL7.x, CentOS7.x and so on) has been removed.