Winstackers project has been retired
- https://review.opendev.org/c/openstack/governance/+/886880
this commit removes the content of oswin-tempest-plugin
deliverables of this project
Change-Id: I489d36a539cb943c1d7216390e469a471719a2cf
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: Idc2841a26f59dc0ba6bf8a24116f5dbcbb059a74
In Zed cycle, we have dropped the python 3.6/3.7[1] testing
and its support. Removing the py36 centos8 job as well as
updating the python classifier also to reflect the same.
Change-Id: I09f5c8abfbf33a628af4f2157164c588e725eac6
Switch to openstackdocstheme 2.2.1 version. Using
this version will allow especially:
* Linking from HTML to PDF document
* Allow parallel building of documents
* Fix some rendering problems
Update Sphinx version as well.
Disable openstackdocs_auto_name to use 'project' variable as name.
Change pygments_style to 'native' since old theme version always used
'native' and the theme now respects the setting and using 'sphinx' can
lead to some strange rendering.
openstackdocstheme renames some variables, so follow the renames
before the next release removes them. A couple of variables are also
not needed anymore, remove them.
See also
http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014971.html
Change-Id: I91b0a362a80ebd37e9bdc3096707851df658e2e7
flake8 new release 3.8.0 added new checks and gate pep8
job start failing. hacking 3.0.1 fix the pinning of flake8 to
avoid bringing in a new version with new checks.
Though it is fixed in latest hacking but 2.0 and 3.0 has cap for
flake8 as <4.0.0 which mean flake8 new version 3.9.0 can also
break the pep8 job if new check are added.
To avoid similar gate break in future, we need to bump the hacking min
version.
- http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014828.html
Change-Id: Ie343a8e748e899196ed543370efe7bf734127163
Update docs building and cleanup:
* Switch to sphinx-build
* Update requirements for Sphinx and openstackdocstheme for
python 3, remove oslosphinx which is dead, create
doc/requirements.txt file
* Remove unneeded doc and translation sections from setup.cfg
* Remove install_command, it's unneeded, the default is fine.
* Move constraints into deps, use TOX_CONSTRAINTS instead of obsolete
UPPER_CONSTRAINTS
* Switch to hacking 3.0, fix problems found
Change-Id: If3c5094d7fbdc9033851024c8e3ae364e4768521
Most of the OpenStack projects have switched to stestr, mostly due
to the fact that testrepository seems to be unmaintained.
We'll do the same for oswin-tempest-plugin, especially since
testrepository no longer handles skip exceptions properly, treating
them as failures.
Change-Id: I27a20bad68fef9f19d46eea4aefcd7e4998fe838
This is a mechanically generated patch to ensure unit testing is in place
for all of the Tested Runtimes for Train.
See the Train python3-updates goal document for details:
https://governance.openstack.org/tc/goals/train/python3-updates.html
Note that since tempest is branchless that we retain py35 support.
Change-Id: I622ef0306ac48509c46e243c83f458e57e496258
Story: #2005924
Task: #34257
This is a mechanically generated patch to add a unit test job running
under Python 3.6 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: Iaa9bde9ddde632edde9158c344cdd4d24a68998e
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: I5c2357e12288e6aa1abef9346d5e6156ebf2c5c7
Story: #2002586
Task: #24345
We want to default to running all tox environments under python 3, so
set the basepython value in each environment.
We do not want to specify a minor version number, because we do not
want to have to update the file every time we upgrade python.
We do not want to set the override once in testenv, because that
breaks the more specific versions used in default environments like
py35 and py36.
Change-Id: Ica0eb93b9b6703f9be57205eaae94cf9e2fb0268
Ceilometer API was removed in Queens, meaning that test_metrics has
not way to validate the metrics collected by the ceilometer-polling
agent.
The metrics are instead sent and collected by Gnocchi.
This patch adds a Gnocchi client, and updates the test_metrics
to use this client properly.
Change-Id: Id999d758505de10abb356befb854736e1904f6ee
The repo and path name is oswin-tempest-plugin, not
oswin_tempest_plugin. Because of this, Devstack fails if this plugin
is included in devstack's local.conf.
Change-Id: I3ea29fc0d9d7c3151c21728daf7345fbeb710b68
This test suite verifies that the instance metrics are properly published
and collected and have non-zero values. The verification is done via the
ceilometer API.
Waiting for the ceilometer compute agent to poll the resources is crucial,
otherwise the test suite will fail due to the fact that no samples would
be found published before checking the samples.
The ceilometer agent's polling interval should have the same value as
the test suite's polled_metric_delay. This can be done in two ways:
a. Configure tempest's polled_metric_delay, by adding the following
line in tempest.conf, in the telemetry section:
polled_metric_delay = <desired value>
b. Set the interval value in pipeline.yaml on the compute node to the
desired value and restart the ceilometer compute agent.
The second method is preferred, as the interval value defined in
pipeline.yaml is 600 seconds, which would mean each test would last
at least 10 minutes.
Change-Id: I2ad696c221fba860a30621686b464b8486bea583
Python allows multiple inheritance, which we use in order to mix and
match test scenarios and actions.
Python performs method resolution as follows:
- checks if the method is defined in the current class.
- if not, check parents, left to right.
Since all tests have test_base as its left-most parent, all methods
are resolved in test_base, which is not the desired behaviour. This
affects optional_feature mixin in particular.
Change-Id: I19d3bdef85a12ef45b600aa4fc68afd390b96c9f
The optional_feature mixin's tests can use the _check_resize
helper method, reducing the code duplication.
Change-Id: I3e3c9be1fe5ba3629e9c7b8db4917c421ce7bd71
Splits the _ResizeMixin into _ResizeMixin and _ResizeNegativeMixin.
Not all test scenarios have negative test scenarios (the cluster tests).
Change-Id: Icab2ebe1233f1bcf4f469d141a8046a5bbbed38e
The test_base's _get_flavor_ref method should be used
when a flavor ref is required. Optional features rely on that
method, as it adds the optional feature as a flavor extra_spec.
The optional_feature's _get_flavor_ref should use the class' _FLAVOR_REF,
not the CONF.compute.flavor_ref. Some tests might require a different
flavor (secure_boot tests).
Change-Id: Ie7f0b0f20fe76a7df5a9b60c8f4c290e810eb2df
In a previous patch, a few extra arguments were added to
wsman's functions, but the argument names were a bit inconsistent,
or not passed correctly. This patch addresses this issue.
Change-Id: I93ee19248bb8fd511d3a42265d936cd2fff2839f