infrastructure/ansible
1
0
Fork 0
Code Pull requests 7 Activity Actions
ansible/inventory/host_vars/qa14.qa.fedoraproject.org

27 lines
1 KiB
Org Mode
Raw Normal View History

add items for qa12->qa14
2015-01-15 21:58:21 +00:00
---
freezes: false
fas_client_groups: sysadmin-qa,sysadmin-main
sudoers: "{{ private }}/files/sudo/qavirt-sudoers"
nrpe_procs_warn: 900
nrpe_procs_crit: 1000
Fix more ip addresses up and blacklist a few more things.
2016-02-06 01:47:02 +00:00
eth0_ip: 10.5.131.22
Add a bunch more network information, blacklist some more groups
2016-02-06 00:25:29 +00:00
gw: 10.5.131.254
openQA: tweak ansible_ifcfg_whitelist handling for workers As we have more and more tap workers, it's no longer practical to do this for the whole group, as each one seems to have a *different* set of interfaces a) present and b) 'active'. So let's just take it out of the group vars and do it per-host instead. Each tap worker only actually has *one* real hardware interface that should be handled by network / NetworkManager, so we just list that one per-host (it's eth0 for all of them except the ppc64 host, which is eth2 for some damn reason). Signed-off-by: Adam Williamson <awilliam@redhat.com>
2018-03-14 12:01:20 -07:00
# 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
Tweak the ifcfg stuff for the other openQA tap workers too ...except ppc64le, which seems to have dropped dead. Once that one is done, we can drop the ugly bits from the tap-setup play, I hope. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2018-12-15 09:48:57 -08:00
# the regular interfaces (which on this system is eth0 and eth1) for us,
# disabling all but the one we want to use (eth0), and leave everything
# else alone.
ansible_ifcfg_whitelist: ['eth0', 'eth1']
ansible_ifcfg_disabled: ['eth1']
openQA: tweak ansible_ifcfg_whitelist handling for workers As we have more and more tap workers, it's no longer practical to do this for the whole group, as each one seems to have a *different* set of interfaces a) present and b) 'active'. So let's just take it out of the group vars and do it per-host instead. Each tap worker only actually has *one* real hardware interface that should be handled by network / NetworkManager, so we just list that one per-host (it's eth0 for all of them except the ppc64 host, which is eth2 for some damn reason). Signed-off-by: Adam Williamson <awilliam@redhat.com>
2018-03-14 12:01:20 -07:00
openqa: give qa14 more workers (it's more powerful) the group setting (4) is appropriate for the current worker boxes, but this one's a lot more powerful.
2016-04-14 14:30:41 -07:00
# this is a powerful machine, can handle more openQA workers
openqa_workers: 10
Fix up firewalling for the other openQA workers Signed-off-by: Adam Williamson <awilliam@redhat.com>
2018-11-23 12:50:02 -08:00
# firewall ports for server->worker websockets connections
# this port is 'QEMUPORT plus 1'
# QEMUPORT is:
# $ENV{QEMUPORT} = ($options{instance}) * 10 + 20002;
# so for worker 1 it's 20012, for worker 2 it's 20022, etc etc
tcp_ports: ['20013', '20023', '20033', '20043', '20053', '20063', '20073', '20083', '20093', '20103']
Copy permalink