[ovs-git] [openvswitch/ovs] 43d3e6: ovn: Add ovn-ctl to assist with OVN daemon lifecyc...

[GitHub]

  Branch: refs/heads/ovn
  Home:   https://github.com/openvswitch/ovs
  Commit: 43d3e694152cb34f65b941a97b3741dd4d42462d
      https://github.com/openvswitch/ovs/commit/43d3e694152cb34f65b941a97b3741dd4d42462d
  Author: Russell Bryant <rbryant at redhat.com>
  Date:   2015-06-15 (Mon, 15 Jun 2015)

  Changed paths:
    M configure.ac
    M ovn/automake.mk
    A ovn/utilities/.gitignore
    A ovn/utilities/automake.mk
    A ovn/utilities/ovn-ctl
    A ovn/utilities/ovn-ctl.8.xml

  Log Message:
  -----------
  ovn: Add ovn-ctl to assist with OVN daemon lifecycle.

This patch introduces ovn-ctl, which is similar to ovs-ctl.  I opted
for a new script as everything in OVN so far is nicely isolated, so a
new script seemed to make the most sense.

If you'd like to run ovn-controller on a host already running ovs:

    # ovn-ctl start_controller

If you'd like to run ovn-northd:

    # ovn-ctl start_northd

Note that ovn-ctl assumes that ovn-northd is running on the same
server as ovsdb-server hosting the OVN databases.  Based on the
current architecture this seems like a completely reasonable
assumption.  This can be improved later when needed.

There's some additional stuff happening in start_northd to make the
experience nicer and not require additional steps by the
administrator.  It creates the OVN dbs if they don't exist.  If
ovsdb-server hasn't loaded them, it tells it to load them, as well.

ovn-ctl also supports running everything on the same host.  This would
be common in a test environment with a single host or small set of
hosts.  That would simply be:

    # ovs-ctl start --system-id=random
    # ovn-ctl start_northd
    # ovn-ctl start_controller

Signed-off-by: Russell Bryant <rbryant at redhat.com>
CC: Flavio Leitner <fbl at redhat.com>
CC: Ben Pfaff <blp at nicira.com>
[blp at nicira.com added configure.ac code to create ovn/utilities builddir]
Signed-off-by: Ben Pfaff <blp at nicira.com>