1.7 KiB
— nm: 255.255.255.0 gw: 10.5.125.254 dns: 10.5.126.21 ks_url: http://10.5.126.23/repo/rhel/ks/kvm-fedora-30 ks_repo: http://10.5.126.23/pub/fedora/linux/releases/30/Server/x86_64/os/ volgroup: /dev/vg_guests eth0_ip: 10.5.125.136 eth1_ip: 10.5.127.62 vmhost: bvirthost14.phx2.fedoraproject.org
bodhi_masher_enabled: False bodhi_updates_handler_enabled: True bodhi_signed_handler_enabled: True
sar_script: /usr/bin/bodhi-sar sar_script_user: apache sar_output_file: bodhi.json
fedmsg_certs:
- service: shell owner: root group: sysadmin
-
service: bodhi owner: root group: masher can_send:
- bodhi.buildroot_override.untag
- bodhi.update.requirements_met.stable
csi_security_category: Low csi_primary_contact: Bodhi Admins bodhiadmin-members@fedoraproject.org csi_purpose: Run the Bodhi UpdatesHandler and other backend processes csi_relationship: | This host handles all of the bodhi backend stuff except for mashing. https://github.com/fedora-infra/bodhi/blob/develop/bodhi/consumers/
-
This host relies on:
- db01 for its database, which is shares with the bodhi2 frontend nodes.
- The fedmsg bus for triggering work.
- 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"
- 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.