Browse Source

Unify the usage of the log module

1. What is the problem?
In tricircle, some files use oslo_log, while others use logging. The
oslo.log(logging) configuration library provides standardized
 configuration for all openstack projects. I think different files in
 tricircle should use a same logging module and it's better to use
 oslo_log.

2. What is the solution to the problem?
Replace logging module with oslo_log.

3. What the features need to be implemented to the Tricircle to realize
the solution?
No new features

Change-Id: Ib3221f763dbe410b4252e5188d13a5824813846e
changes/76/394776/2
howardlee 5 years ago
committed by howard lee
parent
commit
0aec9fe2b0
2 changed files with 2 additions and 4 deletions
  1. +1
    -2
      cmd/api.py
  2. +1
    -2
      cmd/xjob.py

+ 1
- 2
cmd/api.py View File

@ -16,7 +16,6 @@
# Much of this module is based on the work of the Ironic team
# see http://git.openstack.org/cgit/openstack/ironic/tree/ironic/cmd/api.py
import logging as std_logging
import sys
from oslo_config import cfg
@ -53,7 +52,7 @@ def main():
restapp.serve(service, CONF, workers)
LOG.info(_LI("Configuration:"))
CONF.log_opt_values(LOG, std_logging.INFO)
CONF.log_opt_values(LOG, logging.INFO)
restapp.wait()


+ 1
- 2
cmd/xjob.py View File

@ -21,7 +21,6 @@ import eventlet
if __name__ == "__main__":
eventlet.monkey_patch()
import logging as std_logging
import sys
from oslo_config import cfg
@ -53,7 +52,7 @@ def main():
xservice.serve(xservice.create_service(), workers)
LOG.info(_LI("Configuration:"))
CONF.log_opt_values(LOG, std_logging.INFO)
CONF.log_opt_values(LOG, logging.INFO)
xservice.wait()


Loading…
Cancel
Save