Project

General

Profile

Actions

Bug #3208

closed

automatic test setup for OsmoGGSN with kernel-gtp-u

Added by laforge almost 6 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
04/24/2018
Due date:
% Done:

100%

Spec Reference:
Tags:
GTP

Description

We do have some tests in GGSN_Tests.ttcn which are executed at https://jenkins.osmocom.org/jenkins/job/ttcn3-ggsn-test/

However, this runs osmo-ggsn only in userspace mode, i.e. we're not testing the interaction with kernel-gtp-u.

Let's create a setup in which we can test with [various version of the] kernel gtp-u module. I guess this would then mean we're running some qemu-kvm VM with a given kernel + distribution, in which we're running a specified version of osmo-ggsn.

Turning the VM into a jenkins build slave is not a good idea, as that would mean it's not possible to build + restart a different kernel as needed. So we should rather have something like a build slave which then (inside a jenkins job) starts the VM with OsmoGGSN, possibly after rebuilding kernel and/or osmo-ggsn.


Files

.config .config 61.2 KB proposed .config file laforge, 01/19/2021 01:50 PM

Related issues

Related to OsmoGGSN (former OpenGGSN) - Bug #3215: GGSN_Tests.ttcn GTP-U sequence number handling incompatible with kernel GTP-UResolvedlaforge04/25/2018

Actions
Related to Linux Kernel GTP-U - Feature #1943: test setup for Linux kernel GTP-U tunneling moduleResolvedosmith02/06/2017

Actions
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)