RFE: keystone-manage CLI to allow using syslog & specific log files
Bug #1570463 reported by
Emilien Macchi
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
Medium
|
Maram El-Salamouny |
Bug Description
Currently, keystone-manage CLI tool will by default write in $log_dir/$log_file, which is most of the case /var/log/
Some actions (like fernet keys generations) are dynamic, and having them in a separated logfile would be a nice feature for operators. Also supporting syslog would be very helpful for production deployments.
no longer affects: | keystone/newton |
Changed in keystone: | |
assignee: | nobody → Annapoornima Koppad (annakoppad) |
Changed in keystone: | |
assignee: | nobody → Anthony Washington (anthony-washington) |
Changed in keystone: | |
assignee: | Anthony Washington (anthony-washington) → nobody |
Changed in keystone: | |
assignee: | nobody → Huayu Ouyang (hlo323) |
Changed in keystone: | |
assignee: | nobody → Maram El-Salamouny (maramelsalamouny) |
To post a comment you must log in.
The fernet keys should not be writable by the keystone user, typically by root (same as a certificate), therefore the log should likewise be separate to avoid breaking normal logging.
The use of syslog would easily solve this issue.