system-config/zuul.d
Ian Wienand e70c1e581c static: move certs to group, update testing name to static99
Currently we define the letsencrypt certs for each host in its
individual host variables.

With recent work we have a trusted CA and SAN names setup in
our testing environment; introducing the possibility that we could
accidentally reference the production host during testing (both have
valid certs, as far as the testing hosts are concerned).

To avoid this, we can use our naming scheme to move our testing hosts
to "99" and avoid collision with the production hosts.  As a bonus,
this really makes you think more about your group/host split to get
things right and keep the environment as abstract as possible.

One example of this is that with letsencrypt certificates defined in
host vars, testing and production need to use the same hostname to get
the right certificates created.  Really, this should be group-level
information so it applies equally to host01 and host99.  To cover
"hostXX.opendev.org" as a SAN we can include the inventory_hostname in
the group variables.

This updates one of the more tricky hosts, static, as a proof of
concept.  We rename the handlers to be generic, and update the testing
targets.

Change-Id: Id98768e29a06cebaf645eb75b39e4dc5adb8830d
2022-08-05 08:18:55 +10:00
..
docker-images Add Gerrit 3.6 jobs 2022-06-21 16:54:36 -07:00
goaccess.yaml Organize zuul jobs in zuul.d/ dir 2020-05-07 17:30:48 -05:00
infra-prod.yaml static: move certs to group, update testing name to static99 2022-08-05 08:18:55 +10:00
project.yaml Add Gerrit 3.5 to 3.6 upgrade testing 2022-06-22 10:58:17 -07:00
puppet.yaml Remove ethercalc config management 2022-05-30 12:57:48 -07:00
system-config-roles.yaml Add testing for jammy openafs 2022-05-12 12:53:49 +10:00
system-config-run.yaml static: move certs to group, update testing name to static99 2022-08-05 08:18:55 +10:00