Commit Graph

5 Commits

Author SHA1 Message Date
Ghanshyam Mann 0976964257 Retire oswin-tempest-plugin: remove repo content
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
2023-09-09 12:30:57 -07:00
Andreas Jaeger 801924705c Update docs building, cleanup
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
2020-05-03 11:55:53 +02:00
Claudiu Belu bce179882a Adds metrics collection scenario
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
2017-11-16 14:02:53 +00:00
Alexandru Muresan 11f87904b2 Add Live Migration Mixin
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
2017-08-31 14:55:49 +03:00
Claudiu Belu 136ef0ac9d Adds cold migration Mixin
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.
2017-07-18 03:26:48 -07:00