First explain the different config files and directories, later describe
the schemas used in each of them.
Change-Id: Iaf31808a655a5c77a1dfaa155e86d42585130820
It has been notified that current configuration system is difficult to
understand and to use, so it has been envisioned to refactor it a bit.
The idea is that the user passes a -c path/to/main.conf file, which in
turn contains whatever osmo-gsm-tester main settings supports (basically
what old paths.conf used to be, plus some files harcoded to the same -c
directory are now configurable through the main configuration file).
Change-Id: Ieca65b71b543c44cfcec8e83efd0fe053c432e55
Environment variable OSMO_GSM_TESTER_CONF is marked as deprecated and an
error is logged each time it's used. Same feature is available through
"-c" command line parameters, so having the envvar only makes things
more complex for no good reason. It cannot yet be completely dropped
since some environemnt still make use of it. Give some time to users to
adapt their setups.
Other environment variables setting some config apths can be dropped
since they are not being really used in any setup.
Change-Id: I7eb69f870d0dcb5906d45ae067d6bed1aabf5862
Drop old one in doc/ which contains lots of outadated stuff already
placed in the User Manual.
Write a new markdown README in the root directory with pointers to
places in the repo and the issue tracket, ansible setup, etc.
Change-Id: I9febe56223eaeadc9d31291dd0110a11470e3ab1
It contains simple usual setups to get started with osmo-gsm-tester,
such as creating a 4G network using srsLTE or a 2G network using the
osmocom stack (+ ofono modems).
Change-Id: I55d5b1152da201799af21a77ef6c562f97bd94fc
Commit 12ae6d79a5 switched the rf_dev_type
to be in lowercase but forgot to change these conditions.
Change-Id: I91d3877381b4e6343dc4aa0465e699341ed6648d
example/paths.conf and documentation are updated accordingly.
Test suites should have been moved a long time ago, since the they are
user or setup-specific based on what needs to be tested.
Change-Id: I154b19979b545deba8b232b60172903f63fd9e28
Add a section describing how to clean up and recover osmo-gsm-tester
state after a sigkill is used.
Change-Id: I4841ab6d44a122140e6352df1fb6543418adc033
asciidoc: WARNING: install.adoc: line 450: section title out of sequence: expected level 3, got level 4
Change-Id: I0c881405e66cc6815533bb884016db20cfdff3dc
* Some TODOs are added as comments which actually require code changes.
These are details which showed up as incongruences or missing bits
while writing the documentation for them.
* Some sections are introduced but still waiting to be writen soon:
** Debugging section
** Docker Setup section
** Ansible Setup section
** Troubleshooting (add jenkins red cross button sending kill -9)
** resources.conf attribute list needs to be converted to a table
* Device related setup needs to be updated and extended
* Parametrized scenarios need to be documented
* 4G resources documentation needs to be added.
Change-Id: Ifc2a3c74d45336cc988b76c0ff68a85311e4dd40
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
Pau Espin
Holger Hans Peter Freyther
Oliver Smith
Neels Hofmeyr