---
# These set a config value in /etc/fedmsg.d/, see roles/bodhi2/base/
bodhi_masher_enabled: True
bodhi_signed_handler_enabled: False
bodhi_updates_handler_enabled: False
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.
# For the MOTD
csi_security_category: Medium
datacenter: iad2
eth0_ipv4_gw: 10.3.169.254
eth0_ipv4_ip: 10.3.169.101
# These are consumed by a task in roles/fedmsg/base/main.yml
fedmsg_certs:
  # These are certs for pungi
  - 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
    group: sysadmin-releng
    owner: apache
    service: releng
  # These are certs for the masher to publish its own messages as it progresses.
  - 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
    group: apache
    owner: root
    service: bodhi
  - can_send:
      - bodhi.updates.epel.sync
      - bodhi.updates.fedora.sync
    group: ftpsync
    owner: root
    service: ftpsync
# NOTE: DO NOT UPGRADE past f38 until epel7 is EOL
# See https://pagure.io/releng/issue/11664
ks_repo: http://10.3.163.35/pub/fedora/linux/releases/38/Server/x86_64/os/
ks_url: http://10.3.163.35/repo/rhel/ks/kvm-fedora
max_mem_size: 98304
mem_size: 98304
num_cpus: 30
sar_output_file: bodhi.json
# GDPR SAR variables
sar_script: /usr/bin/bodhi-sar
sar_script_user: apache
virt_install_command: "{{ virt_install_command_one_nic }}"
vmhost: bvmhost-x86-04.iad2.fedoraproject.org
volgroup: /dev/vg_guests
