apply rename of resource nitb_iface to ip_address
See osmo-gsm-tester change-id I829903d7b2111ab5ee106bce52d6121204a5a401 Change-Id: Icbbb7d921e7340739883650f778d5a7341840875
This commit is contained in:
parent
97d64d1282
commit
f3981f44bd
|
@ -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
|
||||
|
|
|
@ -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
|
||||
|
|
Loading…
Reference in New Issue