bd6f33070b
Attaching a port with minimum bandwidth policy would require to update the allocation of the server. But for that nova would need to select the proper networking resource provider under the compute resource provider the server is running on. For the first iteration of the feature we consider this out of scope. To avoid resource allocation inconsistencies this patch propose to reject such attach interface request. Rejecting such interface attach does not break existing functionality as today only the SRIOV Neutron backend supports the minimum bandwidth policy but Nova does not support interface attach with SRIOV interfaces today. A subsequent patch will handle attaching a network that has QoS policy. Co-Authored-By: Elod Illes <elod.illes@ericsson.com> Change-Id: Id8b5c48a6e8cf65dc0a7dc13a80a0a72684f70d9 blueprint: bandwidth-resource-provider
11 lines
465 B
YAML
11 lines
465 B
YAML
---
|
|
other:
|
|
- |
|
|
The ``POST /servers/{server_id}/os-interface`` request will be rejected
|
|
with HTTP 400 if the Neutron port referenced in the request body has
|
|
resource request as Nova currently cannot support such operation. For
|
|
example a Neutron port has resource request if a `QoS minimum bandwidth
|
|
rule`_ is attached to that port in Neutron.
|
|
|
|
.. _QoS minimum bandwidth rule: https://docs.openstack.org/neutron/latest/admin/config-qos.html
|