system-config/playbooks/service-zuul.yaml
James E. Blair 1c069add54 Run zuul-launcher
This doesn't do anything substantial yet, but we'd like to start running
the server soon in order to test it out.

Change-Id: I9eb2bccd6e5e9a064cbaff10676aeb1af6653f98
2024-09-18 16:37:40 -07: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-launcher:!disabled"
name: "Configure zuul launcher"
roles:
- zuul-launcher
- hosts: "zuul-merger:!disabled"
name: "Configure zuul merger"
roles:
- zuul-merger
- hosts: "zuul-executor:!disabled"
name: "Configure zuul executor"
roles:
- role: kerberos-client
- 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