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
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
Splits the _ResizeMixin into _ResizeMixin and _ResizeNegativeMixin.
Not all test scenarios have negative test scenarios (the cluster tests).
Change-Id: Icab2ebe1233f1bcf4f469d141a8046a5bbbed38e
test_cluster overrides the test_base's _create_server method, but
it does not respect its signature, leading to issues when flavors are
passed to the method.wq
Change-Id: I6cb0a279bbff653369591246749874b315ed33ab
A new config group is being added, allowing specifying WinRM
credentials to be used when accessing Hyper-V hosts. This will
also allow setting a transport type other than 'plaintext'.
At the same time, this change adds a new helper method that may
be used in order to run commands on the Hyper-V hosts.
Change-Id: I5852154d8275ebd36785bcf56899da3257f1a5a8
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
Hyper-V VMs can be clustered, making them highly available.
We can force a VM failover through WinRM, causing the VM to
restart on another host. For this, the Hyper-V hosts must have
WinRM enabled.
A VM must have network connectivity after the failover,
and operations (resize, migrate, etc.) must still succeed after failover.
Adds the following config options:
- cluster_enabled (default = False)
- username
- password
- failover_timeout (default = 120 seconds)
- failover_sleep_interval (default = 5 seconds)
Adds HyperVClusterTest.
Ghanshyam Mann