Ben Pfaff <b...@ovn.org> writes: > On Mon, Mar 21, 2016 at 09:37:15AM -0400, Aaron Conole wrote: >> Currently, ``ovs-ctl start'' will attempt to start both the DB and >> vswitchd. This is quite convenient when the database already has all of >> the configuration values required, and when using a single services file >> for systemd integration. The same goes for the ``ovs-ctl stop'' command. >> >> However, there are some cases which are not easily covered. The case >> where we want to set values in the database prior to starting the >> forwarding path, as well as the case of supporting multiple service >> files, one per daemon (which is how systemd expects services to look). >> >> Signed-off-by: Aaron Conole <acon...@redhat.com> >> --- >> v2: >> It's possible that the way I did the save/restore flows is not the way folks >> want it, so please let me know. I did only basic testing with this. >> - Renamed the options to --ovs-vswitchd/--no-ovs-vswitchd >> and --ovsdb-server/--no-ovsdb-server >> - Updated the force_reload_kmod to abort in case of --no-ovs-vswitchd >> - Updated the flow save/restore functions to test for --ovs-vswitchd > > I think the ovs-ctl manpage didn't get fully updated to the new option > names.
D'oh! Thanks, v3 will solve this. > I think that the options should be listed in the ovs-ctl manpage list of > options, in addition to the list of steps. Cool, will do! > Thanks, > > Ben. _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
