iad2: bodhi-backend01 for iad2

Signed-off-by: Kevin Fenzi <kevin@scrye.com>

inventory/host_vars/bodhi-backend01.iad22.fedoraproject.org

@@ -0,0 +1,92 @@
+---
+nm: 255.255.255.0
+gw: 10.3.169.254
+dns: 10.3.163.33
+ks_url: http://10.3.163.35/repo/rhel/ks/kvm-fedora-32-iad2
+ks_repo: http://10.3.163.35/pub/fedora/linux/releases/32/Server/x86_64/os/
+volgroup: /dev/vg_guests
+eth0_ip: 10.3.169.101
+vmhost: bvmhost-x86-04.iad2.fedoraproject.org
+mem_size: 98304
+max_mem_size: 98304
+num_cpus: 30
+
+# These set a config value in /etc/fedmsg.d/, see roles/bodhi2/base/
+bodhi_masher_enabled: True
+bodhi_updates_handler_enabled: False
+bodhi_signed_handler_enabled: False
+
+# GDPR SAR variables
+sar_script: /usr/bin/bodhi-sar
+sar_script_user: apache
+sar_output_file: bodhi.json
+
+# These are consumed by a task in roles/fedmsg/base/main.yml
+fedmsg_certs:
+# These are certs for pungi
+- service: releng
+  owner: apache
+  group: sysadmin-releng
+  can_send:
+  # new school pungi-koji stuff (ask dgilmore)
+  - pungi.compose.phase.start
+  - pungi.compose.phase.stop
+  - pungi.compose.status.change
+  - pungi.compose.createiso.targets
+  - pungi.compose.ostree
+  - releng.atomic.twoweek.begin
+  - releng.atomic.twoweek.complete
+# These are certs for the masher to publish its own messages as it progresses.
+- service: bodhi
+  owner: root
+  group: apache
+  can_send:
+  - bodhi.mashtask.complete
+  - bodhi.mashtask.mashing
+  - bodhi.mashtask.start
+  - bodhi.mashtask.sync.done
+  - bodhi.mashtask.sync.wait
+  - bodhi.ostree.compose.start
+  - bodhi.ostree.compose.fail
+  - bodhi.ostree.compose.finish
+  - bodhi.errata.publish
+  - bodhi.update.eject
+  - bodhi.update.complete.testing
+  - bodhi.update.complete.stable
+  - bodhi.update.request.testing
+  - bodhi.update.request.stable
+  - bodhi.update.request.batched
+  - bodhi.update.karma.threshold.reach
+  - bodhi.buildroot_override.untag
+  - bodhi.update.comment
+  - bodhi.update.requirements_met.stable
+- service: ftpsync
+  owner: root
+  group: ftpsync
+  can_send:
+  - bodhi.updates.epel.sync
+  - bodhi.updates.fedora.sync
+
+
+# For the MOTD
+csi_security_category: Medium
+csi_primary_contact: Releng Admins sysadmin-releng-members@fedoraproject.org
+csi_purpose: Run the Bodhi masher.
+csi_relationship: |
+    The mashing of repos here happens as part of the 'fedmsg-hub' daemon.  Check
+    logs with 'journalctl -u fedmsg-hub'.  Check the bodhi masher docs/code for
+    more detail on what it does:
+    https://github.com/fedora-infra/bodhi/blob/develop/bodhi/consumers/masher.py
+
+    * This host relies on:
+      * db01 for its database, which is shares with the bodhi2 frontend nodes.
+      * An NFS mount of koji data in /mnt/koji/
+      * The fedmsg bus for triggering mashes.
+      * XMLRPC calls to koji for tagging and untagging updates.
+      * bugzilla for posting comments about status changes
+      * the wiki for getting information about QA "Test Cases"
+      * taksotron (resultsdb) for getting status-check results (gating updates).
+
+    * No other systems rely directly on this host.  Everything depends on it
+      indirectly for the creation of new updates repos (which get synced out to
+      the master mirror for distribution.

inventory/inventory

@@ -195,6 +195,7 @@ mbs_backend_stg
 [bodhi_backend]
 # This one handles the mashing/releng stuff
 bodhi-backend01.phx2.fedoraproject.org
+bodhi-backend01.iad2.fedoraproject.org
 
 [bodhi_backend_stg]
 bodhi-backend01.stg.phx2.fedoraproject.org
@@ -1284,6 +1285,7 @@ autosign01.iad2.fedoraproject.org
 bastion01.iad2.fedoraproject.org
 batcave01.iad2.fedoraproject.org
 blockerbugs01.iad2.fedoraproject.org
+bodhi-backend01.iad2.fedoraproject.org
 bugzilla2fedmsg01.iad2.fedoraproject.org
 busgateway01.iad2.fedoraproject.org
 bvmhost-x86-01.iad2.fedoraproject.org