Given these backends are now used in many production environments, they
can no longer be considered experimental.
Change-Id: I9e9f3023bf2a50807540e69b764600c0c5f995d5
This patch allows CloudKitty to use InfluxDB v2 with Flux queries. This
type of query uses less CPU and RAM to be processed in the InfluxDB
backend.
Change-Id: I8ee3c92776aa69afbede353981a5fcd65dd7d099
Depends-On: https://review.opendev.org/c/openstack/requirements/+/895629
Story: 2010863
Task: 48539
To facilitate the switch from Elasticsearch to OpenSearch, the ES
backend has been duplicated and renamed where appropriate to OpenSearch.
The OpenSearch implementation was modified in places for compatibility
with OpenSearch 2.x, for example:
- remove mapping name from bulk API URL
- replace put_mapping by post_mapping
This will allow for the future removal of the Elasticsearch backend.
Change-Id: I88b0a30f66af13dad1bd75cde412d2880b4ead30
Co-Authored-By: Pierre Riteau <pierre@stackhpc.com>
This is an automatically generated patch to ensure unit testing
is in place for all the of the tested runtimes for antelope. Also,
updating the template name to generic one.
See also the PTI in governance [1].
[1]: https://governance.openstack.org/tc/reference/project-testing-interface.html
Change-Id: I32e43aeea8767e5a3b4c30beafb03aa105fa23e6
This adds support for the elasticsearch v2 storage driver to the devstack
plugin. Two non-voting check jobs running a the tempest test suite
against a devstack deployment using the elasticsearch driver have also been
added.
Story: 2006332
Task: 36078
Task: 36080
Change-Id: Ib531f83e2c8e5c2494b36af250d7630e32f49f40
This updates the tempest jobs ran by Zuul. Work items:
* Renamed existing tempest jobs to be more explicit about which storage driver
they're using.
* Introduced two new tempest jobs using the SQLAlchmey v1 storage driver,
one with python2 and one with python3.
Change-Id: I6e30fa6a2dfab322d33fed7ec09cc4fcf9b73858
create a tox environment for running the unit tests against the lower
bounds of the dependencies.
Add openstack-tox-lower-constraints job to the zuul configuration.
See http://lists.openstack.org/pipermail/openstack-dev/2018-March/128352.html
for more details.
Change-Id: Iac8d78c191763121cc580c5cdb070b2673e39c99
As part of Train community goal 'Support IPv6-Only Deployments and Testing'[1],
Tempest has defined the base job 'devstack-tempest-ipv6' (adding
in Depends-On patch) which will deploy services on IPv6.
This commit adds the new job 'cloudkitty-tempest-full-ipv6-only'
run on gate which is derived from 'devstack-tempest-ipv6'.
Verification structure will be:
- 'devstack-IPv6' deploy the service on IPv6
- 'devstack-tempest-ipv6' run will verify the IPv6-only setting and listen address
- 'cloudkitty-tempest-full-ipv6-only' will run the tests.
Story: #2005477
Task: #35884
Depends-On: https://review.opendev.org/#/c/671231/
[1] https://governance.openstack.org/tc/goals/train/ipv6-support-and-testing.html
Change-Id: I214b410137e825b529f0bdc34fda74ed1df091ab
This change adds a basic bandit config for cloudkitty. It can be invoked
by running the tox environment for bandit;
tox -e bandit
These changes also fix potential security issues find during bandit checks.
- binding to all interface: remove useless host_ip option to avoid issue
- hash function issue: switch from sha1 to sha512
- use of exec: can't be removed for moment so using #nosec comment
Change-Id: Iae7d7604457345fe6d482cf48311c9b75fdde947
This updates various parts of the devstack plugin:
* The fetcher is now configurable via the "CLOUDKITTY_FETCHER" variable and
defaults to gnocchi (this allows the user to have immediate results).
* The "CLOUDKITTY_SERVICES" variable was removed as it is not used anymore.
* The storage backend does now default to "influxdb". If this storage backend is
selected, influxdb is installed. This can be done on fedora and ubuntu. The
storage backend to use in devstack can be configured through the
``CLOUDKITTY_STORAGE_BACKEND`` and ``CLOUDKITTY_STORAGE_VERSION`` variables.
* Some details about available variables have been added to the devstack
documentation. Since the "admin/quick_deployment" section did only contain
the devstack documentation, it has been removed for now.
* Given that the "ceilometer-low" archive-policy (default in devstack) only
provides the "mean" aggregation method, it is now the aggregation method
used in the default metrics.yml file.
Change-Id: I37452772de163b5fafc502917af870c86a3d38b2
Since the zuul jobs have been converted to the new format (see commit de4a38e),
the devstack-tempest job is stable. In consequence, this makes this job voting.
Given that the "cloudkitty-devstack-install" job was the same as the
devstack-tempest job without the tempest run, it has been removed in order to
put less load on the gate.
Change-Id: I942f9069eedce033b0b087992f8b84c76149ff1a
This converts the "cloudkitty-install" and "cloudkitty-tempest-full" jobs
to the new zuul job format.
Change-Id: I976405ca59a4fc616fbddf9cecbea4de62fdfa29
This updates cloudkitty's requirement and setup files in order to use
openstack/requirements for constraints. This will help to avoid dependency
conflicts when cloudkitty is deployed in an openstack context.
Work items:
* Updated requirements.txt, test-requirements.txt and setup.py with the
`update-requirements` tool provided by openstack/requirements.
* Added a lower-constraints.txt file.
* Added the "check-requirements" zuul job template to the CI.
Change-Id: I5aab02374523be83a65c8b7f47f1df5e93b5a3d2
Use openstack-tox-cover template, this runs the cover job as
non-voting in the check queue only.
Remove jobs and use template instead.
Fix cover environment.
Change-Id: I4fa5ac5d852544beffb020b30f2f428ebf56b78b
This is a mechanically generated patch to switch the documentation
jobs to use the new PTI versions of the jobs as part of the
python3-first goal.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: I6232924e40edd580ab91109ed48b16bcb96b00e0
Story: #2002586
Task: #24289
This is a mechanically generated patch to complete step 1 of moving
the zuul job settings out of project-config and into each project
repository.
Because there will be a separate patch on each branch, the branch
specifiers for branch-specific jobs have been removed.
Because this patch is generated by a script, there may be some
cosmetic changes to the layout of the YAML file(s) as the contents are
normalized.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: I34e54c3776a15f656335d3108c8c179b7dcc7691
Story: #2002586
Task: #24289
Zuul no longer requires the project-name for in-repo configuration.
Omitting it makes forking or renaming projects easier.
Change-Id: Ibafc8c1ca4335454845c4de43fcc5763050315c4
The gate pipeline should only run voting jobs, non-voting ones get
completely ignored and just waste resources. Remove the non-voting job
from gate pipeline.
Change-Id: I598d0473289e88711ab02a8c4b6aad645ee68ae1
This adds check and gate jobs using the new Tempest plugin to CloudKitty.
The jobs are non-voting for now.
Change-Id: I455eb7208fb97c140b94db9ae53f9da2cd87de82
Matt Crees
OpenStack Release Bot