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
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
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
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
If the configured flavor has a disk size of 1 GB, the negative
resize test will fail, because the nova API does not allow
resizing disks to 0 GB.
This patch will instead create a bigger flavor, and resize to the
vanilla one.
Change-Id: I733dab539a3b97a16d0dd14a9bc294c1446c5131
Mixin does a live migration and checks if old host is different
from destination host.
Mixin is used in test_cluster.py and test_vnuma.py.
Change-Id: Ia647b78b24feeba4e6b74ed08a21e8ac0955920d
The test was supposed to create a VM having the configured feature,
and then remove it through resize.
Change-Id: I2c9984f49412ad36f71c4e9da81a6fd6edcf0e43
An optional feature can be defined as a feature that can be turned
off / on through resize (e.g.: vNUMA, RemoteFX, QoS, SR-IOV, PCI
passthrough).
Adds _OptionalFeatureMixin, which contains the following test cases:
* test_feature
* test_resize_add_feature
* test_resize_remove_feature
Adds HyperVvNumaTestCase.
The mixin contains code and tests necessary in order to test
different scenarios / features with cold resize.
The mixins will ensure that the Feature classes they are mixed
into will still behave properly after cold resize.
The mixin contains code and tests necessary in order to
test different scenarios / features with cold migration.
The mixins will ensure that the Feature classes they are mixed
into will still behave properly after cold migration.
Ghanshyam Mann