Hi,
I am starting to work with Docker and saw an section at the end of this
article (http://www.opencloudblog.com/?p=66).
Basically I am creating some containers and want to use ovs for virtual
switching purpose.
On my host, OVS(2.3.1) & Docker(1.4.1) are installed.
What I am doing :
ovs-vsctl add-port vswitch-untrust vlan8 tag=8 -- set Interface vlan8
type=internal
ovs-vsctl add-port vswitch-untrust vlan9 tag=9 -- set Interface vlan9
type=internal
Then I am retrieving the pid of the new containers thanks to a docker
command (sudo docker inspect -f '{{.State.Pid}}' id)
Then I am moving the interface into the container's workspace :
ip link set vlan8 netns pid
ip link set vlan9 netns pid
Firing up the interface
ip netns exec pid ip link set vlan8 up
ip netns exec pid ip link set vlan9 up
Giving an IP address
ip netns exec pid_master ip addr add 10.20.8.254/24 dev vlan8
ip netns exec pid_master ip addr add 10.20.9.254/24 dev vlan9
Everything is working as expected expect one thing :
When I tried to stop the container and start it again I am in a strange
situation where the vlan8 & vlan9 are present in ovs-vsctl but not on
the default workspace as they have move to the container workspace! If I
try to delete vlan8 or vlan0 with ovs-vsctl del-port then I got a kernel
panic :(
Is there a proper way to deal with ovs and namespace? If anyone has some
experience with ovs & docker I would love to hear about that...
Many thanks
belette
_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
