In recent conversations it has been confirmed we need to make sure a port is bound by neutron in a pod that has a link to the amphora controllers (i.e the ovn controller) in order for neutron to allow traffic and establish routes. As this seems something much like the o-hm0 interface in tripleo, we'll need to configure and port on the integration bridge is so neutron can bind it as part of the required network on the relevant integration bridge.

Some options are

• have a script that runs in the ovn-controller pod to run the ovs-vsctl commands locally. This has the benefit of tying the commands to the lifecycle of the pod and existence of the integration bridge. It has the downside of being less than transparent to octavia deployment
• assuming ovs-vsctl can create and remote connection (it should but will probably need security info), add a controller or augment an existing per-deployment controller to monitor the state or periodically run "add-port" with may-exist.