Whether you want to build the software, run it, grow the community or just learn more about it, there will be content, workshops and design sessions for you to attend at the OpenStack Summit, Oct 15-18 in San Diego. Stick around Friday for the first OpenStack service day, a 1/2 day beach cleanup.
Lots of logging to log files is great and all, and things like rsyslog are too - I mean, we pretty much know how to collect and aggregate the actual log messages into a place where we can see them. BUT - what about the content that we put into the log messages in the first place?
oops - http://pypi.python.org/pypi/oops/0.0.13 - was developed with that problem in production environments in mind. It's a framework for serialization and deserialization of software problem reports, as well as various sets of tools for reporting and analysis.
Since at the moment the main way to track down problems is by trolling through things and doing timing corellation, I'd like to chat about if and how we could make use of oops across the openstack projects. I think it would make tracking down problems in integration tests, as well as in actual production much more straight forward.