[ovs-dev] [PATCH] ovs-xapi-sync: Increase the tolerance level for xapi failures for bridges.

Gurucharan Shetty shettyg at nicira.com
Fri Jun 21 20:26:57 UTC 2013

On Wed, Jun 19, 2013 at 1:27 PM, Ben Pfaff <blp at 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 <gshetty at 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.


> Thanks,
> Ben.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openvswitch.org/pipermail/ovs-dev/attachments/20130621/56c27211/attachment-0003.html>

More information about the dev mailing list