Age | Commit message (Collapse) | Author | Files | Lines |
|
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
|
|
Change-Id: I9e3c65342d1bb62d7baa9d589930aa042fb5f7a9
Closes: OS#4279
Related: OS#4246
Depends: osmo-gsm-manuals Ia2c0c833329f8ecab1c427e0d2c002f17ab49a94
|
|
Change-Id: Ibcdf14ba09ab46240cd6bccac82f7b21f99123ef
|
|
Change-Id: Ic314c992f83d9fe1ea6035d67070d7c6004cc9e3
|
|
Change-Id: I6c3b536bee3d1bbd6f526bc3765fc4ad9aa4a0dd
|
|
Change-Id: Iaad3e9f5b6b1966322abb89f54611a2368400dcb
|
|
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
|
|
Change-Id: I31b8f8ea5ed84a676c97ad2f6802be19f0e394d9
|
|
Change-Id: I35f34a089311808cb21a064dd50e41cd1887b320
|
|
Change-Id: Idae47a6529f6a870e29ab688c3479b7ef4ba200a
|
|
Those proprietary libraries are required for testing APER based
protocols such as those spoken on IuCS, IuPS and Iuh.
Change-Id: I07489575d0b71c36b35096ecf1e2aab9577cb43e
|
|
Change-Id: Iaa8802b86429abfaf84fc0f20bd207737dbc9812
|
|
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
|
|
Change-Id: Id62c03b9759367bd5bbe20144e9ad7048d12e61b
|
|
Change-Id: I8d490babb4f1f47e94d15c74a8fba439522e1e18
|
|
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
|
|
Related: SYS#2655
Change-Id: I6198cd14ff86c5d8203d57674a17aa388f21c19d
|
|
Change-Id: I2fa8fa1a195079a0d8beda6a0aa4fc090ca37970
|
|
Change-Id: Iea51362a592c5b42413cb6d72677d01a0e357555
|
|
Change-Id: I188361cceacde60b9b0b954549d63a34ba81646a
|
|
Change-Id: Ia3b52d6fc66efc032b7de4769ad603da177e13da
|
|
Change-Id: I58591ee37c6ec1479778c3f90ed8004a7e2adf1e
|
|
uhubctl doesn't support acting on several hubs from same vendor at once.
Change-Id: I01e698c96240130ed6f632f82383f6020d2a3b81
|
|
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
|
|
Change-Id: I7fb65e3c337fc82c787e925fbbdf9eaf7569defd
|
|
Change-Id: I6e4ad2e3855af7bcefc22d4190cc4e6f58581857
|
|
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
|
|
buster has a liblua5.3-dev, openjdk-8-jre-headless and the ttcn3
packages should work as well.
Change-Id: I76f516bbe503d15d9210ab14e7d9dd024e0ce72f
|
|
These tools are used during gprs data plane setup and performance
testing.
Change-Id: I5beddd74fca726c5ea2c9527836a9f50d92b4ce8
|
|
Change-Id: I32574a935289fa208647d16663b77c0708c0572c
|
|
Related: OS#2308
Change-Id: I587dd5630b211a906351f064c718f8f4c5fe6273
|
|
... which introduces a requirement for libcsv-dev in ansible.
Change-Id: I2ac65947ce9ecc071f774dc4df0f08c99c16c632
|
|
Change-Id: I7fafae340221cac63e33bccabcce6fd8f4385514
|
|
Change-Id: Ia3bd58b98d1e248a92ddd171fb16a23ca8e0b29d
|
|
cmake is required to build LimeSuite, and its not currently installed in
the build slave.
Change-Id: I1808a2394798cd11a0bee8f664c7d18fa71cd5b8
|
|
Change-Id: Ic0fddfc0eaf884cdd5436139675a5a19fafa96b9
|
|
Change-Id: I3967d7b4203f5361dc03074dcd82c870d60c8aac
|
|
Change-Id: Iab74a2b3fc3148bce815b2dadd1fd683c4b64c44
|
|
To select if some utilities including qemu/debootstrap/fakeroot will be installed.
Usefull for small setups e.g. simtester
Change-Id: I72f4460b8550da191e74a44be0ee3eeb3b2d7769
|
|
Pulls a lot of packages
Change-Id: I894455ea779ece84c403f768a1260a1cf2528389
|
|
own file
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
|
|
Change-Id: I878ed30ee2f44d98635511011c17f0f0e986bcc9
|
|
Change-Id: Iedf3b43c164ae7e3e653820284c4d4ddaa545784
|
|
Change-Id: I708960790e330a24c653f162b767d3b3ca4d145d
|
|
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
|
|
Change-Id: I9d22cd6e4d3a3c8c685362bb62cd2a6ef467c461
|
|
Change-Id: I35da5f2276730c7f81d5a1c2e6878ea3e23bca3b
|