Project

General

Profile

Actions

Feature #2477

closed

Automate execution and reporting of OsmoMSC interop tests with NG40 core simulator

Added by laforge over 6 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Urgent
Assignee:
Category:
-
Target version:
-
Start date:
08/31/2017
Due date:
% Done:

0%

Resolution:
Spec Reference:

Description

At sysmocom we have a NG40 RAN simulator which is successfully connecting via AoIP to OsmoMSC, and which can run test cases for functional testing and for load testing. Let's automatize the execution of the test cases into jenkins, with public reporting on jenkins.osmocom.org

We might need to move the NG40 machines to the DMZ network (.23.x) similar to the osmo-gsm-tester setup.

We also need to implement a script that can parse the log file VERDICT for each test case and report that as Junit XML to jenkins.

The IUT should consist of (initially) OsmoSTP + OsmoMSC + OsmoHLR, but later probably will be extended with OsmoSGSN + OpenGGSN for the PS side.

I'm not sure what the best strategy is for the rebuilds. We could use something like the Docker images at http://git.osmocom.org/docker-playground/tree/osmo-stp-master - but this is just an idea, up to you to decide what's the best way to move forward.

The goal should be some periodically executed tests. Daniel can help with NG40-getting-started.


Related issues

Related to OsmoBSC - Feature #2478: Manual interop testing with NG40 core simulatorResolveddexter08/31/2017

Actions
Related to OsmoMSC - Bug #2698: Add more tests to jenkins job testing osmo-msc against NG40testerNew12/01/2017

Actions
Actions #1

Updated by pespin over 6 years ago

  • Status changed from New to In Progress
Actions #2

Updated by laforge over 6 years ago

  • Priority changed from Normal to Urgent
Actions #3

Updated by roh over 6 years ago

i move the 2 machines over to the osmocom segment now. the new addresses are in the wiki dokumentation page.
they should be accessible by jenkins now.

Actions #4

Updated by pespin over 6 years ago

Basic setup with 1 test is running in a job from sysmocom's jenkins. We can move the jenkins job to osmocom jenkin's once we define what can be shown there (like ng40tester configs laying in the git repository and then also in the jenkins workspace).

Actions #5

Updated by laforge over 6 years ago

  • Related to Feature #2478: Manual interop testing with NG40 core simulator added
Actions #6

Updated by pespin over 6 years ago

How are we expectred to proceed with this?
Everything is setup in an automated way, sysmocom's jenkins fetches repo from sysmocom's private git repository, updates and builds nightly osmocom and runs osmo-msc on Bob, then it runs NG40 test (only 1 so far) and reports it as junit.

Do we want to move it to osmocom's jenkins instance? In that case, we require moving "config-alice" repo to sysmocom's public git repository. The only things in there which may cause some problems are NG40 config files and some audio files (wav, amr).

If it's fine keeping it in sysmocom's jenkins, then I think we can close this task.

Actions #7

Updated by laforge over 6 years ago

On Fri, Dec 01, 2017 at 11:31:10AM +0000, pespin [REDMINE] wrote:

If it's fine keeping it in sysmocom's jenkins, then I think we can close this task.

yes, let's keep it this way for the time being. Please add a new ticket/task for expanding
the test suite to more comprehensive tests than just a single one :)

Actions #8

Updated by pespin over 6 years ago

  • Related to Bug #2698: Add more tests to jenkins job testing osmo-msc against NG40tester added
Actions #9

Updated by pespin over 6 years ago

  • Status changed from In Progress to Resolved
Actions #10

Updated by laforge about 6 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)