[systemd-devel] Linking containers

Peter Paule systemd-devel at fedux.org
Wed Mar 11 22:33:03 PDT 2015

Excerpts from Peter Paule's message of 2015-03-02 18:49:42 +0100:
> > I am not sure I want to talk a TCP/TLS based protocol just to add a
> > interface to a local switch. 
> > 
> > To integrate this stuff closely they should either provide a C
> > library, or a bus API or something similar, but having to reimplement
> > a new protocol just to be able to add an interface to a switch is too
> > much...
There's a C-API available, but it's poorly documented. Here's the answer
from one of the `of-config`-maintainers:

  I'm afraid that ovsdb-idl.h (and the commented code of the functions
  declared there) is the only source of information. The ovs-vsctl tool
  also uses IDL, so you can inspire there. You can also try to aks in
  openvswitch's ovs-dev mailing list.


> I understand that. I just mentioned it because you would
> gain support for other sw/hw products as well because OpenFlow is
> vendor-agnostic. 
> BTW: I opened a ticket at their repository at github. Maybe I get some
> more usable information I can pass on to you.
> > The --network-veth and --network-bridge= switches currently support
> > only a single interface. If you want more you need to set them up
> > first, and then move them into the container with --network-interface=
> > which may be called multiple times.
> Ok. Thanks

More information about the systemd-devel mailing list