On Tue, Aug 8, 2017 at 1:32 PM, Guru Shetty <g...@ovn.org> wrote:
> On 8 August 2017 at 07:42, Timothy Redaelli <tredae...@redhat.com> wrote:
>> The reload procedure will trigger a script that saves the flows and tlv
>> maps then it restarts ovsdb-server, it stops ovs-vswitchd, it sets
>> other_config:flow-restore-wait=true (to wait till flow restore is
>> finished), it starts ovs-vswitchd, it restore the backupped flows/tlv
>> maps and it removes other_config:flow-restore-wait=true (logic mostly
>> from ovs-ctl).
>> It uses systemctl with --job-mode=ignore-dependencies to restart
>> and stop and start ovs-vswitchd in order to avoid systemd to restart the
>> other components due to dependencies (as explained in
>> It also uses --bundle, when available, in order to minimize the downtime.
> The core script can probably be added to ovs-ctl, reuse some functions and
> then you can call it? This way, other platforms can benefit too.
Sounds like a good suggestion.
What would you think about updating the stop/start behavior to do
this, as well? It looks like this makes "reload" actually just an
"intelligent restart". systemctl has a "restart" command too, which
looks like it just does stop/start, and it'd be nice to make that work
dev mailing list