[ovs-discuss] Remote connection method for ovn-controller ovs-ofctl invocation.
JaiSingh.Rana at cavium.com
Thu Jul 13 14:06:35 UTC 2017
Thanks Richardson for the suggestion.
This seems to be a better way than using some configuration file for picking connection method. I will look into code for changes required.
From: Lance Richardson <lrichard at redhat.com>
Sent: 13 July 2017 19:05
To: Rana, JaiSingh
Cc: ovs-discuss at openvswitch.org
Subject: Re: [ovs-discuss] Remote connection method for ovn-controller ovs-ofctl invocation.
> From: "JaiSingh Rana" <JaiSingh.Rana at cavium.com>
> To: ovs-discuss at openvswitch.org
> Sent: Thursday, 13 July, 2017 3:49:15 AM
> Subject: [ovs-discuss] Remote connection method for ovn-controller ovs-ofctl invocation.
> Currently in Openvswitch-2.7.1, ovn-controller hard codes connection method
> for ovs-ofctl invokation as unix:file as assumption is there will be unix
> file created by vswitchd in OVS_RUNDIR for managing OF controller on bridge
> e.g. br-int.mgmt
> There is an issue in our Openvswitch offload model where vswitchd is running
> on nic and ovn-controller on host. As there is no option for telling
> ovn-controller to use tcp:port connection method for ovs-ofctl , flows are
> not being pushed to vswitchd.
> For providing the patch, need some input. Should connection method be
> provided as an argument to ovn-controller or it can be written to
> /etc/sysconfig/openvswitch from where ovn-controller can read and use if
> option is present otherwise it defaults to unix file method.
My suggestion would be to use external-ids in the local ovsdb, as is
currently done for ovn-remote and ovn-encap. Maybe something like:
ovs-vsctl set open . external-ids:ovn-ofctl=tcp:w.x.y.z:abcd
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the discuss