Open Stack

On Wed, Jul 25, 2018 at 03:22:27PM +0530, pranab boruah wrote:
> Hello folks,
> 
> I have filed a bug in os-vif:
> https://bugs.launchpad.net/os-vif/+bug/1778724 and
> working on a patch. Any feedback/comments from you guys would be extremely
> helpful.
> 
> Bug details:
> 
> OVS DB server has the feature of listening over a TCP socket for
> connections rather than just on the unix domain socket. [0]
> 
> If the OVS DB server is listening over a TCP socket, then the ovs-vsctl
> commands should include the ovsdb_connection parameter:
> # ovs-vsctl --db=tcp:IP:PORT ...
> eg:
> # ovs-vsctl --db=tcp:169.254.1.1:6640 add-port br-int eth0
> 
> Neutron supports running the ovs-vsctl commands with the ovsdb_connection
> parameter. The ovsdb_connection parameter is configured in
> openvswitch_agent.ini file. [1]
> 
> While adding a vif to the ovs bridge(br-int), Nova(os-vif) invokes the
> ovs-vsctl command. Today, there is no support to pass the ovsdb_connection
> parameter while invoking the ovs-vsctl command. The support should be
> added. This would enhance the functionality of os-vif, since it would
> support a scenario when OVS DB server is listening on a TCP socket
> connection and on functional parity with Neutron.
> 
> [0] http://www.openvswitch.org/support/dist-docs/ovsdb-server.1.html
> [1] https://docs.openstack.org/neutron/pike/configuration
> /openvswitch-agent.html
> TIA,
> Pranab

Hello Pranab,

Makes sense for me. This is really related to the OVS plugin that we
are maintaining. I guess you will have to add a new config option for
it as we have with 'network_device_mtu' and 'ovs_vsctl_timeout'.

Don't hesitate to add me as reviewer when patch is ready.

Thanks,
s.

> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev