x/tobiko
Code Issues Proposed changes

Add config option 'run_background_ping_in_pod'

Browse Source 
This new config option can be used to force run background ping process
on the OCP POD, even if used Topology is Tripleo based.
For now running this background ping from the POD is not yet supported,
that will be added in next patches.

This option will be useful to run background ping from the OCP POD
during the adoption CI jobs so that results will be available for tobiko
run before adoption (tripleo topology) and after adoption (podified topology).

Related: #TOBIKO-100
Change-Id: I30f1be9b426af171f1925dc082bd5ff2853f6023
This commit is contained in:
Slawek Kaplonski 2024-11-21 12:32:00 +01:00
parent e40a40bf5b
commit e93eb610c0
2 changed files with 13 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
tobiko/rhosp/config.py
View File

@ -108,6 +108,14 @@ TRIPLEO_OPTIONS = [
help='Dictionary with the node groups corresponding to '
'different hostname prefixes',
default={'ctrl': 'controller', 'cmp': 'compute'}),
cfg.BoolOpt('run_background_ping_in_pod',
default=False,
help='Wheter background ping should be run directly from '
'the undercloud node (default) or using POD on the OCP '
'cluster. The latter is is useful e.g. for the '
'data plane adoption jobs when background ping should '
'be run from the POD even before adoption.'),
]

6
tobiko/tripleo/_topology.py
View File

@ -189,7 +189,11 @@ class TripleoTopology(rhosp.RhospTopology):
return subgroups
def check_or_start_background_vm_ping(self):
tripleo_nova.check_or_start_background_vm_ping()
if CONF.tobiko.tripleo.run_background_ping_in_pod:
tobiko.skip_test("Running background ping in the POD "
"is not implemented yet")
else:
tripleo_nova.check_or_start_background_vm_ping()
class TripleoTopologyNode(rhosp.RhospNode):