[ovs-dev] [PATCH ovn 2/2] fedora.spec: Create openvswitch-ovn package.

Russell Bryant rbryant at redhat.com
Fri May 29 21:07:19 UTC 2015


On 05/29/2015 04:50 PM, Ben Pfaff wrote:
> On Fri, Apr 24, 2015 at 01:06:06PM -0400, Russell Bryant wrote:
>> This patch creates a new subpackage for OVN, openvswitch-ovn.  It also
>> installs systemd unit files for ovncontroller and ovnnorthd services.
>> Finally, it installs some template service configuration files into
>> /etc/sysconfig/.
>>
>> If you want to run ovn-controller on a host running ovs:
>>
>>     # systemctl start ovncontroller
>>
>> If you want to run ovn-northd and ovsdb-server on a management host:
>>
>>     # systemctl start ovnnorthd
>>
>> If you want to run all of ovs and ovn on the same host:
>>
>>     # cat << EOF > /etc/sysconfig/openvswitch
>>     OPTIONS="'--extra-dbs=ovnnb.db ovnsb.db'"
>>     EOF
>>
>>     # cat << EOF > /etc/sysconfig/ovnnorthd
>>     OPTIONS="--no-ovsdb-server"
>>     EOF
>>
>>     # ovn-ctl create_ovn_dbs
>>     # systemctl start openvswitch
>>     # systemctl start ovnnorthd
>>     # systemctl start ovncontroller
>>
>> Signed-off-by: Russell Bryant <rbryant at redhat.com>
> 
> This looks nice but it seems awkward to have to edit config files if you
> want to run both OVS and OVN on a host.  Do you think there's a way to
> make it simply a matter of starting both services?

I agree that it's a little awkward.  It's a bit better in the latest
rev, but you still have to create the ovn dbs and edit the openvswitch
config to use them.

http://openvswitch.org/pipermail/dev/2015-May/055586.html

I hadn't thought of a good way to make it better, but let's see ...

I see that ovsdb-server supports a command over the appctl unix socket
to tell it to add a db.  We could make ovn-northd automatically create
the dbs if they're not present and tell ovsdb-server to add them.  That
should make it as simple as just starting the services.

A downside is that would make a built-in assumption in ovn-northd that
it runs local to ovsdb-server.  The systemd unit file assumes that right
now, but the code doesn't (and probably shouldn't).  The same general
thing could be implemented in a shell wrapper for ovn-northd ... which
sounds kind of like ovn-ctl, so maybe I should go back to making use of
that.

Let me know if you have thoughts.  Otherwise, I'm thinking I should add
what's needed to make this only require starting the services to ovs-ctl
and ovn-ctl.

-- 
Russell Bryant



More information about the dev mailing list