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

openqa/worker: give up on GRE, single tap host instead

Browse source 
OK, this GRE crap ain't working. Let's give up! Instead let's
have one tap-capable host per openQA deployment, so all the
tap jobs will go to it. This...should achieve that. Let's see
what blows up.
This commit is contained in:
Adam Williamson 2016-05-05 14:10:46 -07:00
parent 5503e325e1
commit b0b7dc9b47
8 changed files with 90 additions and 99 deletions
Download patch file Download diff file Expand all files Collapse all files

17
inventory/group_vars/openqa-workers
View file

@ -4,22 +4,5 @@ openqa_hostname: openqa01.qa.fedoraproject.org
openqa_key: "{{ prod_openqa_apikey }}"
openqa_secret: "{{ prod_openqa_apisecret }}"
# for iptables rules...maybe other stuff in future? both staging
# and prod workers are in this group
host_group: openqa-workers
# firewall rules to allow openQA openvswitch guests to communicate
custom_rules: [
'-A FORWARD -i br0 -j ACCEPT',
'-A FORWARD -m state -i eth0 -o br0 --state RELATED,ESTABLISHED -j ACCEPT',
'-A INPUT -i br0 -j ACCEPT'
]
# we 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 eth0 for us and leave everything else
# alone.
ansible_ifcfg_whitelist: ['eth0']
deployment_type: prod
freezes: false