I actually have a similar patch in my ovn for vtep series. but instead, I added a new command-line option for that... But goal is the same, => use different datapath type (dummy in my case).
So, I'm fine with this change, and will drop mine, looks good, On Mon, Jun 15, 2015 at 11:36 AM, Ben Pfaff <b...@nicira.com> wrote: > On Mon, Jun 15, 2015 at 11:28:12AM -0700, Gurucharan Shetty wrote: > > On Mon, Jun 15, 2015 at 11:09 AM, Daniele Di Proietto > > <diproiet...@vmware.com> wrote: > > > With this commit, the VTEP emulator detects the datapath_type of the > > > bridge used as a "physical" switch, and creates subsequent bridges > > > with the same type. This allows ovs-vtep to work with the userspace > > > datapath. > > > > > > Signed-off-by: Daniele Di Proietto <diproiet...@vmware.com> > > ... > > > > + ovs.util.ovs_fatal(0, "couldn't find %s datapath_type" % > ps_name, vlog) > > Is datapath_type always populated automatically? When I create a > > bridge on tip of master, that column does not get populated. > > Good catch, I think: it's not populated automatically, so treating "" as > an error is probably a bad idea. > _______________________________________________ > dev mailing list > dev@openvswitch.org > http://openvswitch.org/mailman/listinfo/dev > _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
