-----Mensaje original----- De: Jose A. Posada [mailto:joseap...@gmail.com] Enviado el: jueves, 24 de octubre de 2013 10:04 PM Para: discuss@openvswitch.org Asunto: How can I start a LXC container without brcompat compatibility module in OVS 1.11? Importancia: Alta
I was only able to start my LXC container by first loading the brcompat compatibility module in OVS 1.9 and early. LXC with this network configuration: lxc.network.type = veth lxc.network.flags = up lxc.network.link = br0 br0 is an OVS bridge. I need to know if there is a way to do that in OVS 1.10, 1.11, where the brcompat compatibility was removed. PD: (https://help.ubuntu.com/12.04/serverguide/lxc.html) Network Configuration Container networking in LXC is very flexible. It is triggered by the lxc.network.type configuration file entries. If no such entries exist, then the container will share the host's networking stack. Services and connections started in the container will be using the host's IP address. If at least one lxc.network.type entry is present, then the container will have a private (layer 2) network stack. It will have its own network interfaces and firewall rules. There are several options for lxc.network.type: lxc.network.type=empty: The container will have no network interfaces other than loopback. lxc.network.type=veth: This is the default when using the ubuntu or ubuntu-cloud templates, and creates a veth network tunnel. One end of this tunnel becomes the network interface inside the container. The other end is attached to a bridged on the host. Any number of such tunnels can be created by adding more lxc.network.type=veth entries in the container configuration file. The bridge to which the host end of the tunnel will be attached is specified with lxc.network.link = lxcbr0. lxc.network.type=phys A physical network interface (i.e. eth2) is passed into the container. Two other options are to use vlan or macvlan, however their use is more complicated and is not described here. A few other networking options exist: lxc.network.flags can only be set to up and ensures that the network interface is up. lxc.network.hwaddr specifies a mac address to assign the the nic inside the container. lxc.network.ipv4 and lxc.network.ipv6 set the respective IP addresses, if those should be static. lxc.network.name specifies a name to assign inside the container. If this is not specified, a good default (i.e. eth0 for the first nic) is chosen. lxc.network.lxcscript.up specifies a script to be called after the host side of the networking has been set up. See the lxc.conf(5) manual page for details. _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
