openstack
/
neutron-lib
Code Issues Proposed changes

Document that binding:profile is for compute services only 

References:
https://meetings.opendev.org/meetings/neutron_drivers/2022/neutron_drivers.2022-09-30-14.01.log.html#l-28
https://meetings.opendev.org/irclogs/%23openstack-neutron/%23openstack-neutron.2022-09-30.log.html#t2022-09-30T16:08:59

Counterexamples:
https://docs.openstack.org/neutron/rocky/admin/config-ovs-offload.html
https://specs.openstack.org/openstack/nova-specs/specs/rocky/implemented/sriov-trusted-vfs.html

Change-Id: Ia30f679a371911501c4a458b4764da7011535dca
This commit is contained in:
Bence Romsics 2022-10-21 13:48:54 +02:00
parent 30b74827f7
commit 6100385c76
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
api-ref/source/v2/parameters.yaml
View File

@ -2464,6 +2464,12 @@ binding:profile-request:
description: |
A dictionary that enables the application running on the specific host to
pass and receive vif port information specific to the networking back-end.
This field is only meant for machine-machine communication for compute
services like Nova, Ironic or Zun to pass information to a Neutron
back-end. It should not be used by multiple services concurrently or by
cloud end users. The existing counterexamples
(``capabilities: [switchdev]`` for Open vSwitch hardware offload and
``trusted=true`` for Trusted Virtual Functions) are due to be cleaned up.
The networking API does not define a specific format of this field.
The default is an empty dictionary.
If you update it with null then it is treated like {} in the response.