Feature #4424
closedosmo-gsm-tester: support parametrized scenarios
90%
Description
The idea is to have something similar to systemd template unit files: https://fedoramagazine.org/systemd-template-unit-files/
Specially for modifiers, one finds the situation where same scenario structure has to be created with lots of different values. For instance, let's say we want to test with different eNodeB num_prb values: [6, 15, 25, 50, 75,100]
Right now we'd need to create one scenario file for each of them, for instance:
mod-enb-nprb6.conf
mod-enb-nprb15.conf
mod-enb-nprb25.conf
mod-enb-nprb50.conf
mod-enb-nprb75.conf
mod-enb-nprb100.conf
And each of them containing something like (changing the num_prb value):
modifiers: enb: - num_prb: 75
Instead, we could have something like:
mod-enb-nprb@.conf
Which should contain:
modifiers: enb: - num_prb: $1
The general syntax would be something like: "scenario-name@param1,param2,param3". that's is @ separate between scenario name and parameter list, and "," separates between parameters. If any param needs a "," inside, then it must be escaped with "\,".
So osmo-gsm-tester, when reading the suite+scenario list (eg, "4g:srsenb-rftype-uhd+srsue-rftype-uhd+mod-enb-nprb@75"), would check the ones containing @, parse the parameters after it, and run the template engine on it to get the final output.
This way with only 1 scenario file we can use it with any possible value (be it any integer number, or a string, or whatever token we want to pass).
Updated by pespin about 4 years ago
- Status changed from New to Feedback
- % Done changed from 0 to 90
Implemented here:
remote: https://gerrit.osmocom.org/c/osmo-gsm-tester/+/17291 Introduce parametrized scenario files support
remote: https://gerrit.osmocom.org/c/osmo-gsm-tester/+/17292 Use parametrized scenario to set ENB num_prb
Updated by pespin about 4 years ago
- Status changed from Feedback to Resolved
Documented. closing ticket.