On 12/15/2014 04:21 PM, Ihar Hrachyshka wrote: > On 14/12/14 09:45, Thomas Goirand wrote: >> Hi, > >> As I am slowing fixing all systemd issues for the daemons of >> OpenStack in Debian (and hopefully, have this ready before the >> freeze of Jessie), I was wondering what kind of Type= directive to >> put on the systemd .service files. I have noticed that in Fedora, >> there's Type=notify. So my question is: > >> Do all OpenStack daemons, as a rule, support the DBus sd_notify >> thing? Should I always use Type=notify for systemd .service files? >> Can this be called a general rule with no exception? > > (I will talk about neutron only.) > > I guess Type=notify is supposed to be used with daemons that use > Service class from oslo-incubator that provides systemd notification > mechanism, or call to systemd.notify_once() otherwise. > > In terms of Neutron, neutron-server process is doing it, metadata > agent also seems to do it, while OVS agent seems to not. So it really > should depend on each service and the way it's implemented. You cannot > just assume that every Neutron service reports back to systemd. > > In terms of Fedora, we have Type=notify for neutron-server service only. > > BTW now that more distributions are interested in shipping unit files > for services, should we upstream them and ship the same thing in all > interested distributions?
In Debian & Ubuntu, we use a system which, from a sysv-rc init script, generates startup files for systemd, sysv-rc, and upstart. So if you where shipping .service files, I'm not sure I'd use them (though they may serve as good documentation...). Cheers, Thomas Goirand (zigo) __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
