71c732c833
Currently all privsep calls use the same logging level as they use the ``oslo_privsep.daemon`` logger. This creates a problem for services like nova where we don't want to log its own privsep debug messages by default (even in debug mode) but we want them for os-brick privsep calls. This patch introduces a new string parameter to ``PrivContext`` called ``logger_name`` to control the name of the logger to use, which defaults to ``oslo_privsep.daemon``. Related-Bug: #1922052 Change-Id: Ie7cc25ed53563dd500f7b10ff43a48518d46a2e0
16 lines
592 B
YAML
16 lines
592 B
YAML
---
|
|
features:
|
|
- |
|
|
``PrivContext`` accepts a new string parameter called ``logger_name`` to
|
|
define the logger we want to use for the daemon logs of this context.
|
|
|
|
By default all contexts use ``oslo_privsep.daemon``, but in some cases we
|
|
may need finer grained log levels, for example nova running in debug mode
|
|
could log its own privsep calls on INFO level regardless, but leave all
|
|
libraries' privsep calls, such as os-brick's, to be logged in the normal
|
|
DEBUG level.
|
|
|
|
See `bug 1922052`_.
|
|
|
|
.. _`bug 1922052`: https://bugs.launchpad.net/nova/+bug/1922052
|