Hey folks! I just wanted to raise your awareness of a forum session and a working session on Log Messages that is happening during the Boston Summit.
Here is the link to the etherpad for these sessions: https://etherpad.openstack.org/p/BOS-forum-log-messages We’ve been going around in circles on some details of the log messages for years, and Doug Hellmann has graciously stepped up to try and wrestle this beast into submissions. So, besides giving him a warm round of applause, let’s give him (and the small cadre of folks working with him on this) our respectful interactions, comments, concerns, high fives, etc. and turn up to the sessions to get this spec implementable in the here and now. Please add your comments, topics, pre forum discussions, etc. on the etherpad so that we remember to review and discuss them in the sessions. Thanks and see you soon! --Rocky As reference, here is Doug’s email [1] advertising the spec: I am looking for some feedback on two new proposals to add IDs to log messages. The tl;dr is that we’ve been talking about adding unique IDs to log messages for 5 years. I myself am still not 100% convinced the idea is useful, but I would like us to either do it or definitively say we won't ever do it so that we can stop talking about it and consider some other improvements to logging instead. Based on early feedback from a small group who have been involved in the conversations about this in the past, I have drafted new two specs with different approaches that try to avoid the pitfalls that blocked the earlier specs: 1. A cross-project spec to add logging message IDs in (what I hope is) a less onerous way than has been proposed before: https://review.openstack.org/460110 2. An Oslo spec to add some features to oslo.log to try to achieve the goals of the original proposal without having to assign message IDs: https://review.openstack.org/460112 To understand the full history and context, you’ll want to read the blog post I write last week [1]. The reference lists of the specs also point to some older specs with different proposals that have failed to gain traction in the past. I expect all three proposals to be up for discussion during the logging working group session at the summit/forum, so if you have any interest in the topic please plan to attend [2]. Thanks! Doug [1] https://doughellmann.com/blog/2017/04/20/lessons-learned-from-working-on-large-scale-cross-project-initiatives-in-openstack/ [2] https://www.openstack.org/summit/boston-2017/summit-schedule/events/18507/logging-working-group-working-session [1] http://lists.openstack.org/pipermail/openstack-dev/2017-April/115958.html ________________________________ 华为技术有限公司 Huawei Technologies Co., Ltd. [Company_logo] Rochelle Grober Sr. Staff Architect, Open Source Office Phone:408-330-5472 Email:rochelle.gro...@huawei.com ________________________________ 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁 止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中 的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！ This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!
_______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
