Ian Wienand 312b9bec24 Refactor AFS groups
Both the filesevers and db servers have common key material deployed
by the openafs-server-config role.  Put both types of server in a new
group "afs-server-common" so we can define this key material in just
one group file on bridge.

Then separate out the two into afs-<file|db>-server groups for
consistent naming.

Rename afs-admin for consistent naming.

The service file is updated to reflect the new groups.

Change-Id: Ifa5f251fdfb8de737ad2ed96491d45294ce23a0c
2021-02-11 13:35:16 +11:00

58 lines
897 B
YAML

# This is a dictionary of hosts, with a list of what
# groups they should be in
results:
adns1.opendev.org:
- adns
- dns
afs01.dfw.openstack.org:
- afs-server-common
- afs-file-server
- afs-client
firehose01.openstack.org:
- firehose
- puppet
- puppet4
graphite02.opendev.org:
- graphite
- letsencrypt
- webservers
lists.katacontainers.io:
- mailman
- puppet
- puppet4
logstash-worker02.openstack.org:
- logstash-worker
- puppet
- puppet4
mirror02.regionone.linaro-us.opendev.org:
- afs-client
- letsencrypt
- mirror
review01.openstack.org:
- backup
- borg-backup
- gerrit
- letsencrypt
- review
backup01.ord.rax.ci.openstack.org:
- disabled
- puppet
ze01.openstack.org:
- afs-client
- zuul
- zuul-executor
zk01.openstack.org:
- zookeeper