osmo-gsm-manuals needs inkscape to handle svgs. Not all osmo-* projects
are building in docker, so make sure it is also installed on the build
slaves directly.
Related: OS#4314
Change-Id: I63460336d2c4a7594ec9c5c9b60a3d43f0d157aa
Some nodes in the internal network, such as LimeNetMicro, will need
Internet access to upgrade osmo-trx-lms from OBS repos.
It also makes it easier to update manually other nodes inside the
internal network.
Change-Id: I2c89cf9cfcb55b3153e7be212c68ffa8db0f6927
From ansible documentation [1]:
"""
For those used to /usr/bin/chmod remember that modes are actually octal
numbers. You must either add a leading zero so that Ansible's YAML
parser knows it is an octal number (like 0644 or 01777) or quote it
(like '644' or '1777') so Ansible receives a string and can do its own
conversion from string into number.
Giving Ansible a number without following one of these rules will end up
with a decimal number which will have unexpected results.
"""
[1] https://docs.ansible.com/ansible/latest/modules/template_module.html?highlight=template
Change-Id: I91008927c50016a837420c4249b5f69b9153572e
10.42.42.2 is simply one of the IP addresses assigned to osmo-gsm-tester
main unit on its own internal network (the one used between itself and
the connected BTS or helper hosts). There's no DNS server running there.
The main unit already runs lots of services, and there's really no need
for a DNS server running there, so simply point it to a working DNS
server.
Change-Id: I443cc560553c07635763a13bc73ead4835e6a009
It's poky_installer_file, not poky_install_file.
Also, don't mandate a version from april that's no longer on
downloads.sysmocom.de.
This was broken since Change-Id I35f34a089311808cb21a064dd50e41cd1887b320
Change-Id: If3adf078fd89b9d0c5151cdbf745123df34bbaba
Those proprietary libraries are required for testing APER based
protocols such as those spoken on IuCS, IuPS and Iuh.
Change-Id: I07489575d0b71c36b35096ecf1e2aab9577cb43e
Otherwise every time the interface is added (ie when it goes back to
default netns), the generate name changes due to DEVPATH containing
current name at the end of the path.
Change-Id: I87c686caa23a3b39e48e0762d4323a59be7cd4b8
Currently ofono doesn't catch network interface renaming (takes the name
at ofono startup time).
If a modem crashes, its net iface is unregistered and registered again,
and it can happen that the new name is not the same as before (for
instance, wwan8->wwan0 if wwan0 is located on another netns).
These udev rules allow creating persistent unique names to prevent modem
crashes resulting on interface name changing.
dhcpcd is known to race against udev when managing dev interfaces,
bringing them up before udev sometimes, and then udev is unable to
rename it. By denying dhcpcd from managing modem ifaces (ww* and r*
according to kernel/our rules), we get rid of this issue.
Related: OS#3881
Change-Id: Ic3ef75285aa84f9aa606562cd2f6166de186c1a6
This is periodically performed by https://jenkins.osmocom.org/jenkins/job/update-osmo-ci-on-slaves
but in order to get to the point of updating it, we must at least
have done one initial deployment of the repository before. This is
done by the takss in the new osmo-ci.yml
Closes: OS#3773
Change-Id: I581b8713cfdb3ca2ef7f0925730974056981e448
At least with current ansible, this patch is required to avoid
the poky SDK installer waiting indefinitely to somebody answering
his prompts on stdin.
Change-Id: I084a5a152f00bbd484f5616d417fa1486cb79413
4 EC20 modems were attached, and the issue with only 3 out of the 4
showing up was fixed a while ago.
Change-Id: I0e0876fd5581e9eb56c498078ae8cd8c68ede5b5
There is no installable liblimesuite-dev for Debian 8.0 and the
playbook execution fails. Install it for Debian 9.0 or later.
Change-Id: I0cee652b9d9703dc10b6105711a26f33cc2a3fda
To select if some utilities including qemu/debootstrap/fakeroot will be installed.
Usefull for small setups e.g. simtester
Change-Id: I72f4460b8550da191e74a44be0ee3eeb3b2d7769
For small nodes (e.g. simtester) the full blown packages are not required nor supported.
In this case only the jenkins user and the ssh keys will be setted up.
Change-Id: I469a8012b124516bfd9c4d4dd3a3fe0e1ff80bb6
We currently use range around 10.42.42.1-10 for local dynamically
assigned IP addresses (osmo-msc, osmo-bsc, etc.).
The range 10.42.42.50-60 for local statically assigned IP addresses
(to run osmo-bts-trx sysmocell-5k for instance, where the other end
is cofigured with a static dst addr).
For remote addresses, we use IPs in the range 10.42.42.110-120.
Let's create a new range in 10.42.42.120-130 for remote addressess
assigned by udhcpd server.
nanobts assigned assdresses are moved to the latest group to
differentiate them easily and show that they are not IP addr used
locally.
Change-Id: I9eadb0329a670ce6c2254520d9c86bfbdc898b3a
Oliver Smith
Pau Espin
Harald Welte
Alexander Couzens