parallel scenario execution
By now we have three BTS models supported but we are still unable to properly execute more than one scenario at a time.
To make this happen the following things need to be done (see checklist).
[x] write NITB/BSC related files to new scenario directory
[x] write BTS realted files to new scenario directory
[ ] make sure two or more scenarios don't collide in some way by using same filesystem paths for files
[ ] make sure each scenario has its own NITB/BSC allocated and does not by some accident share the same instance
[ ] have tcpdump be configured more specifically to listen only to the peers that are part of a scenario
#2 Updated by lazlo over 4 years ago
- Status changed from New to In Progress
- % Done changed from 0 to 40
By now the following has been done:
- NITB/BSC configuration, logs, MNCC socket and HLR files are now located in the scenario directory of the respective scenario being executed * BTS configuration, logs and "bindir" (that is how we call the directory that contains the binaries to be copied to the BTS) are also located in the respective scenario directory.
These changed should make sure that no two scenarios being executed can mix up/overwrite their NITB/BSC/BTS related files. This should somewhat reduce the factors that kept us from being able to execute more than one scenario in the same test session (parallel or sequential is not actually the issue: both didn't work).
So after these changes are now applied and pushed to master, I will try again to run a test session with more than one scenario i.e. as many scenarios as we have BTSes supported. Will start with two (sysmoBTS and nanoBTS) and later include a run which the special BTS with 8-TRXes.