readme: add some ssh details
Change-Id: Idb5d254768b52300d99b5a1f11f92e8536aec371changes/75/2575/2
parent
47de6b0a24
commit
cceb0f56ab
|
@ -34,6 +34,10 @@ SSH ACCESS
|
|||
Copy the SSH public key from the system/user that runs the tester to the BTS
|
||||
authorized keys file so the tester will be able to deploy binaries.
|
||||
|
||||
scp my_key.pub $sysmobts:
|
||||
ssh $sysmobts
|
||||
cat my_key.pub >> ~/.ssh/authorized_keys
|
||||
|
||||
It is also advisable to configure the eth0 network interface of the BTS to a
|
||||
static IP address instead of using DHCP. To do so adjust /etc/network/interfaces
|
||||
and change the line
|
||||
|
|
|
@ -95,6 +95,17 @@ possibly other) hardware: place the main unit's public SSH key on the sysmoBTS.
|
|||
Log in via SSH at least once to accept the BTS' host key.
|
||||
|
||||
|
||||
Jenkins Configuration
|
||||
|
||||
(TODO: jenkins build slave details)
|
||||
|
||||
When adding an entry to jenkins' known_hosts file, be aware that you need to
|
||||
add an actual RSA host key. Using 'ssh' to access the main unit may work, but
|
||||
jenkins will still fail to access it in the absence of a full RSA host key:
|
||||
|
||||
ssh-keyscan -H $my_main_unit_ip_addr >> ~jenkins/.ssh/known_hosts
|
||||
|
||||
|
||||
LAUNCHING A TEST RUN
|
||||
|
||||
osmo-gsm-tester watches /var/tmp/osmo-gsm-tester for instructions to launch
|
||||
|
|
Loading…
Reference in New Issue