Skip to content
[Jenkins]Jenkins
log in | sign up

Changes

Summary

  1. osmo-gbproxy-master (derived from osmo-sgsn-master) (details)
  2. Add ttcn3-gbproxy-test-fr for FR related testing (details)
Commit 29f454f2f2c2296b4dcd49bac68a38ddc7deaefb by laforge
osmo-gbproxy-master (derived from osmo-sgsn-master)

Using a separate container will allow us to do gbproxy specific things
like waiting for physical net-devices to show up in the docker netns
before actually starting the osmo-gbproxy executable

Change-Id: I5e6351055ac9430f13e43291cf2a9d52683fe6bf
The file was addedosmo-gbproxy-master/pipework
The file was addedosmo-gbproxy-master/Makefile
The file was addedosmo-gbproxy-master/osmo-gbproxy.cfg
The file was addedosmo-gbproxy-master/Dockerfile
The file was addedosmo-gbproxy-master/docker-entrypoint.sh
Commit b83c28fc34c3cabd8ea51bf9dd7a6981b1efd56a by laforge
Add ttcn3-gbproxy-test-fr for FR related testing

Testing FR support in osmo-gbproxy is a bit more complicated
as it involves the "hdlc" net-devices privded by the hdlc_fr.ko
kernel module.

So we need to
* run on a host with actual hdlc net-devices (e.g. dahdi_dyamic_loc)
* move those net-devices into the containers after starting them
* wait for the net-devices to appear in the containers before starting
  either gbproxy or the test suite

Change-Id: Id4b52877db53cb6e59f6d0d3f754aaae633949e8
The file was addedttcn3-gbproxy-test-fr/jenkins.sh
The file was addedttcn3-gbproxy-test/pipework
The file was addedttcn3-gbproxy-test-fr/GBProxy_Tests.cfg
The file was addedttcn3-gbproxy-test-fr/osmo-gbproxy.cfg
The file was addedttcn3-gbproxy-test/docker-entrypoint.sh
The file was addedttcn3-gbproxy-test-fr/netdev-to-docker.sh
The file was modified ttcn3-gbproxy-test/Dockerfile