From b8b1991bea20bb34075cb9295b16256cf0dabc95 Mon Sep 17 00:00:00 2001 From: Dmitry Tantsur Date: Thu, 3 Feb 2022 14:49:36 +0100 Subject: Clean up release notes Change-Id: I568d7edfe81e928e6d7f09bd4a7933ca72b8813a --- ...add_burnin_dynamic_network_pairing-33e398255050eb98.yaml | 13 +++++++------ .../notes/move_swraid_to_efibootmgr-d87c1bfde1661fb5.yaml | 8 ++++---- 2 files changed, 11 insertions(+), 10 deletions(-) diff --git a/releasenotes/notes/add_burnin_dynamic_network_pairing-33e398255050eb98.yaml b/releasenotes/notes/add_burnin_dynamic_network_pairing-33e398255050eb98.yaml index 1802f7ec..f4aaa203 100644 --- a/releasenotes/notes/add_burnin_dynamic_network_pairing-33e398255050eb98.yaml +++ b/releasenotes/notes/add_burnin_dynamic_network_pairing-33e398255050eb98.yaml @@ -3,15 +3,16 @@ features: - | For network burn-in, nodes can now be paired dynamically via a distributed coordination backend (as an alternative to a static - configuration). This allows burn-in to proceed on a 'first come - first served' basis with the nodes available, rather than a node + configuration). This allows burn-in to proceed on a "first come + first served" basis with the nodes available, rather than a node being blocked since the static partner is currently delayed. + In order to configure this dynamic pairing, the nodes will need - at least 'agent_burnin_fio_network_pairing_backend_url' in their - driver-info (the URL for the coordination backend). In order to + at least ``agent_burnin_fio_network_pairing_backend_url`` in their + ``driver_info`` (the URL for the coordination backend). In order to separate different hardware types, which may be using different networks and shall be burnt-in separately, the nodes can in - addition define 'agent_burnin_fio_network_pairing_group_name' to + addition define ``agent_burnin_fio_network_pairing_group_name`` to have pairing only happening between nodes in the same group. An - additional 'agent_burnin_fio_network_pairing_timeout' allows to + additional parameter ``agent_burnin_fio_network_pairing_timeout`` allows to limit the time given to the nodes to wait for a partner. diff --git a/releasenotes/notes/move_swraid_to_efibootmgr-d87c1bfde1661fb5.yaml b/releasenotes/notes/move_swraid_to_efibootmgr-d87c1bfde1661fb5.yaml index 3fa29284..39f202ff 100644 --- a/releasenotes/notes/move_swraid_to_efibootmgr-d87c1bfde1661fb5.yaml +++ b/releasenotes/notes/move_swraid_to_efibootmgr-d87c1bfde1661fb5.yaml @@ -1,7 +1,7 @@ --- fixes: - | - Use efibootmgr instead of grub2-install for software RAID. - This fixes an issue with images which include newer versions - of grub2-install as they refuse bootloader installations in - UEFI boot mode due to the lack of secure boot support. + Uses ``efibootmgr`` instead of ``grub2-install`` for software RAID. This + fixes an issue with images which include newer versions of + ``grub2-install``, such as CentOS Stream 8, as they refuse bootloader + installations in UEFI boot mode due to the lack of secure boot support. -- cgit v1.2.1