Inception Logging Blueprint
Adapt Inception to use logging facilities instead of merely printing to
stdout/stderr.
After review, decide whether to implement "minimum" logging or go straight
to oslo/openstack logging or somewhere in between.
+ logging needs configuration and oslo provides that
- incorporating OpenStack practices pulls in a lot of code
Blueprint information
- Status:
- Complete
- Approver:
- Changbin Liu
- Priority:
- Medium
- Drafter:
- Andrew Forrest
- Direction:
- Approved
- Assignee:
- Changbin Liu
- Definition:
- New
- Series goal:
- None
- Implementation:
- Implemented
- Milestone target:
- None
- Started by
- Changbin Liu
- Completed by
- Changbin Liu
Related branches
Related bugs
Sprints
Whiteboard
Only two files exist with "print" statements in them (see appendix) but should start
with module-specific debuggers.
Time/Date should be appropriate for OpenStack compatibility.
Tasks:
------
T1 Decide which print statements should remain as prints
T2 Decide appropriate log level for each print statement that is to be converted
- in general print statements stating abstractly what is happening should
go to INFO while those showing in detail should go to DEBUG
- messages originating within exception handlers
- should be WARN or higher
- should be logged and displayed
APPENDIX
1. "print" grepped from source:
inception/
inception/
inception/
inception/
inception/
inception/
inception/
inception/
inception/
inception/
inception/
inception/
inception/
inception/
inception/
inception/
inception/
inception/
inception/
inception/
inception/
inception/
inception/
inception/
Work Items
Work items:
A. [forrest-r] review oslo/example openstack logging: INPROGRESS
B. [] choose python built-in logging, oslo or in-between: TODO
C. [forrest-r] implement choice: TODO