On Fri, Jun 21, 2013 at 01:26:57PM -0700, Gurucharan Shetty wrote: > On Wed, Jun 19, 2013 at 1:27 PM, Ben Pfaff <b...@nicira.com> wrote: > > > On Wed, Jun 19, 2013 at 02:03:15AM -0700, Gurucharan Shetty wrote: > > > Specifically for the case, where we know that a bridge record > > > should exist in xapi, if we don't get any bridge records, log > > > the failure and retry again later. > > > > > > Signed-off-by: Gurucharan Shetty <gshe...@nicira.com> > > > > Could we add a helper function for the common code here? > > > I decided to abandon this patch because this makes an assumption that all > the bridges that are created in xenserver are through standard xapi > methods. If anyone creates an asynchronous bridge through command line (ex: > using ovs-vsctl), ovs-xapi-sync will think that xapi is down because there > are no records for the new bridge. > > If xapi is completely down, ovs-xapi-sync will crash and restart. During > the restart, it will wait for xapi to start. So we are protected against > that. For the hypothetical scenario of xapi giving wrong information, there > is only so much you can do.
Good point, thanks. _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
