Open Stack

On 03/19/2018 09:22 AM, Jim Rollenhagen wrote:
>
> On Sat, Mar 17, 2018 at 9:49 PM, Doug Hellmann <doug at doughellmann.com
> <mailto:doug at doughellmann.com>> wrote:
>
>     Both of those are good ideas.
>
>
> Agree. I like the socket idea a bit more as I can imagine some
> operators don't want config file changes automatically applied. Do we
> want to choose one to standardize on or allow each project (or
> operators, via config) the choice?

Just to recap, keystone would be listening for when it's configuration
file changes, and reinitialize the logger if the logging settings
changed, correct?

Would that suffice for the goal? We'd be explicit in checking for
logging option changes, so modifications to other configuration options
shouldn't affect anything, should they?

>
>     I believe adding those things to oslo.service would make them
>     available to all applications. 
>
>
> Not necessarily - this discussion started when the Keystone team was
> discussing how to implement this, given that keystone doesn't use
> oslo.service. That said, it should be easy to implement in services
> that don't want this dependency, so +1.
>
> // jim
>
>
> __________________________________________________________________________
> 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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20180514/ba364935/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20180514/ba364935/attachment.sig>