osmo-ci - Osmocom Continuous Integration

Age	Commit message (Collapse)	Author	Files	Lines
2019-11-22	ansible: gsm-tester-prod: Set dhcp ip addr for LimeNet-micro board	Pau Espin Pedrol	1	-0/+2
	Change-Id: Ibcdf14ba09ab46240cd6bccac82f7b21f99123ef
2019-09-20	ansible: gsm-tester-rnd: Add nano3g device to static IP DHCP leases	Pau Espin Pedrol	1	-0/+2
	Change-Id: Iaad3e9f5b6b1966322abb89f54611a2368400dcb
2018-11-07	ansible: gsm-tester: prod has now 8 modems attached	Pau Espin Pedrol	1	-1/+1
	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
2018-07-26	ansible: osmo-gsm-tester-prod: Add DHCP lease for secondary muliTRX nanobts	Pau Espin Pedrol	1	-0/+2
	Change-Id: I3967d7b4203f5361dc03074dcd82c870d60c8aac
2018-07-02	ansible: gsm-tester: Assign IP addr in different range to nanobts	Pau Espin Pedrol	2	-3/+3
	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
2018-06-12	ansible: gsm-tester: change production gsm_modems to 3	Alexander Couzens	2	-0/+6
	In the production setup, there are only 3 valid modems. Moving the variable into the host_vars so they can have different amount of modem between rnd & prod. Change-Id: Ic51a14a339bb9be50504a27a724f6f428ee7304f
2018-04-11	ansible: setup-gsm-tester: use udhcpd as dhcp server	Alexander Couzens	2	-0/+10
	Required for ip.access Change-Id: I5ae43ebcd3c87e625110d8ff6afa0476f4b1facf