Started by an SCM change14c9fa2a88082da04661495286ae77c266a82aaab7c9fa2a88082da04661495286ae77c266a82aaab7refs/remotes/origin/masterc9fa2a88082da04661495286ae77c266a82aaab7c9fa2a88082da04661495286ae77c266a82aaab7refs/remotes/origin/masterc9fa2a88082da04661495286ae77c266a82aaab7c9fa2a88082da04661495286ae77c266a82aaab7refs/remotes/origin/mastergit://git.osmocom.org/docker-playgroundfalse#14387255update-osmo-ci-on-slaves-dp #1414falsefalse14112771SUCCESS1583090768568https://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves-dp/14/admin2-deb9build- osmo-gsm-tester/ssh/id_rsa.pubosmo-gsm-tester/ssh/authorized_keysosmo-gsm-tester/osmo-gsm-tester.shosmo-gsm-tester/ssh/configosmo-gsm-tester/ssh/known_hostsosmo-gsm-tester/jenkins.shosmo-gsm-tester/resources.confosmo-gsm-tester/Makefileosmo-gsm-tester/Dockerfilemake/Makefileosmo-gsm-tester/ssh/id_rsaosmo-gsm-tester/Release.keyc9fa2a88082da04661495286ae77c266a82aaab71583090580000https://jenkins.osmocom.org/jenkins/user/laforgelaforgelaforge@osmocom.orgIntroduce osmo-gsm-tester docker setup
This set up allows running a typical osmo-gsm-tester set up with a main
unit (ogt-master) attached to one (or more) slaves where resources are
located and processes are run.
As an example, current config allows running an iperf3 test over an
srsLTE stack using the ZeroMQ backend.
Change-Id: Iac7c0b613048ce332642d3957c55cc7c53b56d42
2020-03-01 19:23:00 +0000c9fa2a88082da04661495286ae77c266a82aaab7Introduce osmo-gsm-tester docker setupaddosmo-gsm-tester/ssh/authorized_keyseditmake/Makefileaddosmo-gsm-tester/Makefileaddosmo-gsm-tester/Release.keyaddosmo-gsm-tester/Dockerfileaddosmo-gsm-tester/ssh/id_rsa.pubaddosmo-gsm-tester/jenkins.shaddosmo-gsm-tester/resources.confaddosmo-gsm-tester/ssh/configaddosmo-gsm-tester/osmo-gsm-tester.shaddosmo-gsm-tester/ssh/id_rsaaddosmo-gsm-tester/ssh/known_hosts
githttps://jenkins.osmocom.org/jenkins/user/laforgelaforge