osmo-gsm-tester/doc/examples/4g_srsLTE
Pau Espin 8cfb5d020f Remove all references to defaults: timeout: from suite.conf
This feature is not really implemented and maybe never was. In any case,
it makes sense to have that working per-test so we can specify different
values per test in case it's needed.

Change-Id: I3c1b95c10e974da87ec9abd25578d8bcc0bc55a3
2020-06-12 16:12:43 +02:00
..
scenarios Introduce doc/examples/ directory 2020-04-10 19:00:14 +02:00
suites/4g Remove all references to defaults: timeout: from suite.conf 2020-06-12 16:12:43 +02:00
README.md Cmdline arg -c sets main configuration file (old paths.conf) instead of dir containing it 2020-05-12 14:07:29 +02:00
default-suites.conf Introduce doc/examples/ directory 2020-04-10 19:00:14 +02:00
defaults.conf Introduce doc/examples/ directory 2020-04-10 19:00:14 +02:00
main.conf config: suites_dir and scenarios_dir are now a list of paths 2020-05-25 13:33:50 +02:00
resources.conf ms_{srs,amarisoft}: Reuse run_node to hold run info 2020-05-28 13:13:05 +00:00

README.md

This a sample 4G test suite configured and ready to use srsLTE stack. The only thing missing is a trial dir containing binaries.

You can point osmo-gsm-tester.py at this config using the '-c $DIR/main.conf' command line argument, where DIR is the directory path where this README file resides.

If you have your trial with binary tar archives in ~/my_trial you can run the suite for example like this:

osmo-gsm-tester.py -c $DIR/main.conf ~/my_trial

Alternatively you can setup this example as default config for your user by doing something like:

mkdir -p ~/.config
ln -s "$DIR" ~/.config/osmo-gsm-tester

A ./state dir will be created to store the current osmo-gsm-tester state. If you prefer not to write to $DIR, set up an own configuration pointing at a different path (see main.conf: 'state_dir').