This group is locked. No changes can be made to the group while it is locked.
Re: Retrying connections, persistence, controller restart for ovsdb southbound
toggle quoted message Show quoted text
i had a related question, for switch restarts. do we rely on ovs persistence to save the config, or do we always push down the controller's version of the config to the switch?
if former, then do we need a resync mechanism, to handle config changes that occured between switch reboots? the same resync operation could be used during controller restart.
From: Edward Warnicke <hagbard@...>
To: Ryan Goulding <ryandgoulding@...>
Cc: "ovsdb-dev@..." <ovsdb-dev@...>
Sent: Friday, August 14, 2015 9:23 PM
Subject: Re: [ovsdb-dev] Retrying connections, persistence, controller restart for ovsdb southbound
So we probably also need to get one for retrying connections.. because currently if the ovsdb node is not available or reachable when we configure a connection, we never retry, and if it goes away temporarily, we never retry.
On Fri, Aug 14, 2015 at 8:49 AM, Ryan Goulding <ryandgoulding@...> wrote:
ovsdb-dev mailing list