5c14e86d37
ARA is going to bundle a WSGI middleware that allows an operator to route an URL (by default ^.*/ara-report) to the ARA web application. This URL is expected to contain an 'ansible.sqlite' database that would have been uploaded as part of log collection. There are no static files generated as part of this process. The web application reads directly from the database. It is meant to avoid having to generate a static report for each job which does not scale very well for the amount of jobs we are running. For more details, see this code review in ARA [1]. [1]: https://review.openstack.org/#/c/511992/ Change-Id: I3b10c93b4902a9b45e23c227863e472697f662ef |
||
---|---|---|
contrib | ||
doc/source | ||
files | ||
manifests | ||
spec/acceptance | ||
templates | ||
.gitignore | ||
.gitreview | ||
CONTRIBUTING.rst | ||
Gemfile | ||
LICENSE | ||
README.md | ||
Rakefile | ||
bindep.txt | ||
metadata.json | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.md
OpenStack Continuous Integration Module
Overview
Configures an OpenStack Continuous Integration System
Developing
If you are adding features to this module, first ask yourself: "Does this logic belong in the module for the service?"
An example of this is the gearman-logging.conf file needed by the zuul service. This file should be managed by the zuul module, not managed here. What should go in this module is high level directives and integrations such as a list of jenkins plugins to install or a class that instantiates multiple services.