[ovs-discuss] Using unix sockets for controller communication

Jari Sundell sundell.software at gmail.com
Tue Oct 18 05:25:46 UTC 2011


On Tue, Oct 18, 2011 at 1:46 AM, Ben Pfaff <blp at nicira.com> wrote:
> On Mon, Oct 17, 2011 at 02:59:43PM +0900, Jari Sundell wrote:
>> - I still have to set disable-in-band despite the controller being on
>> a unix socket. Not sure if that was due to me having set tcp:127.0.0.1
>> prior to testing.
>
> In-band control should only get triggered if you have a manager
> configured (e.g. with "ovs-vsctl set-manager") with a TCP or SSL type,
> or if you have an in-band controller configured.  (What do "ovs-vsctl
> list manager" and "ovs-vsctl list controller" print?)

$ ovs-vsctl list manager
$ ovs-vsctl list controller
_uuid               : 3322696b-38c3-4240-b165-f64376278f0a
connection_mode     : []
controller_burst_limit: []
controller_rate_limit: []
external_ids        : {}
inactivity_probe    : []
is_connected        : true
local_gateway       : []
local_ip            : []
local_netmask       : []
max_backoff         : []
role                : other
status              : {last_error="No such file or directory",
sec_since_connect="160", sec_since_disconnect="183", state=ACTIVE}
target              : "unix:/usr/share//ovs/var/run/openvswitch/br0.controller"

Tried restarting the daemon so that no tcp controllers had been set
during the run, and still the issue arises.

>> - The whitelist string comparison seems to encounter some issues when
>> the prefix used to compile ovs contains double slashes, requiring us
>> to insert an additional slash when setting the controller. E.g.
>> 'unix:/usr/share/foo//ovs/var/run/openvswitch/br0.controller', which
>> can crop up when using scripts to compile, etc.
>
> It would be a good idea to fix the scripts, but here's a revised patch
> that works around that.

-            if (equal_pathnames(c->target, whitelist)) {
+            if (!equal_pathnames(c->target, whitelist)) {

Except for that small fix, it works nicely.

Jari Sundell



More information about the discuss mailing list