openqa: tweak x86 worker 04 network variables

Primary interface names are ethX, have to use those for firewall
config to work right.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
This commit is contained in:
Adam Williamson 2020-10-06 12:23:53 -07:00
parent 73363264b6
commit 8bd17b0e15

View file

@ -6,10 +6,10 @@ 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 eno1
ansible_ifcfg_infra_net_devices: [ 'eno1' ]
eno1_ip: 10.3.174.24
eno1_nm: 255.255.255.0
# the if connected to the infra network on this box is eth1
ansible_ifcfg_infra_net_devices: [ 'eth1' ]
eth1_ip: 10.3.174.24
eth1_nm: 255.255.255.0
gw: 10.3.174.254
dns: 10.3.163.33
nm: 255.255.255.0
@ -17,13 +17,13 @@ nm: 255.255.255.0
# 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 em1-4) for us,
# disabling all but the one we want to use (em1), and leave everything
# the regular interfaces (which on this system is eth0-3) for us,
# disabling all but the one we want to use (eth1), 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: eno1
ansible_ifcfg_allowlist: ['{{ openqa_tap_iface }}', 'eno2', 'eno3', 'eno4']
ansible_ifcfg_disabled: ['eno2', 'eno3', 'eno4']
openqa_tap_iface: eth1
ansible_ifcfg_allowlist: ['eth0', '{{ openqa_tap_iface }}', 'eth2', 'eth3']
ansible_ifcfg_disabled: ['eth0', 'eth2', 'eth3']
# Has a hardware RNG
openqa_rngd: True