977271bf11
So we have a record of it that isn't just in my head. Change-Id: I100ab16cc99a75dfd5fa6d3b643eb9957475b0ef |
||
---|---|---|
doc/source | ||
elastic_recheck | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.testr.conf | ||
CONTRIBUTING.rst | ||
LICENSE | ||
MANIFEST.in | ||
README.rst | ||
babel.cfg | ||
elasticRecheck.conf.sample | ||
queries.json | ||
recheckwatchbot.yaml | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.rst
elastic-recheck
"Classify tempest-devstack failures using ElasticSearch"
- Free software: Apache license
- Documentation: http://docs.openstack.org/developer/elastic-recheck
Idea
When a tempest job failure is detected, by monitoring gerrit (using gerritlib), a collection of logstash queries will be run on the failed job to detect what the bug was.
Eventually this can be tied into the rechecker tool and launchpad
Future Work
- Move config files into a seperate directory
- Update sample config files
- Make unit tests robust
- Make pip installable, merge both binaries
- Add debug mode flag
- Split out queries repo
- Expand gating testing
- Cleanup and document code better
- Move away from polling ElasticSearch to discover if its ready or not
- Add nightly job to propose a patch to remove bug queries that return no hits -- Bug hasn't been seen in 2 weeks and must be closed
Main Dependencies
- gerritlib
- pyelasticsearch