Ironic Release Notes - en to en_GB translation catalogue (28 entries)

en: "Choooooo! Choooooo!" The Train is now departing the station. The OpenStack Bare Metal as a service team is proud to announce the release of Ironic 13.0.0. This release brings the long desired feature of software RAID configuration, Redfish virtual media boot support, sensor data improvements, and numerous bug fixes. We hope you enjoy your ride on the OpenStack Ironic Train.
en_GB: "Choooooo! Choooooo!" The Train is now departing the station. The OpenStack Bare Metal as a service team is proud to announce the release of Ironic 13.0.0. This release brings the long-desired feature of software RAID configuration, Redfish virtual media boot support, sensor data improvements, and numerous bug fixes. We hope you enjoy your ride on the OpenStack Ironic Train.

en: A ``[DEFAULT]/enabled_network_interfaces`` option (which must be set for both ironic-api and ironic-conductor services) controls which network interfaces are available for use.
en_GB: A ``[DEFAULT]/enabled_network_interfaces`` option (which must be set for both Ironic-API and Ironic-conductor services) controls which network interfaces are available for use.

en: A bug was identified in the behavior of the iLO drivers where nodes that are not active but taking part of a conductor takeover could be powered off. In preparation for new features and functionality, that risk encountering this bug, we are limiting the deployment preparation steps to the ``deploying`` state to prevent nodes from being erroneously powered off.
en_GB: A bug was identified in the behaviour of the iLO drivers where nodes that are not active but taking part of a conductor takeover could be powered off. In preparation for new features and functionality, that risk encountering this bug, we are limiting the deployment preparation steps to the ``deploying`` state to prevent nodes from being erroneously powered off.

en: A new @passthru decorator was introduced to the driver API in a previous release. In this release, support for vendor_passthru and driver_vendor_passthru methods has been removed. All in-tree drivers have been updated. Any out of tree drivers which did not update to the @passthru decorator during the previous release will need to do so to be compatible with this release.
en_GB: A new @passthru decorator was introduced to the driver API in a previous release. In this release, support for vendor_passthru and driver_vendor_passthru methods has been removed. All in-tree drivers have been updated. Any out-of-tree drivers which did not update to the @passthru decorator during the previous release will need to do so to be compatible with this release.

en: A new class ``ironic.drivers.modules.agent.CustomAgentDeploy`` can be used as a base class for deploy interfaces based on ironic-python-agent.
en_GB: A new class ``ironic.drivers.modules.agent.CustomAgentDeploy`` can be used as a base class for deploying interfaces based on ironic-python-agent.

en: A new configuration option ``[deploy]continue_if_disk_secure_erase_fails``, which has a default value of False, has been added. The default setting represents the standard behavior of the Ironic Python Agent during a cleaning failure.
en_GB: A new configuration option ``[deploy]continue_if_disk_secure_erase_fails``, which has a default value of False, has been added. The default setting represents the standard behaviour of the Ironic Python Agent during a cleaning failure.

en: A node in the ``active`` provision state can be rescued via the ``GET /v1/nodes/{node_ident}/states/provision`` API, by specifying ``rescue`` as the ``target`` value, and a ``rescue_password`` value. When the node has been rescued, it will be in the ``rescue`` provision state. A rescue ramdisk will be running, configured with the specified ``rescue_password``, and listening with ssh on the tenant network.
en_GB: A node in the ``active`` provision state can be rescued via the ``GET /v1/nodes/{node_ident}/states/provision`` API, by specifying ``rescue`` as the ``target`` value, and a ``rescue_password`` value. When the node has been rescued, it will be in the ``rescue`` provision state. A rescue ramdisk will be running, configured with the specified ``rescue_password``, and listening with SSH on the tenant network.

en: Add Neutron ``port_setup_delay`` configuration option. This delay allows Ironic to wait for Neutron port operations until we have a mechanism for synchronizing events with Neutron. Set to 0 by default.
en_GB: Add Neutron ``port_setup_delay`` configuration option. This delay allows Ironic to wait for Neutron port operations until we have a mechanism for synchronising events with Neutron. Set to 0 by default.

en: Add Wake-On-Lan Power Driver
en_GB: Add Wake-On-LAN Power Driver

en: Add ``anaconda`` deploy interface to Ironic. This driver will deploy the OS using anaconda installer and kickstart file instead of IPA. To support this feature a new configuration group ``anaconda`` is added to Ironic configuration file along with ``default_ks_template`` configuration option.
en_GB: Add ``anaconda`` deploy interface to Ironic. This driver will deploy the OS using Anaconda installer and kickstart file instead of IPA. To support this feature a new configuration group ``anaconda`` is added to Ironic configuration file along with ``default_ks_template`` configuration option.

en: Add ``hctl`` to root device hints. HCTL is the SCSI address and stands for Host, Channel, Target and Lun.
en_GB: Add ``hctl`` to root device hints. HCTL is the SCSI address and stands for Host, Channel, Target and LUN.

en: Add support to SNMP driver for "APC MasterSwitchPlus" series PDU's
en_GB: Add support to SNMP driver for "APC MasterSwitchPlus" series PDUs

en: Addresses a condition where the Compute Service may have been unable to remove VIF attachment records while a baremetal node is being unprovisiond. This condition resulted in VIF records being orphaned, blocking future deployments without manual intervention. See `bug 1743652 <https://bugs.launchpad.net/ironic/+bug/1743652>`_ for more details.
en_GB: Addresses a condition where the Compute Service may have been unable to remove VIF attachment records while a baremetal node is being unprovisioned. This condition resulted in VIF records being orphaned, blocking future deployments without manual intervention. See `bug 1743652 <https://bugs.launchpad.net/ironic/+bug/1743652>`_ for more details.

en: Adds ``idrac`` hardware type support of a virtual media boot interface implementation that utilizes the Redfish out-of-band (OOB) management protocol and is compatible with the integrated Dell Remote Access Controller (iDRAC) baseboard management controller (BMC). It is named ``idrac-redfish-virtual-media``.
en_GB: Adds ``idrac`` hardware type support of a virtual media boot interface implementation that utilises the Redfish out-of-band (OOB) management protocol and is compatible with the integrated Dell Remote Access Controller (iDRAC) baseboard management controller (BMC). It is named ``idrac-redfish-virtual-media``.

en: Adds ``ilo-uefi-https`` boot interface to ``ilo5`` hardware type. This boot interface levereges the iLO UEFI firmware capability to boot from given HTTPS URLs hosted securely over HTTPS webserver with standard/custom certificates.
en_GB: Adds ``ilo-uefi-https`` boot interface to ``ilo5`` hardware type. This boot interface leverages the iLO UEFI firmware capability to boot from given HTTPS URLs hosted securely over HTTPS webserver with standard/custom certificates.

en: Adds ``is_allocation_owner`` policy rule, which can be applied to allocation get/update/delete rules. Also adds ``baremetal:allocation:list`` and ``baremetal:allocation:list_all`` rules for listing owned allocations and all allocations. Default rules are unaffected, so default behavior is unchanged.
en_GB: Adds ``is_allocation_owner`` policy rule, which can be applied to allocation get/update/delete rules. Also adds ``baremetal:allocation:list`` and ``baremetal:allocation:list_all`` rules for listing owned allocations and all allocations. Default rules are unaffected, so default behaviour is unchanged.

en: Adds a ``detect_vendor`` management interface method to the ``ipmi`` hardware type. This method is being promoted as a higher level interface as the fundimental need to be able to have logic aware of the hardware vendor is necessary with vendor agnostic drivers where slight differences require slightly different behavior.
en_GB: Adds a ``detect_vendor`` management interface method to the ``ipmi`` hardware type. This method is being promoted as a higher level interface as the fundamental need to be able to have logic aware of the hardware vendor is necessary with vendor agnostic drivers where slight differences require slightly different behaviour.

en: Adds a ``resource_class`` field to the node resource, which will be used by Nova to define which nodes may quantitatively match a Nova flavor. Operators should populate this accordingly before deploying the Ocata version of Nova.
en_GB: Adds a ``resource_class`` field to the node resource, which will be used by Nova to define which nodes may quantitatively match a Nova flavour. Operators should populate this accordingly before deploying the Ocata version of Nova.

en: Adds a ``traits`` field to the node resource, which will be used by the Compute service to define which nodes may match a Compute flavor using qualitative attributes.
en_GB: Adds a ``traits`` field to the node resource, which will be used by the Compute service to define which nodes may match a Compute flavour using qualitative attributes.

en: Adds a boolean flag called ``force_persistent_boot_device`` into a node's ``driver_info`` to enable persistent behavior when you set the boot device during deploy and cleaning operations. This flag will override a non-persistent behavior in the cleaning and deploy process. For more information, see https://bugs.launchpad.net/ironic/+bug/1703945.
en_GB: Adds a boolean flag called ``force_persistent_boot_device`` into a node's ``driver_info`` to enable persistent behaviour when you set the boot device during deploy and cleaning operations. This flag will override a non-persistent behaviour in the cleaning and deploy process. For more information, see https://bugs.launchpad.net/ironic/+bug/1703945.

en: Adds a check to the ``ironic-status upgrade check`` command, to check for compatibility of the object versions with the release of ironic.
en_GB: Adds a check to the ``ironic-status upgrade check`` command, to check for compatibility of the object versions with the release of Ironic.

en: Adds a configuration section ``cinder`` and a requirement of cinder client (python-cinderclient).
en_GB: Adds a configuration section ``cinder`` and a requirement of Cinder client (python-cinderclient).

en: Adds a new ``ansible`` deploy interface. It targets mostly undercloud use-case by allowing greater customization of provisioning process.
en_GB: Adds a new ``ansible`` deploy interface. It targets mostly undercloud use-case by allowing greater customisation of provisioning process.

en: Adds a new configuration option ``[pxe]pxe_config_subdir`` to allow operators to define the specific directory that may be used inside of ``/tftpboot`` or ``/httpboot`` for a boot loader to locate the configuration file for the node. This option defaults to ``pxelinux.cfg`` which is the directory that the Syslinux `pxelinux.0` bootloader utilized. Operators may wish to change the directory name if they are using other boot loaders such as `GRUB` or `iPXE`.
en_GB: Adds a new configuration option ``[pxe]pxe_config_subdir`` to allow operators to define the specific directory that may be used inside of ``/tftpboot`` or ``/httpboot`` for a boot loader to locate the configuration file for the node. This option defaults to ``pxelinux.cfg`` which is the directory that the Syslinux `pxelinux.0` bootloader utilised. Operators may wish to change the directory name if they are using other boot loaders such as `GRUB` or `iPXE`.

en: Beginning with API v1.11, newly created Nodes begin in the ENROLL state, and must be "managed" and "provided" before they are made available for provisioning. API clients must be updated to handle the new workflow when they begin sending the X-OpenStack-Ironic-API-Version header with a value >= 1.11.
en_GB: Beginning with API v1.11, newly created Nodes begin in the ENROLL state and must be "managed" and "provided" before they are made available for provisioning. API clients must be updated to handle the new workflow when they begin sending the X-OpenStack-Ironic-API-Version header with a value >= 1.11.

en: Out of tree drivers may be broken by this release. The AgentDeploy and ISCSIDeploy (formerly known as PXEDeploy) classes now depend on drivers to utilize an instance of a BootInterface. For drivers that exist out of tree, that use these deploy classes, an error will be thrown during deployment. There is a simple fix. For drivers that expect these deploy classes to handle PXE booting, one can add the following code to the driver's `__init__` method::
en_GB: Out-of-tree drivers may be broken by this release. The AgentDeploy and ISCSIDeploy (formerly known as PXEDeploy) classes now depend on drivers to utilize an instance of a BootInterface. For drivers that exist out-of-tree, that use these deploy classes, an error will be thrown during deployment. There is a simple fix. For drivers that expect these deploy classes to handle PXE booting, one can add the following code to the driver's `__init__` method::

en: The Ironic team apologizes profusely for this inconvenience.
en_GB: The Ironic team apologises profusely for this inconvenience.

en: This is the first semver-versioned release of Ironic, created during the OpenStack "Liberty" development cycle.  It marks a pivot in our versioning schema from date-based versioning; the previous released version was 2015.1. Full release details are available on Launchpad: https://launchpad.net/ironic/liberty/4.0.0.
en_GB: This is the first semver-versioned release of Ironic, created during the OpenStack "Liberty" development cycle.  It marks a pivot in our versioning schema from date-based versioning; the previously released version was 2015.1. Full release details are available on Launchpad: https://launchpad.net/ironic/liberty/4.0.0.
