openstack-health-nodejs10-run-test-browser job started failing on
chrome browser
- https://bugs.launchpad.net/stackviz/+bug/1909021
Horizon and its plugins also moved the nodejs browser jobs to
firefox now, let's move openstack-health jobs to firefox.
Closes-Bug: #1909021
Change-Id: I06476189c17323101b4904c3da52248ce04bfb83
when running npm test and npm run unit without the chromium-browser
package installed, the tests fail to run[1]. This commit aims to make
the requirement for this package clear to testers.
[1] http://paste.openstack.org/show/727761/
Change-Id: I5685af1160321378829df27f31c0da1724d263ab
This commit adds a new dogpile.cache backend that uses the memcached
distributed locking mechanism to enable async workers but still uses
the dbm file storage. This should enable us to cache large JSON blobs
without worrying about the memacached size constraints, but at the
same time reap the benefits of having an async worker update the
cache in the background. The tradeoff here is configuration complexity
because you still need to install memcached to leverage this.
Change-Id: Ied241ca1762c62a047bd366d7bd105028a884f30
This commit changes how we refresh our cache from doing it directly on
stale requests to do it async in the background with a worker thread.
This leverages dogpile.cache's async_creation_runner mechanism to start
a background thread when the cache goes stale that will update the cache
while still returning the cached copy in them meantime.
To enable this you need to use a dogpile.cache backend that supports
using a distributed_lock. This does not include the default dbm backend,
using a memcached based backend, like dogpile.cache.pylibmc, is
recommended for enabling this functionality.
Change-Id: I0fd29839c72ca2fdfb4c4724bb3da7e283e3d27d
This commit updates the deployment docs with missing sections on
configuring the DB access and the RSS configuration. With this all
the options in the configuration file should be documented now. We
should strive to keep the readme up to date as we add additional
configuration options.
Change-Id: Ifb4d6ad1f9adacbd5a3ab483d8d23063ba815c7b
This commit is the start of adding support for elastic-recheck data
to openstack-health. This will get the bug numbers for the recent
failed runs it's looking at. To actually use this feature it requires
having elastic-recheck installed and a new api config option for the
location on disk of the query files. This does add some install time
complexity especially as eleastic-recheck is only available via git.
The elastic recheck support is optional and will only be activated if
it is present at import time and the config flag telling the api
server where the queries are located on disk is set.
In order to make the response times reasonable when elastic-recheck
support is enabled dogpile caching is used to keep a cached copy
of the recent results list and limit the amount we're querying
elastic search. By default this is configured to use a dbm file
and refresh the cache every 30mins.
Depends-On: Icf203668690419c38f6d6be6b6fe4af8462845f3
Change-Id: Iccd9ec6d62e2249ec7c09d42ec02ea27c71144cc
This commit fixes the description to run only end-to-end tests. The
previous description "npm run e2e" doesn't work with "missing script:
e2e" error.
Change-Id: I3012b926bae3063ab4da5870a4ff37ef4c11fb78
This patch enables code coverage reporting during unit tests via
the `karma-coverage` plugin, and writes them in HTML form to the
`cover` directory where they can be collected as part of the test
job output.
Change-Id: Ic280664eaf5d5f85acfaeb3f54b314129e9ed786
This adds info on how to keep karma server running and watching for file
changes.
Change-Id: I67fca1ab0936297b4d37ce8484eb4db2730c9b1a
Co-Authored-By: Caio Carrara <ccarrara@thoughtworks.com>
This removes initial ``$`` from code lines as most of them didn't have
the dollar sign already (plus it makes it annoying to copy/paste
commands) and normalizes indentation to 4 spaces (again, as most of them
were already formated as such).
Change-Id: I7b77a1fd20134fa5d23a448a17629621ae0a6b05
Plain installing the python package is cumbersome if you're doing any
development as new changes will not be picked up. This updates it to
also mention installing the package in development mode.
Change-Id: I48a402c0c4a98401144cb9cf445aff0a9105d169
There needed to be an extra blank line after the description
for the commands to be formatted correctly.
Change-Id: Ic7f05d1b63ca1997ff0e96d11455c8cb08883c7f
Adding more detailed instructions to get the dev environment working.
Ideally upgrading the node version would be included, but that can
be added later. This will work.
Change-Id: I89c11a57e2191a0d302ac905b90d30ead85bfb4a
When running the rest api under wsgi container you need to pass the
app callable to uwsgi directly. However, the DB connection
initialization was previously done in the main() function which also
called app.run() which would conflict with running under a wsgi
container. This commit breaks the initialization out into the module
level before the app creation. This ensures that the DB initialization
bits are always run regardless of running under uwsgi, gunicorn,
mod_wsgi, or something else. Additionally, the readme is updated to
document how to run the service under uwsgi standalone.
Change-Id: If53b3a1e6fdecd403ebca44809c767caacbde7fe
Ghanshyam Mann