On 15 December 2015 at 10:50, Russell Bryant <russ...@ovn.org> wrote:
> On 12/15/2015 12:52 PM, Gurucharan Shetty wrote: > > Signed-off-by: Gurucharan Shetty <g...@ovn.org> > > --- > > debian/.gitignore | 1 + > > debian/automake.mk | 7 ++++ > > debian/control | 16 ++++++++++ > > debian/openvswitch-ovn-central.dirs | 1 + > > debian/openvswitch-ovn-central.init | 53 > +++++++++++++++++++++++++++++++ > > debian/openvswitch-ovn-central.install | 3 ++ > > debian/openvswitch-ovn-central.manpages | 3 ++ > > debian/openvswitch-ovn-central.postinst | 49 > ++++++++++++++++++++++++++++ > > debian/openvswitch-ovn-central.postrm | 44 +++++++++++++++++++++++++ > > debian/openvswitch-ovn-central.template | 5 +++ > > debian/rules | 3 ++ > > 11 files changed, 185 insertions(+) > > create mode 100644 debian/openvswitch-ovn-central.dirs > > create mode 100755 debian/openvswitch-ovn-central.init > > create mode 100644 debian/openvswitch-ovn-central.install > > create mode 100644 debian/openvswitch-ovn-central.manpages > > create mode 100755 debian/openvswitch-ovn-central.postinst > > create mode 100755 debian/openvswitch-ovn-central.postrm > > create mode 100644 debian/openvswitch-ovn-central.template > > I think it's worth looking at the differences between the fedora/rhel > and debian packaging here. Any points where we diverge substantially > will cause some pain for someone. For example, someone writing puppet > modules to deal with deploying this across distributions will have to > special case the different package names and service names. (That > puppet work is on my short-term todo list for OpenStack deployment > integration, for example). > > In the fedora/rhel case, we have a single openstack-ovn package that > includes ovn-controller and ovn-northd. It all seemed small enough that > one package seemed fine, but I'd be OK splitting them, too, if there's > good reason. > > The other big difference is the service name. Here you're using > "ovn-central" where the systemd unit for fedora/rhel is just > "ovn-northd". Why'd you go with "ovn-central" here? > My thought process was this, I am happy with any solution that you can think of. 1. With sys-v script, the startup script will automatically start the daemons during system bootup and in ubuntu/debian install of packages starts the daemons automatically. So, on all the hosts/hypervisors, we only need to start ovn-controller and not ovn-northd. So, I thought that a user will install only ovn-controller package in all the places he wants ovn-controller running but not ovn-northd. Hence I split those packages. 2. Currently for openvswitch on debian, we have openvswitch-switch and openvswitch-common packages. And openvswitch-switch starts both ovs-vswitchd and ovsdb-server daemons. The reason to give the name "central" was to include the possibility that in the future we may have more than just the ovn-northd daemon. 3. ovn-ctl is needed for all the daemons. ovn-nbctl is needed on every host for docker. So I thought a "common" package is needed - similar to openvswitch-common. It did occur to me that I am moving away from fedora packaging style. So in fedora, won't the systemd start all the daemons automatically? Do you need ovn-northd started everywhere? > > -- > Russell Bryant > _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
