DocFix: sriov_nic_agent supports qos
The sriov_nic_agent added qos support with the following patches[1][2][3], and the document was not updated to reflect that. The bandwidth limit rule was added by [1] The minimum bandwidth rule was added by [2] and [3] This commit removes QoS from the "to be supported in the future" part of the body and adds a partially supported part to the body. [1] I364fc8158e502d4dcc3510d6157f12969961a11d [2] Iefe5e698e99d186202d6ef170f84e93bfbba46dd [3] I6b619a96a2bfde164646c71409b671352bc6ce7d Change-Id: Ia5e90307795683679a92214786e8d8021eb9ff57
This commit is contained in:
parent
83ecf60999
commit
7a313a55cf
@ -37,8 +37,9 @@ VM instances running on the compute node to the public network.
|
||||
|
||||
In most common deployments, there are compute and a network nodes.
|
||||
Compute node can support VM connectivity via SR-IOV enabled NIC. SR-IOV NIC Agent manages
|
||||
Virtual Functions admin state. In the future it will manage additional settings, such as
|
||||
quality of service, rate limit settings, spoofcheck and more.
|
||||
Virtual Functions admin state. Quality of service is partially implemented with the bandwidth limit
|
||||
and minimum bandwidth rules. In the future it will manage additional settings, such as additional
|
||||
quality of service rules, rate limit settings, spoofcheck and more.
|
||||
Network node will be usually deployed with either Open vSwitch or Linux Bridge to support network node functionality.
|
||||
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user