system-config/playbooks/service-zuul.yaml
Monty Taylor f0b77485ec Run Zuul using Ansible and Containers
Zuul is publishing lovely container images, so we should
go ahead and start using them.

We can't use containers for zuul-executor because of the
docker->bubblewrap->AFS issue, so install from pip there.

Don't start any of the containers by default, which should
let us safely roll this out and then do a rolling restart.
For things (like web or mergers) where it's safe to do so,
a followup change will swap the flag.

Change-Id: I37dcce3a67477ad3b2c36f2fd3657af18bc25c40
2020-04-24 09:18:44 -05:00

40 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:
- 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