Hi, We used a Launchpad bug [1] to track the process of moving to graduated oslo.service so you can refer to the list of affected projects.
_sd_notify is called when a service is launched just before a wait loop [2], [3] so you can check projects from [1] and look for those that start services using ServiceLauncher or ProcessLauncher. [1] https://bugs.launchpad.net/neutron/+bug/1466851 [2] https://github.com/openstack/oslo.service/blob/master/oslo_service/service.py#L277 [3] https://github.com/openstack/oslo.service/blob/master/oslo_service/service.py#L503 Thanks, Elena On Tue, Oct 13, 2015 at 10:01 AM, Thomas Goirand <z...@debian.org> wrote: > Hi, > > As oslo.service implements _sd_notify, I am deeply thinking about > switching Debian .service files to use Type=notify instead of > Type=simple (which is the default, and what OpenStack packages are using > in Debian). > > Though I'm not sure about the state of things. Which package has > switched to using oslo.service, and is _sd_notify always called when a > package declares a dependency on oslo.service? Could someone confirm a > list of projects for which I could enable Type=notify in all daemons? > > 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 >
__________________________________________________________________________ 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
