os-hosts CLIs and python API bindings had been deprecated from
python-novaclient 9.0.0 and finally became removed in 10.0.0 release.
The related scenarios become redundant. We cannot launch then in gates
and it is impossible to ensure that they work even with old novaclient
release. Since it is not something critical and what is called regulary
in old OpenStack environments we should not provide any workaround and
can just remove the os-hosts logic from Rally.
[*] https://github.com/openstack/python-novaclient/blob/master/releasenotes/notes/remove-hosts-d08855550c40b9c6.yaml
Change-Id: I915983dbc634dafcab1cc54dba7bae8d4e368884
ElasticSearch exporter assumes that success_rate from workload stats
is a string with numeric value from 0 to 100 + '%' char in the end.
It is not always True. For example in case of failure in contexts, the
workload inself will have "n/a" success rate.
This patch covers the case
Change-Id: If8380febc65f6f92331ef1137aa83301a81200a9
This scenario, executed concurrently, should be able to trigger any IP
allocation race conditions in database layer of Neutron IPAM layer.
Change-Id: Icecfcd255fb83250cb77e8505f6b4846e005725c
It fails on fedora25 with system gssapi package installed with the
following error:
AttributeError: 'module' object has no attribute 'GSSException'
It happens because of: https://github.com/paramiko/paramiko/issues/584
that will be fixed with https://github.com/paramiko/paramiko/pull/861
that is not released or even merged yet.
It's better to isolate the venv from system libraries that may be
incompatible with paramiko.
Change-Id: I98af75bb01fa42a2902a850de1b974abc982d432
Tempest team switched from `testr` to `stestr` tool. `stestr` is
modified version of original `testr` and has the similar interface.
The support of a new tool can be easily integrated in the currect
TestrRunner
Change-Id: Ibcb949ad98323f770bf20f144ad66b4a47c00e22
Rally <0.10.0 was hardcoded to support only OpenStack platform. That is
why deployment config had a flat schema (i.e openstack credentials were
at the same top-level as other properties).
Rally 0.10 includes an attempt to unify deployment component for
supporting multiple platforms. The deployment config was extended with a
new top level property `creds` which was designed to include credentials
for different platforms.
Since Task and Verification components used deployment.credentials object
from database instead of using deployment config directly, Rally 0.10 did
not provide a database migration of deployment config.
While developing Rally 0.11.0 with new Environment component, we made a
wrong assumption and forgot about an old format. That is why a
7287df262dbc migration relied on "creds" property of deployment.config
If the database was created before Rally<0.10, the introduced assumption
leds to KeyError failure[0] for old deployment configuration:
File ".../7287df262dbc_move_deployment_to_env.py", line 137, in upgrade
and (set(spec["creds"]) == {"openstack"}
KeyError: 'creds'
To fix this issue, we need to disable 7287df262dbc migration, introduce
a new migration for an old deployment format, return the code of
7287df262dbc in a new migration.
NOTE: This commit introduces several migrations at once. These
migrations have downgrade methods which are not tested(we do not support
downgrade, but these methods are mandatory). To make CI happy with these
uncovered by unit tests lines we need to temporary increase the magic
number in coverage job.
Change-Id: I475fd1b0f14af923552d92da87df09c26b81bb7a
- Remove usless abstraction of db.api
- Split API methods to schema management and just record related ops
- Remove part of oslo.db and oslo.utils dependency (need one more patch)
- Improve performance & refactor mulitple requests
Change-Id: I56ca311ea354409e9b19511dca77cda27be5d52b
The new release of kubernetes python client improved the validation,
so we need to ediot our test to create the right fake objects.
As well, kubernetes.client.ConnectionObject was renamed to just `Connection`
and we should handle this.
Change-Id: I1a3275a8a5a3d729ce507689ab38e3c3d54d3c77
1. e.g. When doing ovn-scale-test; to list the lswitches on northbound
database on the controller, self.run is not returning the data back.
Hence this commit fixes it.
Change-Id: I6c5e2c935430641586f204142cb3de00925770c1
This patch is based on [1] and adds following scenarios:
GnocchiArchivePolicyRule.list_archive_policy_rule
GnocchiArchivePolicyRule.create_archive_policy_rule
GnocchiArchivePolicyRule.create_delete_archive_policy_rule
[1] https://review.openstack.org/#/c/453861/
Change-Id: I3d2104fa6f6ba4bd90c4ac1771e48c32a5403832
Signed-off-by: Juha Kosonen <juha.kosonen@nokia.com>
* Make hook tests pass on any platform
* Fix Task Import tests (not sure why they worked before)
* Reduce the time required to run tests
* Use getjson where suitable
* Use no_logs where logs may cause problems
Change-Id: Iae927760152c2e1ca2a4622762b33a57f1070945
Sync our requirements with global openstack requirements.
Also, include uc for not direct rally dependencies
Change-Id: Ia1f0bf2cfbef75214ec66a8551bdfb5e84f90542
As for config options we are using oslo_config library.
It limits us to override config options based on used deployment/env.
To get control of all options and how they are obtained, let's restrict
usage of oslo_config directly and force everyone to use rally.common.cfg
which has the same interface.
Change-Id: Ia845958b50b62d971f1343c03da2552049aa4363
The info method of existing@openstack returns a dict with information
about available services. The key isservice types, the value is
service name. It is convenient for code usage, but not obvious for the
users, as much as "__unknown__" service name.
This patch changes the format to be a list of dicts. Each dict is a
representation of available service. The service type is represented via
"type" field and name (if available) is represented via "name" field.
Also, the new format allows to provide more info about services in
future.
Change-Id: I4be4468d4a78ceb43e1bfa97c35c396606aa4da2
* Port rally.task.engine to use EnvManager instead of Deployment
* Rename method `set_deployment` of `rally.common.objects.Verifier`
to `set_env`. It can be done in backward incompatible way, since the
original method should be called only from rally.api
* Extend `rally.common.objects.Verifier` with `env` property
* Move OpenStackCredential under dict parenthood. object like style
makes things too complicated. The simple dict should give more
transparency. As for backward compatibility old-behaviour is kept.
* Call `check_helth` method of EnvManager from TaskEngine instead of
hardcoded for openstack `verify_connection` method.
* Remove methods `get_validation_context` and `verify_connection` from
OpenStackCredential. It should not be called anywhere.
Change-Id: I76608deaefc68dbd5a99a3339584c9cf70e16ba0
