[RFE] Expose Open vSwitch other_config column in the API
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Wishlist
|
Bence Romsics |
Bug Description
Some of our performance sensitive users would like to tweak Open vSwitch's Tx packet steering option under OpenStack:
https:/
available since Open vSwitch v2.17.0:
https:/
https:/
To enable that, we would like to expose some OVS interface configuration in a Neutron port's binding_profile.
Consider for example:
openstack port create port0 --binding-profile ovs_other_
more generally: --binding-profile ovs_other_
or an alternative syntax: --binding-profile ovs:other_
Given this information, ovs-agent can set the corresponding OVS interface's other_config (using the python native interface of course, not ovs-vsctl):
sudo ovs-vsctl set Interface ovs-interface-
sudo ovs-vsctl set Interface ovs-interface-
summary: |
- RFE Expose Open vSwitch other_config column in the API + [RFE] Expose Open vSwitch other_config column in the API |
Changed in neutron: | |
status: | New → In Progress |
Discussion topics:
1) We could whitelist the keys we accept in ovs_other_config, if needed.
2) At first (or hopefully ever), we don't need to support changing this value for a bound port.
3) Here we expose backend specific information in the API. At least we can reject it at port binding if the port is not bound by the ovs mech driver.
4) Are OVN folks interested in implementing this?
5) Do we need an API extension for this? We usually treat binding_profile as a blob that can contain anything.