Neels Hofmeyr | dae3d3c | 2017-03-28 12:16:58 +0200 | [diff] [blame] | 1 | SETTING UP sysmobts |
| 2 | |
| 3 | PACKAGE VERSIONS |
| 4 | |
| 5 | Depending on the code to be tested, select the stable, testing or nightly opkg |
| 6 | feed: |
| 7 | |
| 8 | To change the feed and packages installed on the sysmobts edit the |
| 9 | following files in /etc/opkg/ |
| 10 | |
| 11 | * all-feed.conf |
| 12 | * armv5te-feed.conf |
| 13 | * sysmobts-v2-feed.conf |
| 14 | |
| 15 | and adjust the URL. For example, to move to the testing feeds: |
| 16 | |
| 17 | sed -i 's/201310/201310-testing/g' /etc/opkg/*.conf |
| 18 | |
| 19 | Then run 'opkg update', 'opkg upgrade' and finally 'reboot'. |
| 20 | |
| 21 | |
| 22 | DISABLE SERVICES |
| 23 | |
| 24 | To use the sysmobts together with the tester, the following systemd services must be disabled |
| 25 | but using the mask and not using the disable option. You can use the following lines: |
| 26 | |
| 27 | systemctl mask osmo-nitb |
| 28 | systemctl mask sysmobts |
| 29 | systemctl mask sysmobts-mgr |
| 30 | |
| 31 | |
| 32 | SSH ACCESS |
| 33 | |
| 34 | Copy the SSH public key from the system/user that runs the tester to the BTS |
| 35 | authorized keys file so the tester will be able to deploy binaries. |
| 36 | |
Neels Hofmeyr | cceb0f5 | 2017-05-10 16:46:26 +0200 | [diff] [blame] | 37 | scp my_key.pub $sysmobts: |
| 38 | ssh $sysmobts |
| 39 | cat my_key.pub >> ~/.ssh/authorized_keys |
| 40 | |
Neels Hofmeyr | dae3d3c | 2017-03-28 12:16:58 +0200 | [diff] [blame] | 41 | It is also advisable to configure the eth0 network interface of the BTS to a |
| 42 | static IP address instead of using DHCP. To do so adjust /etc/network/interfaces |
| 43 | and change the line |
| 44 | |
| 45 | iface eth0 inet dhcp |
| 46 | |
| 47 | to |
| 48 | |
| 49 | iface eth0 inet static |
| 50 | address 10.42.42.114 |
| 51 | netmask 255.255.255.0 |
| 52 | gateway 10.42.42.1 |
| 53 | |
| 54 | Set the name server in /etc/resolve.conf (most likely to the IP of the |
| 55 | gateway). |
| 56 | |
| 57 | |
| 58 | ALLOW CORE FILES |
| 59 | |
| 60 | In case a binary run for the test crashes, we allow it to write a core file, to |
| 61 | be able to analyze the crash later. This requires a limit rule: |
| 62 | |
| 63 | scp install/osmo-gsm-tester-limits.conf sysmobts:/etc/security/limits.d/ |