builders_stg: do not set staging as datacenter for staging builders

This has caused them to pick up the iptables template for staging
instead of the one for their host group (koji_builder). There's no
reason to have staging as a datacenter for these, nothing checks it
besides the base iptables role hopefully.

Signed-off-by: Kevin Fenzi <kevin@scrye.com>
This commit is contained in:
Kevin Fenzi 2022-07-26 12:50:16 -07:00
parent cd0edc872d
commit 4e3d057cbb
2 changed files with 2 additions and 2 deletions

View file

@ -9,7 +9,7 @@ csi_relationship: |
* Several services rely on the builders, including koschei, Bodhi, Tagger, SCM, Darkserver.
* Produces automated builds of packages for the architecture listed. Builders can be scaled by adding new
csi_security_category: High
datacenter: staging
datacenter: iad2
dns: 10.3.163.33
docker_registry: "candidate-registry.stg.fedoraproject.org"
eth0_ipv4_gw: 10.3.167.254

View file

@ -8,7 +8,7 @@ csi_relationship: |
* Several services rely on the builders, including koschei, Bodhi, Tagger, SCM, Darkserver.
* Produces automated builds of packages for the architecture listed. Builders can be scaled by adding new
csi_security_category: High
datacenter: staging
datacenter: iad2
dns1: 10.3.163.33
docker_registry: "candidate-registry.stg.fedoraproject.org"
eth0_ipv4_gw: 10.3.167.254