OpenStack Networking (Neutron) Specifications
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

2.8 KiB

OFAgent: Merge br-int and br-tun

merge br-int and br-tun and stop using OVS patch ports feature. this involves drastic flow table changes.

Problem description

ofagent aims to be portable among switch implementations. currently it uses some of OVS specific features. patch ports is one of them.

Proposed change

merge br-int and br-tun into a single bridge.


  • give up and declare that tunnel support is only for OVS. this is not what we want to do.
  • use veth pair instead. this is not ideal as it still requires multiple logical bridge feature. besides that, it likely involve some performance loss because patch ports is better optimized than veth pair.

Data model impact


REST API impact


Security impact


Notifications impact


Other end user impact


Performance Impact

because OVS patch ports hardly have negative performace effects for fast path, this change is not expected to improve performance.

Other deployer impact

when upgrading the agent, deployer might want to remove br-tun.

Developer impact




Primary assignee:


Other contributors:


Work Items

  • design flow table. see flow_table for WIP design.
  • implement it in ofagent neutron agent
  • document the upgrade procedure


strictly speaking, none. but the following items are nice to have before this.

  • ofagent-l2pop blueprint (our WIP implementation relies on this)
  • matrohon's get_device_details-enhancement. or other way to obtain device's mac_address. (for example, make l2pop provide device-id for entries.) we want to use it for node local routing of packets.


  • unit tests
  • existing third party testing

Documentation Impact

  • document the upgrade procedure