In Yoga testing, we are making py3.9 job to run as voting, so
adding py3.9 job as voting.
Also, as openstack-health is branchless and needs to support older
supported stable branches, let's test it with all the
python version supported in those supported stable branches.
For that, we need to explicitly dd the py jobs instead of using
the template. This way, we will explicitly know that we are testing
all supported python versions when the new release template bumps the
min python version in the template.
Change-Id: I894984577bf8c83669c96fd627bb9767237c3f68
Setuptools v54.1.0 introduces a warning that the use of dash-separated
options in 'setup.cfg' will not be supported in a future version [1].
Get ahead of the issue by replacing the dashes with underscores. Without
this, we see 'UserWarning' messages like the following on new enough
versions of setuptools:
UserWarning: Usage of dash-separated 'description-file' will not be
supported in future versions. Please use the underscore name
'description_file' instead
[1] https://github.com/pypa/setuptools/commit/a2e9ae4cb
Change-Id: Ia1a1bc0cf2f8cba9af76b0b22be153f9e96bb6a8
Openstack-health uses horizon nodejs template [1] to run
nodejs10- jobs Which is wrong because openstack-health is
not a horizon plugins and above template is only for horizon
plugins to run node-js jobs.
This patch remove horizon nodejs template from .zuul.yaml
and define a new job to run Nodejs10 jobs on gate.
Also drop support of py35.
[1] https://opendev.org/openstack/openstack-health/src/branch/master/.zuul.yaml#L3
Change-Id: Ia222ce7f52ee1cfd575ed5204088f0eee2fe903e
Now that we are running the Victoria tests that include a
voting py38, we can now add the Python 3.8 metadata to the
package information to reflect that support.
Change-Id: I02dccb26c236506e9383446e7324cae457e92d1b
This repo is now testing only with Python 3, so let's make
a few cleanups:
- Remove python 2.7 stanza from setup.py
- Remove obsolete sections from setup.cfg
- Update classifiers
- Cleanup doc/source/conf.py to remove now obsolete content.
- Use newer openstackdocstheme version
- Remove install_command from tox.ini, the default is fine
Change-Id: Ied0e774f0efda76794ecfb0f67a5fd51bb380258
Previously the wsgi_script openstack-health entry point was pointing
directly to flask app object in the api module. However the script
constructed by pbr attempts to call app and set that as the
application for mod_wsgi. However this is the incorrect usage for a
flask app, and will fail because the app object isn't expected to be
called by itself without any args) Also, according to the flask docs
[1] you just need to set the flask app as the application var in the
to run with mod_wsgi. This commit fixes the wsgi_script entrypoint by
creating a wrapper function which can be called by the generated
output of wsgi scripts from pbr and will return the flask app. This
function is then used as the wsgi_script entrypoint instead of the app
itself. Additionally, this also gives a good injection point if there
are any future initialization or configuration steps that need to be
taken when running.
[1] http://flask.pocoo.org/docs/0.10/deploying/mod_wsgi/#creating-a-wsgi-file
Change-Id: I6e49b4dbbe58e054a28412207b99eb2982a45fbe
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
This commit adss the basic framework for unit tests of the rest api
and 2, yes 2, unit tests to cover the /runs and /tests endpoints.
This will be expanded in the future, but this is to just give us a
starting point as we expand the api.
Additionally, to unblock the repo this adds missing tox envs which
are needed to pass the docs job. It also takes care of the other
missing pieces to pass a build sphinx run.
Change-Id: Id46476285612789e3b7817eacc45125cf6c3a548
This commit adds the basic python infrastructure to the repo. The
backend rest api on top of the data stores will live in the repo
but before we can add that we need to be able to support python code
in the repo.
Change-Id: I869f42e148c2f5c2369fb5613d43b4ec25aaa2db
Ghanshyam Mann