On Wed, Dec 23, 2015 at 02:00:33PM -0800, Guru Shetty wrote: > On 23 December 2015 at 13:40, Ben Pfaff <b...@ovn.org> wrote: > > > On Wed, Dec 23, 2015 at 01:34:32PM -0800, Guru Shetty wrote: > > > I just looked at the OVN workflow for implementing VTEP schema (L2 only) > > > and at first glance it feels wrong. There is possibly a reason for the > > way > > > it has been implemented, but this is how I see it. > > > > > > The current workflow (from a test case in ovn-controller-vtep.at): > > > > > > 1. In the VTEP GW device, create a logical switch (via vtep-ctl). > > > > > > 2. In VTEP GW device, create a binding that associates > > vlan+physical_port > > > to that logical switch. This creates an entry in ovn-sb's chassis table's > > > 'vtep_logical_switches' column for that VTEP GW. > > > > > > 3. You are then supposed to create a logical switch in OVN NB and create > > a > > > logical port for that switch and then set options:vtep-logical-switch to > > > point to the logical switch that you created in the VTEP GW. > > > > > > IMO the above is wrong. The correct workflow should just have been: > > > > > > 1. In OVN NB, create a logical port (for a particular VTEP physical > > port), > > > specify the VTEP GW chassis to which this logical port belongs to and > > also > > > specify the vlan. > > > > > > The above information should go down to VTEP GW's database and it should > > > create a logical switch record and also create the vlan bindings from > > > physical port to logical switch. > > > > Are you saying that the current workflow is wrong or that it is more > > complicated than necessary? I'm all in favor of making OVN simpler to > > use and deploy. I remember discussing with Alex different ways to do it > > and I think that he eventually settled on a way that we knew was more > > complicated than necessary with a plan to make it easier in the future, > > and perhaps that's what you're seeing. > > > > One could just say that it is more complicated than necessary (instead of > saying it is wrong). > > If you look at it operationally, you are now supposed to configure and > manage each of your physical gateways individually and then come and > configure the NB database. The README.ovs-vtep.md does not do it this way > nor does NSX (which is mentioned in that readme and the vtep man page.)
To be clear, I'm in favor of doing it "the right way". _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
