Commit Graph

13 Commits

Author SHA1 Message Date
Neels Hofmeyr 765c1d9ce3 default suites: enable osmo-bts-trx (Ettus B210)
Change-Id: I5dce732ed21f34988aa014add4d2d611dd0c44fc
2017-05-29 21:43:10 +00:00
Neels Hofmeyr bef36bc5e3 resources.conf: take out 10.42.42.1
This seems to be the default address used to communicate via SSH with the
sysmoBTS. Whichever process ends up getting this address sees all of the
SSH in its pcap (for the AoIP build it tends to be OsmoHLR).

We could filter properly, but actually also just take this address out of
the pool for allocation to server processes.

Change-Id: I07e74ba0b9a5b08a308aae7646c4b7c70fe4aa0e
2017-05-29 02:54:16 +00:00
Neels Hofmeyr 0e8b900a0f default-suites.conf: run aoip
Change-Id: I0f7d6feec5062c2aaf07eb9a7f543a4a84cb1ff7
2017-05-29 00:19:46 +02:00
Neels Hofmeyr 798e592fd6 MSC+BSC: add test api to run OsmoMSC and OsmoBSC with AoIP
Change-Id: I5842e8f1cba8e8e6bedfc08540efcafe207159cb
2017-05-29 00:19:45 +02:00
Neels Hofmeyr 866d27eb5c resources.conf: more IP addresses
The upcoming BSC+MSC+HLR+MGCPGW style will need four IP addresses. I found six
already configured on the main unit, so adding all of them to our
resources.conf.

Change-Id: Ie0e0ed9bb7fbd87ebe630c32ef59659117d77ed8
2017-05-29 00:18:43 +02:00
Neels Hofmeyr c4ba4a6866 rename more items from nitb to bsc
A NITB is a BSC + MSC, and if a BTS talks to a NITB, it talks to the BSC part
of the NITB. Hence it makes more sense to name certain things 'bsc' instead of
'nitb', to prepare for a separate BSC process appearing soon.

Change-Id: I6a0343b9243b166d4053cc44f523543f1245d772
2017-05-29 00:18:43 +02:00
Neels Hofmeyr 76d8103bfb rename resource nitb_iface to ip_address
I would like to use the IP addresses also for OsmoBSC processes, so it is more
than clear now that 'nitb_iface' was the wrong naming choice.

The only distinction we may need in the future is public versus loopback
interface. To add that, we may add a trait to the 'ip_address' resource
like:

  ip_address:
  - addr: 10.42.42.1
    type: public
  - addr: 127.0.0.1
    type: loopback

This way we can substitute public vs loopback addresses flexibly (e.g. using
scenarios).

Change-Id: I3ad583ae7a33f7a7bb56fe78a125f73c56a0e860
2017-05-29 00:18:43 +02:00
Neels Hofmeyr 095d1290a6 resources.conf: remove unused example BTS
Change-Id: I370789a4dc048cf71c1951f2eb70bfec261583a2
2017-05-25 04:09:20 +02:00
Neels Hofmeyr aca2624273 paths: have one common parent dir /var/tmp/osmo-gsm-tester
In the example config and the jenkins scripts, use paths below common parent
dir /var/tmp/osmo-gsm-tester.

1. example: put the state dir in /var/tmp/osmo-gsm-tester/state, instead of in
the config dir like /etc/osmo-gsm-tester.

2. contrib scripts: place trials in /var/tmp/osmo-gsm-tester/trials, and to
move into place atomically, use /var/tmp/osmo-gsm-tester/.prep-trials as
temporary location.

The OsmoGSMTester manual is currently also being updated to setup these paths,
with /var/tmp/osmo-gsm-tester owned by a common group and having group-sticky
as well has group-writable access rules.

Change-Id: I2961e9d1d9b14859b886058b54ffcb36f4d88bc1
2017-05-11 17:39:02 +02:00
Neels Hofmeyr 56b3d7e685 defaults.conf: use only TCH/F instead of dynamic channels
Let's opt for the oldest/simplest case by default.

Change-Id: I89d634cc51e13bdf6ec157ffb64baa80a469f4c8
2017-05-08 10:43:59 +00:00
Pau Espin b73a1dbbe4 resources: Fix path for gobi_3
Change-Id: I10e5e56b6bec6c0b25db15af75d4cbd60fbbc7d9
2017-05-05 16:02:28 +02:00
Neels Hofmeyr 2831de5790 move /example/suites to /suites
/suites will be the definitive GSM tests collection where everyone should contribute.

Since we're using /example on our current osmo-gsm-tester setup actually as-is,
change paths.conf to point at ../suites.

Change-Id: I7a4d0161d3dcb3a0c723b0b96db85dd032cc2159
2017-05-04 16:42:51 +02:00
Neels Hofmeyr 0cb4522a92 put the example suite in /example, not /selftest/real_suite
Also drop the env file and tweak the README.txt

Change-Id: Ieea274dfd6756498b760c18a5852398cfa396b50
2017-05-04 16:42:50 +02:00