From f546c11b331b5c5827648c35f6a63f69537a6ebd Mon Sep 17 00:00:00 2001 From: elajkat Date: Fri, 17 Sep 2021 10:48:09 +0200 Subject: [PATCH] doc: Change availability of QoS policy change [1] allowed to change QoS policy of a bound port, but finally got only merged during Wallaby cycle. The documentation (see [2]) says that it is available from Victoria. Fix this to avoid misunderstandings. [1]: https://review.opendev.org/c/openstack/neutron/+/747774 [2]: https://docs.openstack.org/neutron/xena/admin/config-qos-min-bw.html#limitations Change-Id: If313ec090919206e7de7492c7b82c44be3eceff0 --- doc/source/admin/config-qos-min-bw.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/source/admin/config-qos-min-bw.rst b/doc/source/admin/config-qos-min-bw.rst index 37bcb9d0573..95ee1ab7f8f 100644 --- a/doc/source/admin/config-qos-min-bw.rst +++ b/doc/source/admin/config-qos-min-bw.rst @@ -62,7 +62,7 @@ Limitations to change guarantees of in-use policies are rejected. * Changing the QoS policy of the port with new ``minimum_bandwidth`` rules - changes placement ``allocations`` from Victoria release. + changes placement ``allocations`` from Wallaby release. If the VM was booted with port without QoS policy and ``minimum_bandwidth`` rules the port update succeeds but placement allocations will not change. The same is true if the port has no ``binding:profile``, thus no placement