system-config/playbooks/service-zuul.yaml
Monty Taylor d93a661ae4 Run iptables in service playbooks instead of base
It's the only part of base that's important to run when we run a
service. Run it in the service playbooks and get rid of the
dependency on infra-prod-base.

Continue running it in base so that new nodes are brought up
with iptables in place.

Bump the timeout for the mirror job, because the iptables addition
seems to have just bumped it over the edge.

Change-Id: I4608216f7a59cfa96d3bdb191edd9bc7bb9cca39
2020-06-04 07:44:22 -05:00

41 lines
1.1 KiB
YAML

# We exclude !disabled because we want to run the noop task on all
# of the hosts in the group, not just the active ones, because we're
# pulling their hostvars from the fact cache. They don't stop being
# zookeeper servers just because they are disabled.
- hosts: "zookeeper"
tasks:
- name: Use the host so we have access to its hostvars
debug:
msg: "This debug statement is to get us access to hostvars"
- hosts: "zuul:!disabled"
name: "Configure zuul servers"
roles:
- iptables
- install-docker
- zuul
- hosts: "zuul-merger:!disabled"
name: "Configure zuul merger"
roles:
- zuul-merger
- hosts: "zuul-executor:!disabled"
name: "Configure zuul executor"
roles:
- role: kerberos-client
kerberos_realm: 'OPENSTACK.ORG'
kerberos_admin_server: 'kdc.openstack.org'
kerberos_kdcs:
- kdc03.openstack.org
- kdc04.openstack.org
- role: openafs-client
openafs_client_cache_size: "{{ afs_client_cache_size | default(10000000) }}" # 10GiB
- role: zuul-executor
- hosts: "zuul-scheduler:!disabled"
name: "Configure zuul scheduler"
roles:
- zuul-scheduler
- zuul-web