On Tue, Dec 20, 2016 at 8:27 AM, Guru Shetty <g...@ovn.org> wrote: > > > On 15 December 2016 at 05:35, Andy Zhou <az...@ovn.org> wrote: > >> The goal of this series is to make it easier to set up OVN in >> a larger setup, i.e. not having all services running on a single host. >> >> Currently ovn-central package starts and stop all three services >> northbound-db, northd and southbound-db on the same host. While it >> is convenient for a single host setup, it is hard to test scale >> and HA, where OVN services may have to be installed on different hosts. >> >> This patch series splits the ovn-central package into three packages >> ovn-northbound-database, ovn-southbound-database and ovn-northd. >> Also, Each one provides the corresponding systemd services. >> >> Another drawback of current packaging is that ovsdb-server is part >> of vswitchd package. If one wants to run ovn-northbound-database, >> he needs to install and start vswitchd service as well. This is >> unnecessary and may lead to confusions. This patch series separate >> ovsdb-server into its own package. >> >> ovn-central package is retained to be friendly to single host >> deployments. However ovn-central service is marked as exclusive >> with the other three services mentioned above. (I am not sure >> if this is necessary, and may more confusing than its worth) >> > > Overall, I have a few comments. > 1. Splitting ovs-vswitchd and ovsdb-server into separate packages will > need rock solid testing to figure out any upgrade or downgrade issues. > Those 2 have been together for a long time and it will have to be done very > carefully. > Thanks for the advice. I will work on this as a separate patch, carefully.
2. I am not a big fan of splitting ovn-central into 3 separate packages > (one for ovn-northd, one for NB DB and one for SB DB). Specially because, > we are anyway dependent on a config file to figure out who/where to connect > to. I think, having the single package is easier for people to get started > and explore OVN. Advanced users, will anyway have to use configuration > scripts, so as well use that to decide the daemons to start. > > I think less packages is just one dimension of easiness. Any one working with Linux system has to deal with multiple packages. I find having unnecessary files installed and unnecessary services running can be very confusing at times. On the other hand, I do agree with your suggestion. Since being able to configure and control individual services within ovn-central is a necessary step forward, let's start there. I will rework the patch series to reduce the scope. > > > > > >> >> Andy Zhou (5): >> rpms: Seperate ovsdb-server into its own package >> rpms: Style fixes >> rhel: Rename nrothd to central service >> ovn-ctl: Factor out start/stop ovnsb/ovnnb >> rpms: Adding three additional OVN packages >> >> ovn/utilities/ovn-ctl | 55 +++++++- >> ovn/utilities/ovn-ctl.8.xml | 4 + >> rhel/automake.mk | 3 + >> rhel/openvswitch-fedora.spec.in | 141 >> +++++++++++++++------ >> rhel/usr_lib_systemd_system_ovn-central.service | 34 +++++ >> ...sr_lib_systemd_system_ovn-northbound-db.service | 16 +++ >> rhel/usr_lib_systemd_system_ovn-northd.service | 29 ++++- >> ...sr_lib_systemd_system_ovn-southbound-db.service | 16 +++ >> 8 files changed, 251 insertions(+), 47 deletions(-) >> create mode 100644 rhel/usr_lib_systemd_system_ovn-central.service >> create mode 100644 rhel/usr_lib_systemd_system_ovn-northbound-db.service >> create mode 100644 rhel/usr_lib_systemd_system_ovn-southbound-db.service >> >> -- >> 1.8.3.1 >> >> _______________________________________________ >> dev mailing list >> d...@openvswitch.org >> https://mail.openvswitch.org/mailman/listinfo/ovs-dev >> > > _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
