Feature #2269
Updated by neels almost 7 years ago
We want to be able to run OsmoBSC and OsmoMSC instead of OsmoNITB. Add explicit Consider this though: it would make sense to run the same SMS, voice etc. tests independently from whether an OsmoBSC+MSC or OsmoNITB is used. For the resources like BTS and modems, we have the scenarios that allow picking various hardware for the same test API, runs. But for the core network software launched, this is so far still explicit, for the very reason that instead of 'suite.nitb()', a test can call 'suite.bsc()' and 'suite.msc()' and launch those. should be able to start/stop/configure CN components in arbitrarily complex sequences. In this issue, we first want It would be good to have the same powerful selection mechanism for the core network components, i.e. have an abstract API that can operate on both an OsmoNITB or an OsmoBSC + OsmoMSC "backend". More specific tests should still be able to write a separate launch individual processes (have the choice to launch an OsmoBSC directly), but tests could choose to use an "abstract" core network that is then exchangeable between test for run invocations using scenario configurations, without the BSC+MSC way, and accept that need to write each test would have to be written a second time. To have an abstraction of twice (once for NITB vs BSC+MSC, see #2270. and once for MSC + BSC).
