The GET /v2.0/qos/rule-types API does not return the minimum_packet_rate rule type even though the feature itself is configured, qos policy can be created with that rule type and ports can be bound with such qos policy.
It is reproduced on recent neutron and neutron-lib master in a devstack.
stack@master0:~/neutron$ git log --oneline | head -n1
e7b70521d0 Merge "Use elevated context to update router's external gateway"
stack@master0:~/neutron-lib$ git log --oneline | head -n1
c5fd706 Merge "Add "connectivity" property to "MechanismDriver""
Example outputs from this system:
stack@master0:~$ openstack network qos rule type list
+-------------------+
| Type |
+-------------------+
| minimum_bandwidth |
| bandwidth_limit |
+-------------------+
stack@master0:~$ openstack network qos rule list qp3-bw-pps
+--------------------------------------+--------------------------------------+---------------------+----------+-----------------+----------+-----------+-----------+
| ID | QoS Policy ID | Type | Max Kbps | Max Burst Kbits | Min Kbps | DSCP mark | Direction |
+--------------------------------------+--------------------------------------+---------------------+----------+-----------------+----------+-----------+-----------+
| 27a29b90-ce72-4f9c-8a0f-e36596a62e19 | 53bc1d66-c4ce-4f98-b703-8ae29afab6b1 | minimum_bandwidth | | | 2000 | | egress |
| 2872f1cd-88df-4f13-a689-d53a2b4bf923 | 53bc1d66-c4ce-4f98-b703-8ae29afab6b1 | minimum_bandwidth | | | 2000 | | ingress |
| 3aa02806-fe95-4bd9-b840-3d7472466f72 | 53bc1d66-c4ce-4f98-b703-8ae29afab6b1 | minimum_packet_rate | | | | | any |
+--------------------------------------+--------------------------------------+---------------------+----------+-----------------+----------+-----------+-----------+
Hello Balazs:
What driver were you using? Was that OVN+SR-IOV? I'm saying that because of the output.
Since [1], we return only the QoS rule types accepted by all loaded mechanism drivers. That means, for example, if you are using OVN, the supported rule set won't have the "packet_rate_limit" rule type.
However, you can create a rule of any type. When you try to assign an unsupported rule to a driver, the API will raise an exception.
However, if we use several drivers, what we should do is to return not the common subset (intersection) but the joined set (union). But this is an opinion.
Regards.
[1]https:/