5569dabadc
Additionally, there was narrowed down amount of security group rules for test_ipblock_network_policy_allow_except test, as it only requires pod to pod connection, so that instead of creating rules for entire wide range (like 0.0.0.0/0 or ::/0) but only for network, which the pods are in. Change-Id: I9e9b2af6404d6cfd3e43e149fd89b8825fa2cb35
Team and repository tags
Tempest Integration of Kuryr
Overview
This project defines a tempest plugin containing tests used to verify the functionality of a kuryr installation. The plugin will automatically load these tests into tempest.
For more information about Kuryr see: https://docs.openstack.org/kuryr/latest/
For more information about Kuryr-kubernetes see: https://docs.openstack.org/kuryr-kubernetes/latest/
For more information about Tempest plugins see: https://docs.openstack.org/tempest/latest/plugin.html
- Free software: Apache license
- Documentation: https://docs.openstack.org/kuryr-tempest-plugin/latest/
- Source: https://opendev.org/openstack/kuryr-tempest-plugin
- Bugs: https://bugs.launchpad.net/kuryr
Installing
Clone this repository and call from the repo:
$ pip install -e .Running the tests
To run all the tests from this plugin, call from the tempest repo:
$ tox -e all -- kuryr_tempest_pluginTo run a single test case, call with full path, for example:
$ tox -e all -- kuryr_tempest_plugin.tests.scenario.test_cross_ping.TestCrossPingScenario.test_vm_pod_pingTo retrieve a list of all tempest tests, run:
$ testr list-tests