Make etherpad configuration more generic for multiple hosts

This switches us to running the services against the etherpad group. We
also define vars in a group_vars file rather than a host specific
file. This allows us to switch testing over to etherpad99 to decouple it
from our production hostnames.

A followup change will add a new etherpad production server that will be
deployed alongside the existing one. This refactor makes that a bit
simpler.

Change-Id: I838ad31eb74a3abfd02bbfa77c9c2d007d57a3d4
This commit is contained in:
Clark Boylan
2023-04-03 14:56:17 -07:00
parent 19352a6944
commit ed1c7c94a3
10 changed files with 10 additions and 11 deletions

View File

@@ -1,8 +1,8 @@
etherpad_vhost_name: etherpad.opendev.org
letsencrypt_certs:
etherpad01-opendev-org-main:
etherpad-opendev-org-main:
- etherpad.opendev.org
- etherpad01.opendev.org
- '{{ inventory_hostname }}'
- etherpad.openstack.org
etherpad_redirect_vhost: etherpad.openstack.org
borg_backup_excludes_extra:

View File

@@ -55,7 +55,7 @@ groups:
- adns*.opendev.org
- ns*.opendev.org
eavesdrop: eavesdrop[0-9]*.opendev.org
etherpad: etherpad[0-9]*.open*.org
etherpad: etherpad[0-9]*.opendev.org
gitea:
- gitea[0-9]*.opendev.org
gitea-lb: