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

en: A database migration is required to change some columns from Float to DateTime type. This may take some time based on the number of introspection statuses in DB.
en_GB: A database migration is required to change some columns from Float to DateTime type. This may take some time based on the number of introspection statuses in the DB.

en: Added CORS support middleware to Ironic Inspector, allowing a deployer to optionally configure rules under which a javascript client may break the single-origin policy and access the API directly.
en_GB: Added CORS support middleware to Ironic Inspector, allowing a deployer to optionally configure rules under which a JavaScript client may break the single-origin policy and access the API directly.

en: Adds dependency on the `retrying <https://github.com/rholder/retrying>`_ python library.
en_GB: Adds dependency on the `retrying <https://github.com/rholder/retrying>`_ Python library.

en: Adds support for filter by state in the list introspection API. See `story 1625183 <https://storyboard.openstack.org/#!/story/1625183>`_.
en_GB: Adds support for filtering by state in the list introspection API. See `story 1625183 <https://storyboard.openstack.org/#!/story/1625183>`_.

en: Adds the ability for periodic clean-up and synchronization tasks with ``ironic`` to be able to be disabled by setting the ``[DEFAULT]clean_up_period`` to a value of ``0``. This is intended for "stand-alone" operators only as it may result in unexpected behaviors if used in a non-standalone environment.
en_GB: Adds the ability for periodic clean-up and synchronization tasks with ``ironic`` to be able to be disabled by setting the ``[DEFAULT]clean_up_period`` to a value of ``0``. This is intended for "stand-alone" operators only as it may result in unexpected behaviours if used in a non-standalone environment.

en: Allows splitting the ironic-inspector service into ironic-inspector-api and ironic-inspector-conductor which coordinate via tooz and its underlying backend. A new configuration option ``[DEFAULT]standalone`` is introduced to enable this feature. The configuration defaults to True, and ironic-inspector runs as a single service, which is compatible with the old behavior. When set to False, ``ironic-inspector-api-wsgi`` is used to start the API service, and ``ironic-inspector-conductor`` is used to start the conductor service. For ironic-inspector running in non-standalone mode, the user needs to set the new configuration option ``[coordination]backend_url``, which specifies the backend used for coordination.
en_GB: Allows splitting the ironic-inspector service into ironic-inspector-api and ironic-inspector-conductor which coordinate via Tooz and its underlying backend. A new configuration option ``[DEFAULT]standalone`` is introduced to enable this feature. The configuration defaults to True, and ironic-inspector runs as a single service, which is compatible with the old behaviour. When set to False, ``ironic-inspector-api-wsgi`` is used to start the API service, and ``ironic-inspector-conductor`` is used to start the conductor service. For ironic-inspector running in non-standalone mode, the user needs to set the new configuration option ``[coordination]backend_url``, which specifies the backend used for coordination.

en: By default the DHCP filtering will open the DHCP server for any node when introspection is active. It will only block DHCP for enrolled nodes that are not being introspected. Doing so is required to support interface discovery (which by default will enroll the pxe port to ironic if not present). This behaviour is not always wanted, as nodes not managed by ironic may boot the inspection image.
en_GB: By default the DHCP filtering will open the DHCP server for any node when introspection is active. It will only block DHCP for enrolled nodes that are not being introspected. Doing so is required to support interface discovery (which by default will enrol the PXE port to Ironic if not present). This behaviour is not always wanted, as nodes not managed by Ironic may boot the inspection image.

en: Deprecates the configuration option ``[processing]store_data_location``. The introspection data can be retrieved from the ironic-inspector API, there is no need to keep an extra link in ironic.
en_GB: Deprecates the configuration option ``[processing]store_data_location``. The introspection data can be retrieved from the ironic-inspector API, there is no need to keep an extra link in Ironic.

en: Don't fail on finish power off if node in 'enroll' state. Nodes in 'enroll' state are not expected to have power credentials.
en_GB: Don't fail on finish power off if node in 'enrol' state. Nodes in 'enrol' state are not expected to have power credentials.

en: Fixes an issue during manual inspection of active nodes where the node uuid was not passed back to the inspector when it tried to identify a matching port.
en_GB: Fixes an issue during manual inspection of active nodes where the node UUID was not passed back to the inspector when it tried to identify a matching port.

en: Fixes bug in which the ``switch_id`` field in a port's ``local_link_connection`` can be set to a non-MAC address if the processed LLDP has a value other than a MAC address for ``ChassisID``. The bare metal API requires the ``switch_id`` field to be a MAC address, and will return an error otherwise. See `bug 1748022 <https://bugs.launchpad.net/ironic-inspector/+bug/1748022>`_ for details.
en_GB: Fixes bug in which the ``switch_id`` field in a port's ``local_link_connection`` can be set to a non-MAC address if the processed LLDP has a value other than a MAC address for ``ChassisID``. The Bare Metal API requires the ``switch_id`` field to be a MAC address, and will return an error otherwise. See `bug 1748022 <https://bugs.launchpad.net/ironic-inspector/+bug/1748022>`_ for details.

en: Follow the same process for determining root device as Ironic Python Agent which has been changed to accommodate for the feature enabling users to specify a list of devices that should be skipped during cleaning/deployment The field ``skip_block_devices`` is one of the properties of a node
en_GB: Follow the same process for determining the root device as Ironic Python Agent which has been changed to accommodate for the feature enabling users to specify a list of devices that should be skipped during cleaning/deployment The field ``skip_block_devices`` is one of the properties of a node

en: Inspector now ignores failures to list ironic ports during pxe filter driver sync, and just skips the sync in this case. Previously such errors resulted in pxe filter driver being stuck in an uninitialized state until ironic inspector was restarted. See bug `2008971 <https://storyboard.openstack.org/#!/story/2008971>`_.
en_GB: Inspector now ignores failures to list ironic ports during PXE filter driver sync, and just skips the sync in this case. Previously such errors resulted in the PXE filter driver being stuck in an uninitialized state until Ironic inspector was restarted. See bug `2008971 <https://storyboard.openstack.org/#!/story/2008971>`_.

en: Only issue iptables calls when list of active MAC's changes.
en_GB: Only issue iptables calls when list of active MAC addresses changes.

en: Plugin maintainers should be aware that the Node Cache object field ``version_id`` filed is no longer in use. It is still returned by the data model if stored for the purposes of compatibility, but Inspector will not update the field through the normal course of it's operation.
en_GB: Plugin maintainers should be aware that the Node Cache object field ``version_id`` filed is no longer in use. It is still returned by the data model if stored for the purposes of compatibility, but Inspector will not update the field through the normal course of its operation.

en: Plugin maintainers who are directly working with the database will need to update their plugins. Specifically the Database API has been delineated into using ``enginefacade`` with a dedicated reader and writer model, in anticipation of support for SQLAlchemy 2.0 and an eventual merge of Inspector into Ironic at some point in the future. Database actions are now performed through the ``ironic_inspector.db.api`` module, where previously they were spread across ``ironic_inspector.db`` and ``ironic_inspector.node_cache``.
en_GB: Plugin maintainers who are directly working with the database will need to update their plugins. Specifically, the Database API has been delineated into using ``enginefacade`` with a dedicated reader and writer model, in anticipation of support for SQLAlchemy 2.0 and an eventual merge of Inspector into Ironic at some point in the future. Database actions are now performed through the ``ironic_inspector.db.api`` module, where previously they were spread across ``ironic_inspector.db`` and ``ironic_inspector.node_cache``.

en: Remove upper constraint for python construct library and use the latest version available. The minimum compatible version for python construct is now 2.9.39
en_GB: Remove upper constraint for Python construct library and use the latest version available. The minimum compatible version for Python construct is now 2.9.39

en: Set the node to the error state when it failed get data from swift.
en_GB: Set the node to the error state when it failed get data from Swift.

en: Several configuration options related to swift API access are deprecated and will be removed in Rocky release. These include:
en_GB: Several configuration options related to Swift API access are deprecated and will be removed in Rocky release. These include:

en: Start using reno to manage release notes.
en_GB: Start using Reno to manage release notes.

