Add physnet name case sensitivity limitation to the qos doc

Change-Id: I1485948b251e451895f8e773cc34be1221cf650d
This commit is contained in:
Balazs Gibizer 2021-05-07 18:24:40 +02:00
parent 52b14863ef
commit dcd277f4f1
1 changed files with 7 additions and 0 deletions

View File

@ -118,6 +118,13 @@ Limitations
an Open vSwitch bridge, and another 5 Gbps NIC whose virtual functions
can be handed out to servers by neutron-sriov-agent.
* Neutron allows physnet names to be case sensitive. So physnet0 and
Physnet0 are treated as different physnets. Physnets are mapped to
traits in Placement for scheduling purposes. However Placement traits are
case insensitive and normalized to full capital. Therefore the scheduling
treats physnet0 and Physnet0 as the same physnet. It is advised not to use
physnet names that are only differ by case.
Placement pre-requisites
------------------------