[ovs-dev] [PATCH ovn 1/3] ovn: Enforce unique tags for container interfaces.

Thomas Graf tgraf at noironetworks.com
Tue Apr 7 07:29:16 UTC 2015


On 04/06/15 at 02:00pm, Gurucharan Shetty wrote:
> > I think lxc deployment inside the VM definitely makes sense from a
> > hardware isolation perspective but it may not be feasible for
> > everyone. A simple example is resource allocation across multiple
> > tenants on process level which becomes a lot more difficult if the
> > host can no longer see the tasks themselves.
> I did not quite understand what you mean above. The OVN schema allows
> both lxc-in-vm as well as lxc in host. The ovn-architecture document
> provides details on that front.

Right. That's why I said it's a nit on commit message level.

The commit message defined the tag as being a VLAN ID. The OVN
architecture doc does this as well to some extend. I'm not convinced
that using the VLAN ID this is suitable for everyone, in particular
as we don't support QinQ yet.

I agree though that identifying the VIF based on *a* tag is
appropriate.



More information about the dev mailing list