Classify tempest-devstack failures using ElasticSearch
Go to file
James E. Blair 338c2135b4 Make pid file configurable
And some other fixups around starting the daemon:
* read config file before forking
* add '-d' option to avoid forking
* default pidfile to /var/run/elastic-recheck/elastic-recheck.pid
* add pidfile option to config file
* switch to python-daemon library (which is the version of the
  lib that the code was expecting anyway)
* use expanduser in the query file path (to match the rest of the
  paths)

Change-Id: I674778ef189cd216a80f74bd449cdc3b12b57a7d
2013-09-30 10:29:32 -07:00
doc/source Apply Cookiecutter to the repo. 2013-09-23 15:27:39 -07:00
elastic_recheck Make pid file configurable 2013-09-30 10:29:32 -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
babel.cfg 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
elasticRecheck.conf.sample Switch queries file to YAML 2013-09-30 08:48:41 -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
queries.yaml Switch queries file to YAML 2013-09-30 08:48:41 -07:00
README.rst Update future work section in README 2013-09-26 08:16:53 -07:00
recheckwatchbot.yaml Make bot.py behave like a daemon 2013-09-18 17:45:12 -04:00
requirements.txt Make pid file configurable 2013-09-30 10:29:32 -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

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