Sounds like a useful idea if projects can plug-in themselves into the reloading process. I definitely think there needs to be a way for services to plug-in to this, although I'm not quite sure it will be sufficient at the current time though. An example of why: - https://github.com/openstack/cinder/blob/stable/kilo/cinder/volume/__init__.py#L24 (unless this module is purged from python and reloaded it will likely not reload correctly). Likely these can all be easily fixed (I just don't know how many of those exist in the various projects); but I guess we have to start somewhere so getting the underlying code able to be reloaded is a first step of likely many. - Josh mhorban wrote: > Hi guys, > > I would like to talk about reloading config during reloading service. > Now we have ability to reload config of service with SIGHUP signal. > Right now SIGHUP causes just calling conf.reload_config_files(). > As result configuration is updated, but services don't know about it, > there is no way to notify them. > I've created review https://review.openstack.org/#/c/213062/ to allow to > execute service's code on reloading config event. > Possible usage can be https://review.openstack.org/#/c/223668/. > > Any ideas or suggestions > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev