39c0152b7b
* adapted config.yaml to the new feature * temporarly pointing requirement.txt to the lib feature branch * run_kraken.py + arcaflow scenarios refactoring typo * plugin scenario * node scenarios return failed scenarios * container scenarios fix * time scenarios * cluster shutdown scenarios * namespace scenarios * zone outage scenarios * app outage scenarios * pvc scenarios * network chaos scenarios * run_kraken.py adaptation to telemetry * prometheus telemetry upload + config.yaml some fixes typos and logs max retries in config telemetry id with run_uuid safe_logger * catch send_telemetry exception * scenario collection bug fixes * telemetry enabled check * telemetry run tag * requirements pointing to main + archive_size * requirements.txt and config.yaml update * added telemetry config to common config * fixed scenario array elements for telemetry
CI Tests
First steps
Edit my_tests with tests you want to run
How to run
./CI/run.sh
This will run kraken using python, make sure python3 is set up and configured properly with all requirements
Adding a test case
-
Add in simple scenario yaml file to execute under ../CI/scenarios/
-
Copy test_application_outages.sh for example on how to get started
-
Lines to change for bash script
a. 11: Set scenario type to be your new scenario name
b. 12: Add pointer to scenario file for the test
c. 13: If a post action file is needed; add in pointer
d. 14: Set filled in config yaml file name specific to your scenario
e. 15: Make sure name of config in line 14 matches what you pass on this line
-
Add test name to my_tests file
a. This will be the name of the file without ".sh"
-
If any changes to the main config (other than the scenario list), please be sure to add them into the common_config