f6f77354b1
In test_kuryr_restart use one pod to check connectivity to the created pods from this pod instead of assigning a fip for each created pod. This can solve problems when there is shortage of floating ips. Also, Don't fail on deletion of a pod in cleanup if it's not found Change-Id: I55a33f88356ff3d1ef6ed0ce83bb102172e46023 |
||
---|---|---|
.. | ||
README.rst | ||
__init__.py | ||
base.py | ||
base_network_policy.py | ||
consts.py | ||
test_cross_ping.py | ||
test_cross_ping_multi_worker.py | ||
test_daemon.py | ||
test_ha.py | ||
test_kuryr_restart.py | ||
test_namespace.py | ||
test_network_policy.py | ||
test_npwg_multi_vif.py | ||
test_port_pool.py | ||
test_service.py |
README.rst
What are these tests?
As stated in the tempest developer guide, scenario tests are meant to be used to test the interaction between several OpenStack services to perform a real-life use case.
In the case of the Kuryr Tempest Plugin it also involves interaction with Kubernetes pods, so its manager class includes handlers to its python bindings.
A developer using this manager would be able to perform, among others, CRUD operations with pods, alongside Kuryr-K8s added funcionality.