From b41676f7fb9d98afb44f636cd1c10153f2b2aa15 Mon Sep 17 00:00:00 2001 From: Brian Haley Date: Fri, 23 Oct 2020 08:59:56 -0400 Subject: [PATCH] Fix recent QoS minimum_bandwidth release note Just fixed some grammatical issues in the release note. Change-Id: I8b87ae6244b3eb74e7296139aaa5f654afbd8e57 --- ...s_allocation_for_bound_port-5358620322b66ae9.yaml | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/releasenotes/notes/update_qos_allocation_for_bound_port-5358620322b66ae9.yaml b/releasenotes/notes/update_qos_allocation_for_bound_port-5358620322b66ae9.yaml index 8d64c0695dc..7de48e7a163 100644 --- a/releasenotes/notes/update_qos_allocation_for_bound_port-5358620322b66ae9.yaml +++ b/releasenotes/notes/update_qos_allocation_for_bound_port-5358620322b66ae9.yaml @@ -1,8 +1,10 @@ --- features: - | - Update of an ``already bound port`` with ``QoS minimum_bandwidth`` rule - with new ``QoS policy`` with ``minimum_bandwidth`` rule changes the - allocations in placement as well. ``NOTE``: updating the - ``minimum_bandwidth`` rule of a QoS policy that is attached to a port - which is bound to a VM is still not possible. + Update of an already bound port with a QoS ``minimum_bandwidth`` rule + with a new QoS policy with a ``minimum_bandwidth`` rule now changes the + allocations in placement as well. + + .. NOTE:: Updating the ``minimum_bandwidth`` rule of a QoS policy that + is attached to a port which is bound to a VM is still not + possible.