Classify tempest-devstack failures using ElasticSearch
Go to file
Joe Gordon 977271bf11 Update future work section in README
So we have a record of it that isn't just in my head.

Change-Id: I100ab16cc99a75dfd5fa6d3b643eb9957475b0ef
2013-09-26 08:16:53 -07:00
doc/source Apply Cookiecutter to the repo. 2013-09-23 15:27:39 -07:00
elastic_recheck Further shuffling to get this to fit the standard code layout 2013-09-25 18:20:51 -07:00
.coveragerc Apply Cookiecutter to the repo. 2013-09-23 15:27:39 -07:00
.gitignore Apply Cookiecutter to the repo. 2013-09-23 15:27:39 -07:00
.gitreview Apply Cookiecutter to the repo. 2013-09-23 15:27:39 -07:00
.testr.conf Apply Cookiecutter to the repo. 2013-09-23 15:27:39 -07:00
CONTRIBUTING.rst Apply Cookiecutter to the repo. 2013-09-23 15:27:39 -07:00
LICENSE Apply Cookiecutter to the repo. 2013-09-23 15:27:39 -07:00
MANIFEST.in Apply Cookiecutter to the repo. 2013-09-23 15:27:39 -07:00
README.rst Update future work section in README 2013-09-26 08:16:53 -07:00
babel.cfg Apply Cookiecutter to the repo. 2013-09-23 15:27:39 -07:00
elasticRecheck.conf.sample Add ssh key to config file 2013-09-19 12:12:10 -04:00
queries.json Add query for bug 1230407 2013-09-25 18:50:55 -07:00
recheckwatchbot.yaml Make bot.py behave like a daemon 2013-09-18 17:45:12 -04:00
requirements.txt Add launchpadlib to requirements 2013-09-23 19:02:53 -07:00
setup.cfg Further shuffling to get this to fit the standard code layout 2013-09-25 18:20:51 -07:00
setup.py Apply Cookiecutter to the repo. 2013-09-23 15:27:39 -07:00
test-requirements.txt Apply Cookiecutter to the repo. 2013-09-23 15:27:39 -07:00
tox.ini Apply Cookiecutter to the repo. 2013-09-23 15:27:39 -07:00

README.rst

elastic-recheck

"Classify tempest-devstack failures using ElasticSearch"

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