system-config/playbooks/service-zuul.yaml
James E. Blair fd47d15196 Add clouds.yaml to zuul schedulers
Similar to I127ba4a2cf33f7ffcecdf81acfc5c38db565da82 we now need
to add the nodepool clouds.yaml to the zuul schedulers.  When validating
and generating the config for the launchers, they need to access the
clouds.yaml file to learn some information about the cloud (eg, image
format).  Therefore, they must have the same clouds.yaml that the
launchers use.

Change-Id: I4a7076e66c9f8eca936ca3a7902537d427a99323
2024-10-14 11:32:49 -07:00

43 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:
- configure-openstacksdk
- 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:
- configure-openstacksdk
- zuul-scheduler
- zuul-web