3.0 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-27 ks_repo: http://10.5.126.23/pub/fedora/linux/releases/27/Server/x86_64/os/ volgroup: /dev/vg_host01 eth0_ip: 10.5.125.135 eth1_ip: 10.5.127.61 vmhost: bvirthost03.phx2.fedoraproject.org mem_size: 98304 max_mem_size: 98304 num_cpus: 30
bodhi_masher_enabled: True bodhi_updates_handler_enabled: False bodhi_signed_handler_enabled: False
fedmsg_certs:
-
service: shell owner: root group: masher can_send:
- bodhi.masher.start
-
service: releng owner: apache group: sysadmin-releng can_send:
- pungi.compose.phase.start
- pungi.compose.phase.stop
- pungi.compose.status.change
- pungi.compose.createiso.targets
- releng.atomic.twoweek.begin
- releng.atomic.twoweek.complete
-
service: bodhi owner: root group: masher 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.stable
- bodhi.update.karma.threshold.reach
- bodhi.buildroot_override.untag
-
service: ftpsync owner: root group: ftpsync can_send:
- bodhi.updates.epel.sync
- bodhi.updates.fedora.sync
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.