[openstack-dev] [oslo][oslo.config] Reloading configuration of service

2015-09-29 Thread mhorban
> Excerpts from Josh's message: >> So a few 'event' like constructs/libraries that I know about: >> >> http://docs.openstack.org/developer/taskflow/types.html#taskflow.types.notifier.Notifier >> >> >> I'd be happy to extract that and move to somewhere else if needed, it >> provides basic

Re: [openstack-dev] [oslo][oslo.config] Reloading configuration of service

2015-09-29 Thread Joshua Harlow
mhorban wrote: > Excerpts from Josh's message: >> So a few 'event' like constructs/libraries that I know about: >> >> http://docs.openstack.org/developer/taskflow/types.html#taskflow.types.notifier.Notifier >> >> >> I'd be happy to extract that and move to somewhere else if needed, it

Re: [openstack-dev] [oslo][oslo.config] Reloading configuration of service

2015-09-29 Thread Doug Hellmann
Excerpts from Joshua Harlow's message of 2015-09-29 11:39:16 -0700: > mhorban wrote: > > > Excerpts from Josh's message: > > > > >> So a few 'event' like constructs/libraries that I know about: > > >> > > >> > >

[openstack-dev] [oslo][oslo.config] Reloading configuration of service

2015-09-17 Thread mhorban
Hi Doug, > Rather than building hooks into oslo.config, why don't we build them > into the thing that is catching the signal. That way the app can do lots > of things in response to a signal, and one of them might be reloading > the configuration. Hm... Yes... It is really stupid idea to put

[openstack-dev] [oslo][oslo.config] Reloading configuration of service

2015-09-17 Thread mhorban
Hi Josh, > 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: > > - >

Re: [openstack-dev] [oslo][oslo.config] Reloading configuration of service

2015-09-17 Thread Doug Hellmann
Excerpts from mhorban's message of 2015-09-17 10:26:28 +0300: > Hi Doug, > > > Rather than building hooks into oslo.config, why don't we build them > > into the thing that is catching the signal. That way the app can do lots > > of things in response to a signal, and one of them might be

Re: [openstack-dev] [oslo][oslo.config] Reloading configuration of service

2015-09-17 Thread Joshua Harlow
Agreed, +1 :) Gotta start somewhere to get to somewhere else ;) mhorban wrote: Hi Josh, > 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

Re: [openstack-dev] [oslo][oslo.config] Reloading configuration of service

2015-09-17 Thread Joshua Harlow
So a few 'event' like constructs/libraries that I know about: http://docs.openstack.org/developer/taskflow/types.html#taskflow.types.notifier.Notifier I'd be happy to extract that and move to somewhere else if needed, it provides basic event/pub/sub kind of activities for taskflow

Re: [openstack-dev] [oslo][oslo.config] Reloading configuration of service

2015-09-15 Thread Joshua Harlow
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: -

[openstack-dev] [oslo][oslo.config] Reloading configuration of service

2015-09-15 Thread mhorban
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

Re: [openstack-dev] [oslo][oslo.config] Reloading configuration of service

2015-09-15 Thread Doug Hellmann
Excerpts from mhorban's message of 2015-09-15 19:38:58 +0300: > 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