Skip to content

Commit 75cdbd0

Browse files
danpawliksauragar
authored andcommitted
Add edpm-ansible-molecule-edpm_kernel for being tested when molecule change
After doing improvements in molecule CI job process [1][2], the edpm_kernel CI job should be working now. [1] #3421 [2] openstack-k8s-operators/edpm-ansible#1048 Signed-off-by: Daniel Pawlik <[email protected]>
1 parent 72060fa commit 75cdbd0

File tree

1 file changed

+24
-7
lines changed

1 file changed

+24
-7
lines changed

roles/test_operator/README.md

Lines changed: 24 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -39,15 +39,13 @@ Execute tests via the [test-operator](https://openstack-k8s-operators.github.io/
3939
* `test_vars`: (String) Testing parameters for this specific stage if a `test_vars` is used the specified parameters would override the ones in the `test_vars_file`. Only parameters specific for the controller can be used (Tempest, Ansibletest, Horizontest and Tobiko).
4040
> Important note! Generally only the variables with the following structure can be used to override inside a stage: `cifmw_test_operator_[test-operator CR name]_[parameter name]`. For example, these variables cannot be overridden per stage: `cifmw_test_operator_default_registry`, `cifmw_test_operator_default_namespace`, `cifmw_test_operator_default_image_tag`. One exception is `cifmw_test_operator_namespace`, which allows running the testing frameworks in multiple namespaces.
4141
* `pre_test_stage_hooks`: (List) List of pre hooks to run as described [hooks README](https://github.com/openstack-k8s-operators/ci-framework/tree/main/roles/run_hook#hooks-expected-format).
42-
* `post_test_stage_hooks`: (List) List of post hooks to run as described [hooks README](https://github.com/openstack-k8s-operators/ci-framework/tree/main/roles/run_hook#hooks-expected-format).
43-
Default value:
44-
```
45-
cifmw_test_operator_stages:
46-
- name: tempest
47-
type: tempest
48-
```
42+
* `post_test_stage_hooks`: (List) List of post hooks to run as described [hooks README](https://github.com/openstack-k8s-operators/ci-framework/tree/main/roles/run_hook#hooks-expected-format)
43+
* `cifmw_test_operator_default_namespace`: (Default: `podified-antelope-centos9`)
44+
* `cifmw_test_operator_default_image_tag`: (Default: `current-podified`)
4945

46+
### Tempest
5047

48+
<<<<<<< HEAD
5149
## Tempest specific parameters
5250
* `cifmw_test_operator_tempest_name`: (String) Value used in the `Tempest.Metadata.Name` field. The value specifies the name of some resources spawned by the test-operator role. Default value: `tempest-tests`
5351
* `cifmw_test_operator_tempest_registry`: (String) The registry where to pull tempest container. Default value: `{{ cifmw_test_operator_default_registry }}`
@@ -78,6 +76,25 @@ cifmw_test_operator_stages:
7876
* `cifmw_test_operator_tempest_resources`: (Dict) A dictionary that specifies resources (cpu, memory) for the test pods. When untouched it clears the default values set on the test-operator side. This means that the tempest test pods run with unspecified resource limits. Default value: `{requests: {}, limits: {}}`
7977
* `cifmw_tempest_tempestconf_config`: Deprecated, please use `cifmw_test_operator_tempest_tempestconf_config` instead
8078
* `cifmw_test_operator_tempest_tempestconf_config`: (Dict) This parameter can be used to customize the execution of the `discover-tempest-config` run. Please consult the test-operator documentation. For example, to pass a custom configuration for `tempest.conf`, use the `overrides` section:
79+
=======
80+
* `cifmw_test_operator_tempest_name`: (Default: `tempest-tests`) — Value used in the `Tempest.Metadata.Name` field. The value specifies the name of some resources spawned by the test-operator role
81+
* `cifmw_test_operator_tempest_test`: (Default: `{{ cifmw_test_operator_tolerations | default(omit) }}`)
82+
* `cifmw_test_operator_tempest_concurrency`: (Default: `8`) — The number of worker processes running tests concurrently
83+
* `cifmw_test_operator_tempest_registry`: (Default: `{{ cifmw_test_operator_default_registry }}`) — The registry where to pull tempest container
84+
* `cifmw_test_operator_tempest_namespace`: (Default: `{{ cifmw_test_operator_default_namespace }}`) — Registry's namespace where to pull tempest container
85+
* `cifmw_test_operator_tempest_container`: (Default: `openstack-tempest-all`) — Name of the tempest container
86+
* `cifmw_test_operator_tempest_image`: (Default: [Refer to `roles/test_operator/defaults/main.yml`]) — Tempest image to be used
87+
* `cifmw_test_operator_tempest_image_tag`: (Default: `{{ cifmw_test_operator_default_image_tag }}`) — Tag for the `cifmw_test_operator_tempest_image`
88+
* `cifmw_test_operator_tempest_network_attachments`: (Default: [Refer to `roles/test_operator/defaults/main.yml`]) — List of network attachment definitions to attach to the tempest pods spawned by test-operator
89+
* `cifmw_test_operator_tempest_tests_include_override_scenario`: (Default: `False`) — Whether to override the scenario `cifmw_test_operator_tempest_include_list` definition
90+
* `cifmw_test_operator_tempest_tests_exclude_override_scenario`: (Default: `False`) — Whether to override the scenario `cifmw_test_operator_tempest_exclude_list` definition
91+
* `cifmw_test_operator_tempest_workflow`: (Default: [Refer to `roles/test_operator/defaults/main.yml`])
92+
* `cifmw_test_operator_tempest_cleanup`: (Default: `False`) — Run tempest cleanup after test execution (tempest run) to delete any resources created by tempest that may have been left out.
93+
* `cifmw_test_operator_crs_path`: (String) The path into which the tests CRs file will be created in
94+
* `cifmw_test_operator_tempest_rerun_failed_tests`: (Default: `False`) — Activate tempest re-run feature. When activated, tempest will perform another run of the tests that failed during the first execution
95+
* `cifmw_test_operator_tempest_rerun_override_status`: (Default: `False`) — Allow override of exit status with the tempest re-run feature. When activated, the original return value of the tempest run will be overridden with a result of the tempest run on the set of failed tests
96+
* `cifmw_test_operator_tempest_tempestconf_config`: (Default: `{{ cifmw_tempest_tempestconf_config }}`) — This parameter can be used to customize the execution of the `discover-tempest-config` run. Please consult the test-operator documentation. For example, to pass a custom configuration for `tempest.conf`, use the `overrides` section:
97+
>>>>>>> 0daf6d11 (Testing my script to update the README.md file to sync variables of tesat-operator role from defaults/main.yml)
8198
```
8299
cifmw_test_operator_tempest_tempestconf_config:
83100
overrides: |

0 commit comments

Comments
 (0)