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

[Ben Pfaff]

On Mon, Apr 06, 2015 at 03:12:03PM -0400, Russell Bryant wrote:
> A logical port that represents a container that sits behind another
> logical port has both a parent_name and a tag set.  The parent_name
> identifies the parent port and the tag is the VLAN ID used to identify
> which traffic comes from that container.  The combination of
> parent_name and tag must always be unique.  This applies to both the
> ovn and ovn-nb schemas.
> 
> Signed-off-by: Russell Bryant <rbryant at redhat.com>

I'm pretty sure that this will be too restrictive because, in the
absence of nested virtualization, (parent_name, tag) will be the
constant pair (<empty>, <empty>) and ovsdb-server will reject that.

If I'm wrong, then this seems OK to me.