osmo-ci/ansible/host_vars/osmo-gsm-tester-rnd.yml

---
udhcpd_static_leases:
  - mac: 00:02:95:00:41:b3
    ip: 10.42.42.120

# how many modems are connected via a quadmodem?
gsm_modems: 4
ansible: setup-gsm-tester: use udhcpd as dhcp server Required for ip.access Change-Id: I5ae43ebcd3c87e625110d8ff6afa0476f4b1facf 2018-04-10 14:11:49 +00:00			`---`
			`udhcpd_static_leases:`
			`- mac: 00:02:95:00:41:b3`
ansible: gsm-tester: Assign IP addr in different range to nanobts 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-26 10:49:35 +00:00			`ip: 10.42.42.120`
ansible: gsm-tester: change production gsm_modems to 3 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-06-07 13:24:26 +00:00
			`# how many modems are connected via a quadmodem?`
			`gsm_modems: 4`