OpenDev Migration Patch
This commit was bulk generated and pushed by the OpenDev sysadmins as a part of the Git hosting and code review systems migration detailed in these mailing list posts: http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html Attempts have been made to correct repository namespaces and hostnames based on simple pattern matching, but it's possible some were updated incorrectly or missed entirely. Please reach out to us via the contact information listed at https://opendev.org/ with any questions you may have.
|3 days ago|
|apache||5 years ago|
|devstack||3 years ago|
|doc/source||4 years ago|
|etc/os_loganalyze||2 years ago|
|os_loganalyze||5 months ago|
|.coveragerc||3 years ago|
|.gitignore||4 years ago|
|.gitreview||3 days ago|
|.mailmap||5 years ago|
|.testr.conf||5 years ago|
|.zuul.yaml||5 months ago|
|CONTRIBUTING.rst||4 years ago|
|LICENSE||5 years ago|
|MANIFEST.in||5 years ago|
|README.rst||2 years ago|
|babel.cfg||5 years ago|
|openstack-common.conf||5 years ago|
|requirements.txt||5 months ago|
|setup.cfg||5 years ago|
|setup.py||3 years ago|
|test-requirements.txt||2 years ago|
|tox.ini||4 years ago|
OpenStack tools for gate log analysis
os_loganalyze is designed as a lightweight wsgi filter for openstack logs, making it easier to interact with them on OpenStack's logs.openstack.org repository. This includes colorizing the logs based on log level severity, having bookmarkable links to timestamps in the logs for easy reference, and being able to filter by log level.
This is implemented as a low level wsgi application which returns a generator so that it can act like a pipeline. Some of our logs are 35 MB uncompressed, so if we used a more advanced framework that required we load the entire data stream into memory, the user response would be very poor. As a pipeline and generator the delay added by this script to the user grabbing the logs is largely not noticeable (< 1s).
Next steps, roughly in order
If you are working on making changes one of the easiest ways to do this is to run the server stack locally to see how your changes look on same data included for the tests.
This can be done with
tox -e run, which will use the script designed for devstack locally pointed at the sample data. A url where you can browse the resultant content will be provided on the command line.