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
2013-09-23 15:27:39 -07:00
2013-09-23 15:27:39 -07:00
2013-09-23 15:27:39 -07:00
2013-09-23 15:27:39 -07:00
2013-09-23 15:27:39 -07:00
2013-09-23 15:27:39 -07:00
2013-09-23 15:27:39 -07:00
2013-09-30 08:48:41 -07:00
2013-09-30 10:29:32 -07:00
2013-09-23 15:27:39 -07:00
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
Description
Classify tempest-devstack failures using ElasticSearch
Readme 14 MiB
Languages
Python 53.3%
JavaScript 38.1%
HTML 7.5%
Makefile 0.5%
CSS 0.4%
Other 0.2%