tobiko/tobiko/tripleo
Slawek Kaplonski 67a2bd3faa Add way to know topology is based on containers
It is important in some cases to know if cloud topology is
contenerized (like TripleO) or not (like e.g. Devstack).
In case of contenerized topology, we need for now to skip
radvd related faults test as this isn't run in side car container
so it's gone always when neutron-l3-agent is stopped.

Change-Id: If7f93c21814cfc75cdd3d32900403dc978b53afe
2020-04-24 09:27:05 +02:00
..
__init__.py Create TripleO section in tobiko.conf 2019-08-12 04:49:40 +00:00
config.py Try connecting to undercloud-0 host to verify it exists 2020-03-17 06:09:38 +01:00
containers.py Reduce test_reboot_computes_recovery duration 2020-04-14 14:09:55 +02:00
neutron.py make use of csv files with container state checks 2020-03-07 03:30:32 +02:00
nova.py Add wait_for_all_instances_status for test_reboot_computes_recovery 2020-04-08 09:23:24 +02:00
overcloud.py Resolve overcloud key file path relative to tobiko.conf file 2020-03-11 11:03:46 +01:00
pacemaker.py Fix ovn_resource_healthy function 2020-03-06 08:55:09 +01:00
processes.py fix false : AssertionError: nova agents are unhealthy and 2020-02-27 02:14:24 +02:00
services.py fix services polling and make it more robust 2020-01-03 12:24:12 +00:00
topology.py Add way to know topology is based on containers 2020-04-24 09:27:05 +02:00
undercloud.py Try connecting to undercloud-0 host to verify it exists 2020-03-17 06:09:38 +01:00