In case of the "virtual" tests we:
* Don't use ofono based modems (they are physical for now).
* Run in an environment that doesn't naturally run a dbus-daemon
Modify the code to memoize the bus by hand.
Change-Id: Ieae4bf819903402f7f715eb489e0a96ed59dc3f8
Create a dedicated resources file for running "virtual" tests. If all
components run on the same machine we can avoid having to manage
separate network.
Change-Id: I0da1267a71dc06fd06f3cf4fc3dcfefda4bcf40b
Bind the mobile's to a random (chosen by the kernel) VTY port. The
CLI option was removed and I added a new VTY command to be able to
specify the port in addition to the address.
Change-Id: Ie40a2ba156ba5674d37a15eb30e5b2527e75fbe7
It's very close to the osmo-bts-trx but without osmo-trx. Modify
the suite to make use of this BTS.
Change-Id: I9f5a2501eb4473ccf2287c902ee207c6a45a1bc5
Add contrib/jenkins-build-manuals.sh, which clones or updates
osmo-gsm-manuals and builds the manuals. When the environment variable
PUBLISH=1 is set, it also uploads them.
Call jenkins-build-manuals.sh from jenkins-run.sh, without PUBLISH=1,
so the manuals get build-tested in the osmo-gsm-tester_gerrit job.
A new job master-osmo-gsm-tester will be added in the future, which
will run PUBLISH=1 jenkins-build-manuals.sh.
The jenkins-build-manuals.sh script does not use the osmo-ci.git
scripts for installing dependencies and cleaning up the workspace.
These scripts are not available on the node, which runs the
osmo-gsm-tester_gerrit job, and it is not trivial to add just them
(without building the osmo-ci Docker image etc.). The only dependency
is osmo-gsm-manuals, and it does not need to be compiled, so it seemed
to be the most maintainable solution to implement the clone/update and
clean up in a few lines of shell code instead.
Related: OS#3385
Change-Id: I4ebfe12a164f807b63bc897aff44db83fc0705bd
PACCH is used for paging only if the MS is actively using a PDCH, and
the only way to be sure that's happening is to place some data through
the GPRS path so MS has TBF in use when the call is placed.
Change-Id: Id29391d75101d94e2cd58f444b383f4c5217ab6a
Storing them inside the testrun directory will most likely violate
the file length limit of the AF_UNIX files. This has happened on
the jenkins test run and can not be mitigated by picking shorter
paths in the code. We are already storing the event server in a
tmp directory and can add subdirs+files there.
Change-Id: I9ba4cd5c3e220ec10fc7c3160d7211daa821358f
nanoBTS doesn't support SDCCH8 in TS!=1 according to osmo-bsc code.
Let's use in this case TCH/H to make sure they are not used for the test
(since we require osmo-bsc to use full rate codecs for the call).
Change-Id: I37f3fe813d4074fbfe64ff3176048e7d25d470e2
If OML IP doesn't need to be changed because it's the one already
configured, then there's no need to set + restart the nanoBTS, which
means we can speed up a test running a nanoBTS by aprox 2 minutes per
nanoBTS used.
Requires osmo-bsc.git 5c2485dcff35996fce328798351af79c0ff4474c, which
fixes json generation in ipaccess-config after -G -q was implemented.
Related: OS#3624
Change-Id: I2871dee3de11512250445127f0b807a8990fd4c6
Update .gitignore and make the manuals build without a toplevel
configure.ac file from autotools:
$ cd doc/manuals
$ make
Related: OS#3385
Change-Id: I5916bc7e656b508fc74917e79841ce7e1ee4981b
Moved to doc/manuals/, with full commit history, in preceding merge commit.
Now incorporate in the build system.
Build with:
$ autoreconf -fi
$ ./configure --enable-manuals
$ make
Shared files from osmo-gsm-manuals.git are found automatically if
- the repository is checked out in ../osmo-gsm-manuals; or
- if it osmo-gsm-manuals was installed with "make install"; or
- OSMO_GSM_MANUALS_DIR is set.
Related: OS#3385
Change-Id: I8a34871948425ea40f40dbb11a59806905e4bed1
Latest changes in osmo-gsm-tester require this import change.
Depends on: osmo-gsm-tester I520bd046cb09042b5567d967f951f050e4e02e85
Change-Id: I0f7f7d0353014b7ef8a0c5a7707c91b2613be79a
It's difficult to understand when it referrs to jenkins job in general
and when it talks about specific jenkins jobs that builds binaries required for
osmo-gsm-tester and the ones which run osmo-gsm-tester.
As a result, it's difficult to understand which sections apply to each
host in case more than one host is used.
Change-Id: I5c882e77b469629028b8d773053783e18f3d1737
This is the one we are usig nowadays in suite.conf, which explicitly
asks to be run with modems supporting sms features.
Change-Id: If5dbc3b4689b282db6fae4668e2838be59e88da8
The osmo-bts-trx tgz doesn't exist anymore and it does not contain
osmo-trx, which comes in its own tgz.
Change-Id: Id803eca3791137b04bc24d195119d5c511fcfc49
* Add sysmocell5000
* Remove 1 modem, showing 2 of them is enough
* Split osmo-bts-trx from osmo-trx node as sysmocell500 doesn't use the
later.
* Update OsmoNITB node to show we also support split openbsc.git
components.
Change-Id: I893beb114d47edd3f67183dd9ea5acc19462496c
The initial goal was to make sure we don't have overall FORCE rules causing
unnecessary rebuilds -- annoying while writing documentation. As I looked
through possible dependencies, I finally understood what's going on here.
Remove code dup and nicely sort which belongs where in build/Makefile.*.inc. In
each, describe in a top comment how to use it, and also unify how they are
used:
- Rename Makefile.inc to Makefile.docbook.inc and refactor
- Add Makefile.vty-reference.inc
- Add Makefile.common.inc
Make sure that we accurately pick up all dependencies.
Drop use of the macro called 'command', that silenced the actual command lines
invoked and replaced them with short strings: it obscures what is actually
going on and makes the Makefiles hard to read and understand.
Each manual's makefile is greatly reduced to few definitions and a Makefile
include, e.g. one for asciidoc, one for VTY reference.
Move common/bsc_vty_additions.xml to OsmoBSC/vty/libbsc_vty_additions.xml, link
from OsmoNITB. It applies only to OsmoBSC and OsmoNITB.
Add a script that combines a VTY reference file with *all* additions files
found in a manual's vty/ dir. Call this from Makefile.vty-reference.inc.
Change-Id: I9758e04162a480e28c7dc83475b514cf7fd25ec0
This section is moved further below in order to have it after section
which explains how to create user jenkins and osmo-gsm-tester group, as
we need this group already created anyway for the config to work
correctly.
Change-Id: I5bdde0a9960f9806f081e9a876b8b66db9e7f37c
* use osmo-bts-sysmo for sysmoBTS systemd service name which is available
since 114293a414bd5b7c86622ec8c293c4034c80d243
* use osmo-pcu for OsmoPCU systemd service name which is available since
241f5bcb00f9c6fee4200a3aea9aa497bf0d3eee
Change-Id: Ie017946b9099460ac6758ff84ec7a10df13390a1
Add instructions to install Java JDK for jenkins build slave.
Minor fixes to SSH key instructions.
Change-Id: Ib2c1adc2ddee3be016e4d253451593b19dbe133a
Simpler systemctl rule to disable stock services.
Fix the limits config, which was not the right way for sysmoBTS.
SSH access: apparently no need to create an ssh key at all, login is permitted
right away.
Add hint to reboot at the right time.
Change-Id: I8e686383318ee2eece908a4e690e5061ade0cd02
Needed to setup the initial hlr db using the hlr.sql file from osmo-hlr
since osmo-gsm-tester commit 798e592fd6
"MSC+BSC: add test api to run OsmoMSC and OsmoBSC with AoIP"
Change-Id: Ic19f93a69df4062364da8523b5d30a1611a0eb77