pdc-backend: clean up last bits of pdc-backend hosts.

Signed-off-by: Kevin Fenzi <kevin@scrye.com>
This commit is contained in:
Kevin Fenzi 2020-08-24 09:32:04 -07:00
parent 5f114a7c98
commit eed8859c64
4 changed files with 0 additions and 116 deletions

View file

@ -1,41 +0,0 @@
---
# Define resources for this group of hosts here.
lvm_size: 20000
mem_size: 2048
num_cpus: 2
host_group: pdc-backend
# for systems that do not match the above - specify the same parameter in
# the host_vars/$hostname file
tcp_ports: []
fas_client_groups: sysadmin-noc,sysadmin-releng,sysadmin-datanommer,sysadmin-mbs,sysadmin-veteran
# See the host_vars files for the value of fedmsg_error_recipients here
csi_security_category: Moderate
csi_primary_contact: Ralph Bean <rbean@redhat.com>
csi_purpose: fedmsg-hub daemon that ferries data from fedmsg to PDC.
csi_relationship: |
NOTICE - The three pdc-backend do *different* things. They all run a
fedmsg-hub daemon that loads the pdc-updater consumer plugin. However, the
pdc-updater plugin is configured to do different things in each place.
On pdc-backend01, the compose handler is enabled which listens for new pungi
composes, and stores them in PDC. Fedora QE uses this data. The consumer
has only a single thread enabled to avoid OOMing itself with more than one
compose at a time.
On pdc-backend02, the modularity handlers are enabled which listen for MBS
activity, and store that in PDC. pdc-backend02 also hosts the retirement
handler which listens to dist-git for new dead.package files, and propagates
the retirement to PDC (by prematurely EOLing the branch). Multiple threads are
enabled so that it can work more efficiently on these smaller tasks.
On pdc-backend03, the dep chain handlers are enabled which listen for koji
messages and store dep chain information in PDC, like what rpms depend on what
other rpms at build time, and what containers depend on what rpms, etc..
Multiple threads are enabled so that it can work more efficiently on these
smaller tasks.

View file

@ -1,33 +0,0 @@
---
# Define resources for this group of hosts here.
lvm_size: 20000
mem_size: 2048
num_cpus: 1
host_group: pdc-backend
# for systems that do not match the above - specify the same parameter in
# the host_vars/$hostname file
tcp_ports: []
fas_client_groups: sysadmin-noc,sysadmin-releng,sysadmin-datanommer,sysadmin-mbs,sysadmin-veteran
# See the host_vars files for the value of fedmsg_error_recipients here
csi_security_category: Moderate
csi_primary_contact: Ralph Bean <rbean@redhat.com>
csi_purpose: fedmsg-hub daemon that ferries data from fedmsg to PDC.
csi_relationship: |
NOTICE - pdc-backend01 and pdc-backend02 do *different* things. They both run
a fedmsg-hub daemon that loads the pdc-updater consumer plugin. However, the
pdc-updater plugin is configured to do different things in each place.
On pdc-backend01, the compose handler is enabled which listens for new pungi
composes, and stores them in PDC. Fedora QE uses this data. The consumer
has only a single thread enabled to avoid OOMing itself with more than one
compose at a time.
On pdc-backend02, the dep chain and modularity handlers are enabled which
listen for koji and MBS activity, and store that in PDC. Multiple threads
are enabled so that it can work more efficiently on these smaller tasks.

View file

@ -627,9 +627,6 @@ os-node05.stg.iad2.fedoraproject.org
# osbs-aarch64-node01.stg.iad2.fedoraproject.org
# osbs-aarch64-node02.stg.iad2.fedoraproject.org
# packages03.stg.iad2.fedoraproject.org
# pdc-backend01.stg.iad2.fedoraproject.org
# pdc-backend02.stg.iad2.fedoraproject.org
# pdc-backend03.stg.iad2.fedoraproject.org
# pdc-web01.stg.iad2.fedoraproject.org
# pkgs01.stg.iad2.fedoraproject.org
proxy01.stg.iad2.fedoraproject.org
@ -814,16 +811,6 @@ pdc-web02.iad2.fedoraproject.org
[pdc_web_stg]
# pdc-web01.stg.iad2.fedoraproject.org
[pdc_backend]
pdc-backend01.iad2.fedoraproject.org
pdc-backend02.iad2.fedoraproject.org
pdc-backend03.iad2.fedoraproject.org
[pdc_backend_stg]
# pdc-backend01.stg.iad2.fedoraproject.org
# pdc-backend02.stg.iad2.fedoraproject.org
# pdc-backend03.stg.iad2.fedoraproject.org
[maintainer_test]
f31-test.fedorainfracloud.org
f32-test.fedorainfracloud.org
@ -1383,9 +1370,6 @@ osbs-control01.iad2.fedoraproject.org
osbs-master01.iad2.fedoraproject.org
osbs-node01.iad2.fedoraproject.org
osbs-node02.iad2.fedoraproject.org
pdc-backend01.iad2.fedoraproject.org
pdc-backend02.iad2.fedoraproject.org
pdc-backend03.iad2.fedoraproject.org
pdc-web01.iad2.fedoraproject.org
pdc-web02.iad2.fedoraproject.org
pkgs01.iad2.fedoraproject.org

View file

@ -88,13 +88,6 @@ define service {
# use defaulttemplate
#}
define service {
host_name pdc-backend01.iad2.fedoraproject.org
service_description Check for fedmsg-hub proc
check_command check_by_nrpe!check_fedmsg_hub_proc
use defaulttemplate
}
# Odd one, check for the supybot fedmsg plugin
define service {
@ -320,12 +313,6 @@ define service {
# use defaulttemplate
#}
define service {
host_name pdc-backend01.iad2.fedoraproject.org
service_description Check fedmsg consumers and producers hub
check_command check_by_nrpe!check_fedmsg_cp_pdc_backend
use defaulttemplate
}
define service {
host_name mbs-backend01.iad2.fedoraproject.org
service_description Check fedmsg consumers and producers hub
@ -399,12 +386,6 @@ define service {
# use defaulttemplate
#}
define service {
host_name pdc-backend01.iad2.fedoraproject.org
service_description Check fedmsg-hub consumers exceptions
check_command check_by_nrpe!check_fedmsg_cexceptions_pdc_backend
use defaulttemplate
}
define service {
host_name mbs-backend01.iad2.fedoraproject.org
service_description Check fedmsg-hub consumers exceptions
@ -479,13 +460,6 @@ define service {
# use defaulttemplate
#}
define service {
host_name pdc-backend01.iad2.fedoraproject.org
service_description Check fedmsg-hub consumers backlog
check_command check_by_nrpe!check_fedmsg_cbacklog_pdc_backend
use defaulttemplate
}
define service {
host_name mbs-backend01.iad2.fedoraproject.org
service_description Check fedmsg-hub consumers backlog