On Tue, Apr 28, 2015 at 11:49 AM, Han Zhou <[email protected]> wrote:
> Hi Shan, > > Thanks, but why can't we just add an internal port to OVS bridge and > put into namespace? > Internal port is single port that is connects to hosts IP stack. veth pair, come with pair of ports, like a pipe, one end in one namespace (your host) and another end in docker containers namespace. So, packets send at one end is received at another end . > And what's the native support mentioned in INSTALL.docker.md? > Docker uses linux bridges natively i.e., when you launch a container, it creates its own veth pair, and sets up IP etc. It also removes the veth pair, etc when a docker container is deleted. Docker does not have a native support for Open vSwitch Bridges. i.e., you have to manually add Docker in OVS Bridge and remove the veth pair, when the docker is deleted. AFAIK, Native integration of Docker with Open vSwitch, is on the road-map. > > Best regards, > Han > > On Tue, Apr 28, 2015 at 2:13 PM, Shanmugam Sundaram > <[email protected]> wrote: > > Hi Han, > > > > Dockers uses NameSpaces for isolation, to connect between network > > namespaces, we have to go with veth pairs. > > > > regards, > > Shan > > > > On Tue, Apr 28, 2015 at 11:35 AM, Han Zhou <[email protected]> wrote: > >> > >> Hello everyone, > >> > >> I have a question about the ovs-docker utility. Why can't internal > >> port work for docker case? For native support, does it mean we need a > >> new port type? > >> > >> Best regards, > >> Han > >> _______________________________________________ > >> discuss mailing list > >> [email protected] > >> http://openvswitch.org/mailman/listinfo/discuss > > > > > > > > > > -- > > regards, > > Shan > -- regards, *Shan*
_______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