en: The default API version was synchronized with the current API version again after removal of the IPMI credentials setting.
en_GB: The default API version was synchronised with the current API version again after removal of the IPMI credentials setting.

en: The default policy will been replaced with one which aligns with the Secure-RBAC scopes and roles. Since ironic-inspector is a tool used only by system-level admins, only the ``system`` scope is supported, and the only roles in the policy rules are ``admin`` and ``reader``.
en_GB: The default policy will be replaced with one which aligns with the Secure-RBAC scopes and roles. Since ironic-inspector is a tool used only by system-level admins, only the ``system`` scope is supported, and the only roles in the policy rules are ``admin`` and ``reader``.

en: The devstack plugin for ``ironic-inspector`` has been changed to utilize pre-built ``ironic-python-agent`` images based on Centos8 instead of legacy CoreOS based images.
en_GB: The devstack plugin for ``ironic-inspector`` has been changed to utilise pre-built ``ironic-python-agent`` images based on Centos8 instead of legacy CoreOS based images.

en: The introspection start API is now synchronous when ``manage_boot==False``. This means that any failures will be propagated to ironic, preventing it from powering a node on and booting it without the PXE filter updated.
en_GB: The introspection start API is now synchronous when ``manage_boot==False``. This means that any failures will be propagated to Ironic, preventing it from powering a node on and booting it without the PXE filter updated.

en: The new ``[healthcheck] enabled`` option has been added. When this option is set to ``True``, the healthcheck middleware is enabled in API pipeline and the additional API endpoint to monitor service availability becomes available at ``/healthcheck`` path.
en_GB: The new ``[healthcheck] enabled`` option has been added. When this option is set to ``True``, the healthcheck middleware is enabled in the API pipeline and the additional API endpoint to monitor service availability becomes available at ``/healthcheck`` path.

en: The only password digest supported is bcrypt, and the ``bcrypt`` python library is used for password checks since it supports ``$2y$`` prefixed bcrypt passwords as generated by the Apache htpasswd utility.
en_GB: The only password digest supported is bcrypt, and the ``bcrypt`` Python library is used for password checks since it supports ``$2y$`` prefixed bcrypt passwords as generated by the Apache htpasswd utility.

en: The previous behavior can be returned by setting the new option ``[extra_hardware]strict`` to ``True``.
en_GB: The previous behaviour can be returned by setting the new option ``[extra_hardware]strict`` to ``True``.

en: The python-ironicclient package has been removed as a dependency in favor of openstacksdk. Third party modules and plugins will require an update if they previously invoked ironicclient.
en_GB: The python-ironicclient package has been removed as a dependency in favour of openstacksdk. Third party modules and plugins will require an update if they previously invoked ironicclient.

en: Use of legacy policy files was deprecated by the ``oslo.policy`` library during the Victoria development cycle. As a result, this deprecation is being noted in the Wallaby with an anticipated future removal of support by ``oslo.policy``. As such operators will need to convert to YAML policy files. Please see the upgrade notes for details on migration of any custom policy files.
en_GB: The use of legacy policy files was deprecated by the ``oslo.policy`` library during the Victoria development cycle. As a result, this deprecation is being noted in the Wallaby with an anticipated future removal of support by ``oslo.policy``. As such operators will need to convert to YAML policy files. Please see the upgrade notes for details on the migration of any custom policy files.

en: ``[ironic]/ironic_url`` - use ``[ironic]/endpoint_override`` option to set specific ironic API endpoint address if discovery of ironic API endpoint is not desired or impossible (for example in standalone mode)
en_GB: ``[ironic]/ironic_url`` - use ``[ironic]/endpoint_override`` option to set specific ironic API endpoint address if discovery of Ironic API endpoint is not desired or impossible (for example in standalone mode)

en: ``[ironic]/os_endpoint_type`` - use ``[ironic]/valid_interfaces`` option to set ironic endpoint types that will be attempted to be used
en_GB: ``[ironic]/os_endpoint_type`` - use ``[ironic]/valid_interfaces`` option to set Ironic endpoint types that will be attempted to be used
