Zed Series Release Notes

18.0.0.0b1-202

New Features

  • New variables have been added to allow a deployer to enable iPXE support for Ironic Conductor, which uses HTTP rather than TFTP, and can speed up baremetal provisioning considerably. To enable, simply set the ironic_ipxe_enabled override to True.

  • UEFI boot support has been added. To migrate from Legacy BIOS mode, define boot_mode:uefi as a capability for baremetal nodes that support UEFI. In addition, corresponding flavor(s) will need to be created or modified to include boot_mode:uefi as a capability for scheduling to occur against UEFI nodes.

  • The os_ironic ansible role can now upload the ironic deploy image to glance. Several new variables are defined as ironic_deploy_image_* which control this. It is possible to disable the upload to glance and also to specify custom locations to stage the images from if required.

  • The service setup in keystone for ironic will now be executed through delegation to the ironic_service_setup_host which, by default, is localhost (the deploy host). Deployers can opt to rather change this to the utility container by implementing the following override in user_variables.yml.

    ironic_service_setup_host: "{{ groups['utility_all'][0] }}"

  • Support separate oslo.messaging services for RPC and Notifications to enable operation of separate and different messaging backend servers in ironic.

Upgrade Notes

  • The variables ironic_inspector_ipa_initrd_name and ironic_inspector_ipa_initrd_name are removed from the os_ironic role and more flexible functionality is now provided with the ironic_deplo_image_* variables. Review any overrides you have for the ironic service and adjust these new variables if necessary.

Deprecation Notes

  • The pxe_append_params configuration option has been deprecated by Ironic and replaced with kernel_append_params. The corresponding configuration override, ironic_pxe_append_params, has been replaced by ironic_kernel_append_params but will continue to be supported until a future undetermined release.

  • The variable ironic_requires_pip_packages is no longer required and has therefore been removed.

  • The rabbitmq server parameters have been replaced by corresponding oslo.messaging RPC and Notify parameters in order to abstract the messaging service from the actual backend server deployment. - ironic_oslomsg_rpc_servers replaces ironic_rabbitmq_servers - ironic_oslomsg_rpc_port replaces ironic_rabbitmq_port - ironic_oslomsg_rpc_use_ssl replaces ironic_rabbitmq_use_ssl - ironic_oslomsg_rpc_userid replaces ironic_rabbitmq_userid - ironic_oslomsg_rpc_vhost replaces ironic_rabbitmq_vhost

16.0.0.0b2

New Features

  • New variables have been added to allow a deployer to customize a ironic systemd unit file to their liking.

  • The task dropping the ironic systemd unit files now uses the config_template action plugin allowing deployers access to customize the unit files as they see fit without having to load extra options into the defaults and pollute the generic systemd unit file with jinja2 variables and conditionals.

  • For the os_ironic role, the systemd unit TimeoutSec value which controls the time between sending a SIGTERM signal and a SIGKILL signal when stopping or restarting the service has been reduced from 300 seconds to 120 seconds. This provides 2 minutes for long-lived sessions to drain while preventing new ones from starting before a restart or a stop. The RestartSec value which controls the time between the service stop and start when restarting has been reduced from 150 seconds to 2 seconds to make the restart happen faster. These values can be adjusted by using the ironic_*_init_config_overrides variables which use the config_template task to change template defaults.

Upgrade Notes

  • For the os_ironic role, the systemd unit TimeoutSec value which controls the time between sending a SIGTERM signal and a SIGKILL signal when stopping or restarting the service has been reduced from 300 seconds to 120 seconds. This provides 2 minutes for long-lived sessions to drain while preventing new ones from starting before a restart or a stop. The RestartSec value which controls the time between the service stop and start when restarting has been reduced from 150 seconds to 2 seconds to make the restart happen faster. These values can be adjusted by using the ironic_*_init_config_overrides variables which use the config_template task to change template defaults.

16.0.0.0b1

New Features

  • Capping the default value for the variable ironic_wsgi_processes to 16 when the user doesn’t configure this variable. Default value is one fourth the number of vCPUs available on the machine with a capping value of 16.

15.0.0.0rc1

New Features

  • Added support for ironic-OneView drivers. Check the documentation on how to enable them.

15.0.0.0b2

New Features

  • Add support for neutron as an enabled_network_interface.

  • The ironic_neutron_provisioning_network_name and ironic_neutron_cleaning_network_name variable can be set to the name of the neutron network to use for provisioning and cleaning. The ansible tasks will determine the appropriate UUID for that network. Alternatively, ironic_neutron_provisioning_network_uuid or ironic_neutron_cleaning_network can be used to directly specify the UUID of the networks. If both ironic_neutron_provisioning_network_name and ironic_neutron_provisioning_network_uuid are specified, the specified UUID will be used. If only the provisioning network is specified, the cleaning network will default to the same network.

15.0.0.0b1

Upgrade Notes

  • The variables ironic_requirements_git_repo and ironic_requirements_git_install_branch have been removed in favour of using the URL/path to the upper-constraints file using the variable pip_install_upper_constraints instead.

14.0.0.0b3

New Features

  • The os_ironic role now supports the ability to configure whether apt/yum tasks install the latest available package, or just ensure that the package is present. The default action is to ensure that the latest package is present. The action taken may be changed to only ensure that the package is present by setting ironic_package_state to present.

Upgrade Notes

  • The variable ironic_api_apt_packages has been renamed to ironic_api_distro_packages.

  • The variable ironic_conductor_apt_packages has been renamed to ironic_conductor_distro_packages.

  • The variable ironic_conductor_standalone_apt_packages has been renamed to ironic_conductor_standalone_distro_packages.

  • The os_ironic role always checks whether the latest package is installed when executed. If a deployer wishes to change the check to only validate the presence of the package, the option ironic_package_state should be set to present.

14.0.0.0b2

New Features

  • The ironic role now supports Ubuntu 16.04 and SystemD.

Upgrade Notes

  • Installation of ironic and its dependent pip packages will now only occur within a Python virtual environment. The ironic_venv_bin and ironic_venv_enabled variables have been removed.