diff options
| author | Neels Hofmeyr <nhofmeyr@sysmocom.de> | 2017-05-18 18:38:50 +0200 |
|---|---|---|
| committer | Neels Hofmeyr <nhofmeyr@sysmocom.de> | 2017-05-22 23:59:21 +0200 |
| commit | f3981f44bd4116edd23ba302fe014e6e40102665 (patch) | |
| tree | 84ed1d3455acb4b5c261e814a8ac3571b57532ef /OsmoGSMTester | |
| parent | 97d64d1282a36253c8f192c95e4ba9d939ef5ead (diff) | |
apply rename of resource nitb_iface to ip_address
See osmo-gsm-tester change-id I829903d7b2111ab5ee106bce52d6121204a5a401
Change-Id: Icbbb7d921e7340739883650f778d5a7341840875
Diffstat (limited to 'OsmoGSMTester')
| -rw-r--r-- | OsmoGSMTester/chapters/config.adoc | 4 | ||||
| -rw-r--r-- | OsmoGSMTester/chapters/intro.adoc | 8 |
2 files changed, 6 insertions, 6 deletions
diff --git a/OsmoGSMTester/chapters/config.adoc b/OsmoGSMTester/chapters/config.adoc index f264284..7c06392 100644 --- a/OsmoGSMTester/chapters/config.adoc +++ b/OsmoGSMTester/chapters/config.adoc @@ -75,7 +75,7 @@ where each item has one or more settings -- for an example, see These kinds of resource are known: -'nitb_iface':: +'ip_address':: List of IP addresses to run osmo-nitb instances on. The main unit typically has a limited number of such IP addresses configured, which the connected BTS models can see on their network. @@ -138,7 +138,7 @@ These kinds of resource are known: currently always comp128v1) Side note: at first sight it might make sense to the reader to rather structure -e.g. the 'nitb_iface' or 'arfcn' configuration as + +e.g. the 'ip_address' or 'arfcn' configuration as + '"arfcn: GSM-1800: [512, 514, ...]"', + but the more verbose format is chosen to stay consistent with the general structure of resource configurations, which the resource allocation algorithm diff --git a/OsmoGSMTester/chapters/intro.adoc b/OsmoGSMTester/chapters/intro.adoc index 46c5ec6..8a09910 100644 --- a/OsmoGSMTester/chapters/intro.adoc +++ b/OsmoGSMTester/chapters/intro.adoc @@ -96,7 +96,7 @@ digraph G { subgraph cluster_suite { label = "Suite: sms"; - requires [label="Requirements (suite.conf):\nmodem: times: 2\nbts\nnitb_iface\narfcn"] + requires [label="Requirements (suite.conf):\nmodem: times: 2\nbts\nip_address\narfcn"] subgraph cluster_tests { label = "Test Scripts (py)"; mo_mt_sms @@ -202,7 +202,7 @@ A global configuration of hardware may look like below; for details, see <<resources_conf>>. ---- -nitb_iface: +ip_address: - addr: 10.42.42.1 - addr: 10.42.42.2 - addr: 10.42.42.3 @@ -268,7 +268,7 @@ like this: ---- resources: - nitb_iface: + ip_address: - times: 1 bts: - times: 1 @@ -291,7 +291,7 @@ resources: - type: osmo-bts-sysmo ---- -Which 'nitb_iface' or 'modem' is used in particular doesn't really matter, so +Which 'ip_address' or 'modem' is used in particular doesn't really matter, so it can be left up to the osmo-gsm-tester to pick these automatically. Any number of such scenario configurations can be combined in the form |