On 03/06/2015 11:36 AM, Gurucharan Shetty wrote: > The design was come up after inputs and discussions with multiple > people, including (in alphabetical order) Aaron Rosen, Ben Pfaff, > Ganesan Chandrashekhar, Justin Pettit, Russell Bryant and Somik Behera. > This commit introduces some complications around the Bindings table > of OVN schema that is yet to be sorted out. So this is a early version. > > Signed-off-by: Gurucharan Shetty <gshe...@nicira.com>
> +* When a container needs to be created inside the VM with a container network > +interface that is expected to be attached to a particular logical switch, the > +network plugin in that VM chooses any unused VLAN (This VLAN tag only needs > to > +be unique inside that VM. This limits the number of Container interfaces to > +4096 inside a single VM). This VLAN tag is stripped out in the hypervisor > +by OVN and is only useful as a context (or metadata) for OVN. The 4096 limitation is something that I keep thinking back to as an unfortunate limitation. I wish I had a good alternative to propose, but I don't. Do you have any additional thoughts on it? I think it's worth some extra consideration up front as this isn't a completely isolated implementation detail. IIUC, whatever is doing container management has to implement this part to hook up the container to ovs inside the VM to add the tags to the container traffic, so it doesn't seem like something that can be trivially changed later without some extra effort to provide a staged transition with backwards compatibility. -- Russell Bryant _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
