From dcd277f4f1f6fa0b5d9568e03ece608e3bf34390 Mon Sep 17 00:00:00 2001 From: Balazs Gibizer Date: Fri, 7 May 2021 18:24:40 +0200 Subject: [PATCH] Add physnet name case sensitivity limitation to the qos doc Change-Id: I1485948b251e451895f8e773cc34be1221cf650d --- doc/source/admin/config-qos-min-bw.rst | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/doc/source/admin/config-qos-min-bw.rst b/doc/source/admin/config-qos-min-bw.rst index 7ddc7120ef1..c84815a3d5c 100644 --- a/doc/source/admin/config-qos-min-bw.rst +++ b/doc/source/admin/config-qos-min-bw.rst @@ -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 ------------------------