aboutsummaryrefslogtreecommitdiffstats
path: root/ttcn3-gbproxy-test-fr
AgeCommit message (Collapse)AuthorFilesLines
2024-03-25ttcn3-*-test: set OSMO_SUT_{HOST,PORT} for more testsuitesVadim Yanitskiy1-0/+2
Let's also retrieve talloc reports for these testsuites. Change-Id: Iaa94dd200fdb98962b784cb507c9995096232dc9
2023-01-30FR testsuites: clean up all networks before startOliver Smith1-0/+1
Add a new network_clean_remove_all_ttcn3 function and use it in the fr related testsuites to ensure no network is running before the test starts. We just had the situation where the network link between gtp0-deb10fr (where these testsuites run exclusively, and only one at a time) and the jenkins host went down. And so the clean up trap apparently did not run and starting a new test fails as the old network still exists and has the network devices attached. Related: OS#5802 Change-Id: I6a9464a11edcba978be08764bec9de19760a5c77
2023-01-16network_create: find free subnet automaticallyOliver Smith1-3/+3
Try multiple subnet numbers until successfully creating a network. This way we can run the same ttcn3 testsuite multiple times in parallel without conflicts (e.g. once against latest, once against nightly). Also we don't need to make sure each new testsuite has a unique subnet number anymore. I've considered also adjusting network_bridge_create, but that gets used exclusively by osmo-ran/jenkins.sh, a script which we don't actually run in jenkins. It seems that in this script it makes more sense to not get a random subnet number. Related: OS#5802 Change-Id: I57152b08ef0f38e17e7019a8df032189b03f56cf
2021-11-26ttcn3: write Osmocom repository to configsOliver Smith1-0/+1
Write a line like 'Misc_Helpers.mp_osmo_repo := "nightly"' into the TTCN-3 config file (e.g. BSC_Tests.cfg), before starting the testsuite. This allows executing different code paths in the tests based on the repository. Related: OS#5327 Change-Id: Ic06532f7a67e59458652c5cf4c8f6fee8113e703
2021-05-28ttcn3-gbproxy-test*: Update gbproxy NS timersDaniel Willmann1-3/+3
Change-Id: I7d436327bb57a3f6c6b071c28308c8a74561d93c Related: OS#4952
2021-04-25remove deprecated 'logging level all everything' from configsHarald Welte1-1/+1
it has been deprecated in libosmocore.git 2.5 years ago: commit 7e0686c6b4b456ec4e6e15689694b1bcf96c301f Author: Neels Hofmeyr <neels@hofmeyr.de> Date: Mon Sep 10 20:58:52 2018 +0200 Change-Id: Ia6946fae497319a894d4e664ac8642340620822e
2021-04-09gbproxy: Add mp_gbproxy_ip to check BVC FSM stateHarald Welte2-0/+4
In docker-playground.git I272e43b9be8ba53d8a815e8ab099c939f63413a7 we introduce FSM state introspection and we need to add the CTRL hostname here. Change-Id: Idcd77353a661cfc1685ded64b5993ff63637addc
2021-02-26*/jenkins.sh: set -e after setting clean up trapOliver Smith1-0/+1
Abort the script and trigger the clean up script, whenever any of the commands below to prepare the testsuite are failing. This saves time with figuring out why suddenly all or most tests are failing, and avoids running the entire testsuite on jenkins if it's obviously not going to work. Related: OS#3208 Change-Id: Ie68da2affda8c96b3a515a857a921a05f1bf8ef7
2021-02-26jenkins-common.sh: add common clean up trapOliver Smith1-6/+2
Add set_clean_up_trap() in jenkins-common.sh and run it at the beginning of the jenkins.sh files. Move the common clean up code from the end of every jenkins.sh file into clean_up_common(), which gets called by the trap. Add a custom clean_up() function to those jenkins.sh files that need additional clean up. Replace explicit container stop commands (for containers attached to the docker network) with one call to network_clean() in clean_up_common(). It kills all containers attached to the docker network. The motivation for this change is the upcoming optional build of initrd and kernel during ttcn3-ggsn-test/jenkins.sh. After building these, a short smoke test will be performed to make sure we can boot the kernel and initrd, before continuing to run the entire testsuite against it. If building or the smoke test fails, we must do a proper clean up of the network and fix permissions. Related: OS#3208 Change-Id: I807c6221d22fec31db23e2516e477a3eb43347fb
2021-02-25Remove test backward compatibility with older osmo-* versionsPau Espin Pedrol1-5/+0
These changes are no longer needed since master versions of whole CNI have been recently released. Related: OS#5042 Change-Id: I6f491b58d4576b22c8ff3ab56a7b9e17163a8739
2021-02-16gbproxy: update sns configuration to use ip-sns-bindAlexander Couzens1-0/+2
With libosmocore commit the SNS configuration requires a ip-sns-bind vty configuration to define the binds which should be use. Related: SYS#5354 Depends-on: I9ab8092bf286e7d90e92f5702a5404425e959c84 (libosmocore) Change-Id: I11541540468584fc17a18fa294da5c9813c28d64
2021-02-16ttcn3-gbproxy-test: remove broken merge logs cmdOliver Smith1-12/+0
Remove commands that result in a docker error message, like in Ie6f8270230e1f0372b63d610b7868ea8719b18ad. Change-Id: I9dec8d27c0f09cd8ee75255c8dfa314c70387ee9
2021-02-10gbproxy: Fix ip-sns VTY configDaniel Willmann1-2/+2
Change-Id: I8faa5d29bfffe50c76c1b907717144ff893126a3 Related: SYS#5354 Depends: Ida979f3b9daa5f7280a629441e4006a7635653b0 (libosmocore.git)
2021-02-04Add osmo-gbproxy-* container for osmo-gbproxyDaniel Willmann1-1/+0
Uses the new repo split off of osmo-sgsn Related: OS#4992 Change-Id: I1e7ede4d1da54e3bcb286213b34401bd9dcf7cc1
2021-01-21osmo-gbproxy: fix configurationHarald Welte2-22/+6
also, only change those values from their default values that are neccessary to change; fall-back on the defaults whenever possible. Change-Id: I5fba21ddf1854ed2b4f829785ab016dfa284456e
2021-01-21gbproxy: Use separate NS-VC for data + signalingHarald Welte1-0/+22
This follows the change implemented in osmo-ttcn3-hacks.git If0e404bdf2c30a5e18748695608611be83f61109 to use data-only and signalling-only NS-VCs on the SGSN side Change-Id: I58f8a6d1c8d01551d366bd7d0dbfb892cce512ae Requires: osmo-ttcn3-hacks.git If0e404bdf2c30a5e18748695608611be83f61109 Related: OS#4953
2021-01-21gbproxy,pcu,sgsn: Update config filesHarald Welte1-2/+6
In upstream I9798e639b4bc8658482945970775b012b5840779 we introduce two additional fields per NSVC (data_weight, signalling_weight). Make sure those are specified everywhere. Related: OS#4953 Requires: osmo-ttcn3-hacks.git I9798e639b4bc8658482945970775b012b5840779 Change-Id: Ic607b3edc3bf724a8b2dbd6be8c806002c229509
2021-01-17gbproxy: Update configs for SGSN poool with 2 SGSN, NRI, ...Harald Welte2-1/+22
Change-Id: Iac57e079d1375f186ddc200471bad1fa622c8860
2021-01-12make osmo-gbproxy.cfg in ttcn3-gbproxy and ttcn3-gbproxy-fr to look similiarAlexander Couzens1-12/+12
Reduces human error when changing the configruation for both cases. Change-Id: I807589cc04f23d483695467320d34d79eaf5d290
2021-01-12ttcn3-gbproxy-test-fr: fix SNS ip addressAlexander Couzens1-1/+1
Change-Id: Iba5aee47fb237884d4b0238b9cef4e2370e7ce09
2021-01-11gbproxy-fr: Enable IP-SNS towards SGSNAlexander Couzens2-1/+2
Change-Id: Id59cc404c355a3f494ad60be8d3a499b217084ec
2021-01-08ttcn3-gbproxy-test: Fix pcap capture with dumpcapDaniel Willmann1-1/+1
In commit 2279aac6 dumpcap is used to capture pcaps, but dumpcap fails if the directory isn't writable for everyone. Commit 62ac27779 only fixed this issue for frame relay, this simply mirrors the change for ttcn3-gbproxy-test Change-Id: I11dcf9efd0b06544a82e31dec03fe76e182fd0d3 Related: OS#4518 SYS#5115
2021-01-05ttcn3-gbproxy-test: Fix osmo-gbproxy configDaniel Willmann1-18/+34
Change-Id: If6fd41d0cecb807f002d87e18d4b0d80f41977ef
2020-12-30osmo-gbproxy: Change config file to comply with change in upstreamHarald Welte1-1/+1
In osmo-sgsn Change-Id Id67592aa7712e5e04e7264b2fb8f26d57eb7e69e we have changed the config file syntax and must adjust here accordingly. Change-Id: I8770baac2298ee9a71d7428ea30600751783b4f9 Depends: osmo-sgsn Id67592aa7712e5e04e7264b2fb8f26d57eb7e69e
2020-12-11gbproxy-test-fr: Avoid dumpcap failing to write to /dataHarald Welte1-0/+2
Change-Id: I73dbdb4d85342e5fccd5ea4d9927f3244293d718
2020-12-11ttcn3-gbproxy-test-fr: depend also on osmo-sgsn-masterHarald Welte1-0/+1
osmo-gbproxy-master is derived from osmo-sgsn-mater, and the former needs to be re-built to catch up with osmo-sgsn.git changes (Where the osmo-gbproxy source code is located) Change-Id: I8abc9f89d19d657403569b7705cd923342ff300b
2020-12-09ttcn3-gbproxy-test-fr: Fix hdlcnet device namesHarald Welte1-4/+4
In Change-Id I80de01c96185c60fe2de7a8ffa9daed2669658e1 we introduced the wrong hdlcnetX device names. We must use each devoce only once, rather than trying to use hdlcnet1..4 twice. Change-Id: I56f75995fe94b46b0210de2a4f83e384b4e4ca4f
2020-12-09gbproxy-test-fr: Fix syntax error in config fileHarald Welte1-1/+1
It's mp_enable_bss_load_sharing, not mp_enable_load_sharing Change-Id: I0d2241e0d9e376f27d04721034b1e197901aa662
2020-12-08gbproxy: Enable test of load-sharing when running over FRHarald Welte1-0/+1
Change-Id: I2ce1f67dc8f45f7a62a923e45fb479c4c482eec9 Depends: osmo-ttcn3-hacks.git I96e8b6a1a69148f770476e87c920dc256c1d7379 Related: OS#4520
2020-12-08gbproxy: update ttcn3 configuration to reflect osmo-gbproxy.cfgHarald Welte1-20/+45
In Change-Id I80de01c96185c60fe2de7a8ffa9daed2669658e1 we updated only the osmo-gbproxy.cfg, but noth the GBProxy_Tests.cfg for the test suite, which of course won't work. Change-Id: I35603dc76926d76e57993f7eab1354eea8d25dad Related: SYS#5226
2020-12-04ttcn3-gbproxy-test-fr: Catch up with config changesDaniel Willmann1-4/+8
Change-Id: I80de01c96185c60fe2de7a8ffa9daed2669658e1 Related: SYS#5226 Depends: I698a932b3dc78c776e9350283109463bcdc40e6b (osmo-ttcn3-hacks)
2020-11-30Add ttcn3-gbproxy-test-fr for FR related testingHarald Welte4-0/+271
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
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-30 12:40:36 +0000