openstack/neutron
Code Issues Proposed changes

doc: Change availability of QoS policy change

Browse Source 
[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
This commit is contained in:
elajkat 2021-09-17 10:48:09 +02:00
parent b52e5ecae2
commit f546c11b33
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/source/admin/config-qos-min-bw.rst
View File

@ -62,7 +62,7 @@ Limitations
to change guarantees of in-use policies are rejected. to change guarantees of in-use policies are rejected.
* Changing the QoS policy of the port with new ``minimum_bandwidth`` rules * 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`` If the VM was booted with port without QoS policy and ``minimum_bandwidth``
rules the port update succeeds but placement allocations will not change. 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 The same is true if the port has no ``binding:profile``, thus no placement