Infrastructure/ansible
1
0
Fork 0
Code Issues Pull requests 6 Projects Releases Packages Wiki Activity Actions

openqa-x86-worker01: update network vars again

Browse source 
We got the interfaces named by biosdevname now, which should be
more stable.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
This commit is contained in:
Adam Williamson 2020-06-10 12:26:50 -07:00
parent 2d5a0ddfe5
commit 7713cab37c
1 changed files with 9 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

18
inventory/host_vars/openqa-x86-worker01.iad2.fedoraproject.org
View file

@ -6,22 +6,22 @@ sudoers: "{{ private }}/files/sudo/qavirt-sudoers"
nrpe_procs_warn: 1400
nrpe_procs_crit: 1600
# the if connected to the infra network on this box is eth0
ansible_ifcfg_infra_net_devices: [ 'eth0' ]
eth0_ip: 10.3.174.21
eth0_nm: 255.255.255.0
# the if connected to the infra network on this box is em1
ansible_ifcfg_infra_net_devices: [ 'em1' ]
em1_ip: 10.3.174.21
em1_nm: 255.255.255.0
gw: 10.3.174.254
# openQA tap worker hosts (like this one) do stuff with ifcfg that base
# doesn't understand. terrible, terrible stuff. seriously - it doesn't
# handle the openvswitch config well. so let's tell it to just configure
# the regular interfaces (which on this system is eth0-3) for us,
# disabling all but the one we want to use (eth0), and leave everything
# the regular interfaces (which on this system is em1-4) for us,
# disabling all but the one we want to use (em1), and leave everything
# else alone. We use a variable definition here so the firewall config
# (in the openqa_tap_workers group_vars) can reuse it.
openqa_tap_iface: eth0
ansible_ifcfg_whitelist: ['{{ openqa_tap_iface }}', 'eth1', 'eth2', 'eth3']
ansible_ifcfg_disabled: ['eth1', 'eth2', 'eth3']
openqa_tap_iface: em1
ansible_ifcfg_whitelist: ['{{ openqa_tap_iface }}', 'em2', 'em3', 'em4']
ansible_ifcfg_disabled: ['em2', 'em3', 'em4']
# Has a hardware RNG
openqa_rngd: True