[lxc-devel] [PATCH 3/3] allow lxc.network.pair to specify host-side name for veth interface

Andrian Nord nightnord at gmail.com
Tue Nov 17 23:42:24 UTC 2009


On Wed, Nov 18, 2009 at 02:23:27AM +0300, Michael Tokarev wrote:
> other things like bridge should be specified.  Instead, if bridge
> is needed AND it should be done using config file still, I'd go
> for lxc.network.bridge parameter instead.

Agreed. Name 'bridge' for bridging and 'link' for linking (macvlan/phys to
physical device, veth to it's pair) would be much more logical.

>     phy: the host device to pass to container
>       (how about renaming it??)

Is it possible? If yes - probably lxc.network.name should serve for this
task perfectly.

>   lxc.network.bridge - if specified, add it to the bridge.
>     Probably only valid for veth again, but it can be done
>     unconditionally in the common code and fail with system
>     errno.

Maybe it should be called lxc.network.veth.bridge than? It will allow to
introduce lxc.network.veth.ip* values, for host-side autoconfiguration.
lxc.network.{veth.,}route = would also quite useful =)

> To me, the above looks more logical.  But this breaks
> current setup for sure.

Probably your code should check, if 'link' interface already exists, and
issue well-readable error. It will show everyone, that their
configuration is not valid anymore and force them to read documentation,
that should be also updated.




More information about the lxc-devel mailing list