On 04/06/2015 06:11 PM, Ben Pfaff wrote: > 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 <rbry...@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.
You're right. My simple test made sure more than one port with the same parent_name was rejected, but I failed to re-test multiple ports without anything set. Oops. I suppose it's about time I start writing some real tests for all of this ... -- Russell Bryant _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
