bugzilla2fedmsg: clean up old vm's since we moved to openshift

Signed-off-by: Kevin Fenzi <kevin@scrye.com>
This commit is contained in:
Kevin Fenzi 2021-06-02 14:55:19 -07:00
parent 612843d72b
commit 24031a2038
7 changed files with 0 additions and 217 deletions

View file

@ -1,62 +0,0 @@
---
lvm_size: 20000
mem_size: 6144
num_cpus: 2
freezes: false
# for systems that do not match the above - specify the same parameter in
# the host_vars/$hostname file
tcp_ports: [ 3000, 3001, 3002, 3003 ]
primary_auth_source: ipa
ipa_host_group: bugzilla2fedmsg
ipa_host_group_desc: Service to bridge Bugzilla events into fedmsg
ipa_client_shell_groups:
- sysadmin-datanommer
- sysadmin-noc
- sysadmin-veteran
ipa_client_sudo_groups:
- sysadmin-datanommer
# These are consumed by a task in roles/fedmsg/base/main.yml
fedmsg_certs:
- service: shell
owner: root
group: sysadmin
can_send:
- logger.log
- service: bugzilla2fedmsg
owner: root
group: fedmsg
can_send:
- bugzilla.bug.new
- bugzilla.bug.update
# for fedora-messaging
username: "bugzilla2fedmsg{{ env_suffix }}"
# For the MOTD
csi_security_category: Low
csi_primary_contact: Fedmsg admins - sysadmin-datanommer-members@fedoraproject.org
csi_purpose: Run the bugzilla2fedmsg bridge to forward RH messages onto fedmsg
csi_relationship: |
A 'moksha-hub' daemon is the only thing really running here. (Don't confuse
that with the 'fedmsg-hub' running on most of our other backend machines.)
The bugzilla2fedmsg package provides a plugin to the moksha-hub that
connects out over the STOMP protocol to a 'fabric' of JBOSS FUSE brokers
living in the Red Hat DMZ. We authenticate with a cert/key pair that is
kept in /etc/pki/fedmsg/. Those brokers should push bugzilla events over
STOMP to our moksha-hub daemon. When a message arrives, we query bugzilla
about the change to get some 'more interesting' data to stuff in our
payload, then we sign the message using a fedmsg cert and fire it off to the
rest of our bus.
This service has no database, no memcached usage. It depends on those STOMP
brokers and being able to query bugzilla.rh.com.
STOMP config: /etc/moksha/production.ini
fedmsg config: /etc/fedmsg.d/
certs: /etc/pki/fedmsg
code: /usr/lib/python2.7/site-packages/bugzilla2fedmsg.py

View file

@ -1,61 +0,0 @@
---
# Define resources for this group of hosts here.
lvm_size: 20000
mem_size: 4096
num_cpus: 1
# for systems that do not match the above - specify the same parameter in
# the host_vars/$hostname file
tcp_ports: [ 3000, 3001 ]
ipa_host_group: bugzilla2fedmsg
ipa_host_group_desc: Service to bridge Bugzilla events into fedmsg
ipa_client_shell_groups:
- sysadmin-datanommer
- sysadmin-noc
- sysadmin-veteran
ipa_client_sudo_groups:
- sysadmin-datanommer
# These are consumed by a task in roles/fedmsg/base/main.yml
fedmsg_certs:
- service: shell
owner: root
group: sysadmin
can_send:
- logger.log
- service: bugzilla2fedmsg
owner: root
group: fedmsg
can_send:
- bugzilla.bug.new
- bugzilla.bug.update
# for fedora-messaging
username: "bugzilla2fedmsg{{ env_suffix }}"
# For the MOTD
csi_security_category: Low
csi_primary_contact: Fedmsg admins - sysadmin-datanommer-members@fedoraproject.org
csi_purpose: Run the bugzilla2fedmsg bridge to forward RH messages onto fedmsg
csi_relationship: |
A 'moksha-hub' daemon is the only thing really running here. (Don't confuse
that with the 'fedmsg-hub' running on most of our other backend machines.)
The bugzilla2fedmsg package provides a plugin to the moksha-hub that
connects out over the STOMP protocol to a 'fabric' of JBOSS FUSE brokers
living in the Red Hat DMZ. We authenticate with a cert/key pair that is
kept in /etc/pki/fedmsg/. Those brokers should push bugzilla events over
STOMP to our moksha-hub daemon. When a message arrives, we query bugzilla
about the change to get some 'more interesting' data to stuff in our
payload, then we sign the message using a fedmsg cert and fire it off to the
rest of our bus.
This service has no database, no memcached usage. It depends on those STOMP
brokers and being able to query bugzilla.rh.com.
STOMP config: /etc/moksha/production.ini
fedmsg config: /etc/fedmsg.d/
certs: /etc/pki/fedmsg
code: /usr/lib/python2.7/site-packages/bugzilla2fedmsg.py

View file

@ -1,14 +0,0 @@
---
nm: 255.255.255.0
gw: 10.3.163.254
dns: 10.3.163.33
ks_url: http://10.3.163.35/repo/rhel/ks/kvm-rhel-7-iad2
ks_repo: http://10.3.163.35/repo/rhel/RHEL7-x86_64/
eth0_ip: 10.3.163.45
volgroup: /dev/vg_guests
vmhost: vmhost-x86-05.iad2.fedoraproject.org
datacenter: iad2

View file

@ -1,13 +0,0 @@
---
nm: 255.255.255.0
gw: 10.3.166.254
dns: 10.3.163.33
volgroup: /dev/vg_guests
vmhost: vmhost-x86-04.stg.iad2.fedoraproject.org
datacenter: iad2
ks_url: http://10.3.163.35/repo/rhel/ks/kvm-rhel-7-iad2
ks_repo: http://10.3.163.35/repo/rhel/RHEL7-x86_64/
eth0_ip: 10.3.166.45

View file

@ -73,12 +73,6 @@ blockerbugs01.iad2.fedoraproject.org
[blockerbugs_stg]
blockerbugs01.stg.iad2.fedoraproject.org
[bugzilla2fedmsg]
bugzilla2fedmsg01.iad2.fedoraproject.org
[bugzilla2fedmsg_stg]
bugzilla2fedmsg01.stg.iad2.fedoraproject.org
[centos_ipa_client_stg]
centos-ipa-client01.stg.iad2.fedoraproject.org
centos-ipa-client02.stg.iad2.fedoraproject.org
@ -623,7 +617,6 @@ autosign01.stg.iad2.fedoraproject.org
# basset01.stg.iad2.fedoraproject.org
blockerbugs01.stg.iad2.fedoraproject.org
bodhi-backend01.stg.iad2.fedoraproject.org
bugzilla2fedmsg01.stg.iad2.fedoraproject.org
bvmhost-x86-01.stg.iad2.fedoraproject.org
bvmhost-x86-02.stg.iad2.fedoraproject.org
bvmhost-x86-03.stg.iad2.fedoraproject.org
@ -847,12 +840,6 @@ proxies
busgateway_stg
proxies_stg
[moksha_hubs:children]
bugzilla2fedmsg
[moksha_hubs_stg:children]
bugzilla2fedmsg_stg
[fedmsg_services:children]
fedmsg_hubs
fedmsg_ircs

View file

@ -19,7 +19,6 @@
- import_playbook: /srv/web/infra/ansible/playbooks/groups/batcave.yml
- import_playbook: /srv/web/infra/ansible/playbooks/groups/blockerbugs.yml
- import_playbook: /srv/web/infra/ansible/playbooks/groups/bodhi-backend.yml
- import_playbook: /srv/web/infra/ansible/playbooks/groups/bugzilla2fedmsg.yml
- import_playbook: /srv/web/infra/ansible/playbooks/groups/buildhw.yml
- import_playbook: /srv/web/infra/ansible/playbooks/groups/buildvm.yml
- import_playbook: /srv/web/infra/ansible/playbooks/groups/busgateway.yml

View file

@ -1,53 +0,0 @@
# create a new bugzilla2fedmsg server
# NOTE: should be used with --limit most of the time
# NOTE: make sure there is room/space for this server on the vmhost
# NOTE: most of these vars_path come from group_vars/mirrorlist or from hostvars
- import_playbook: "/srv/web/infra/ansible/playbooks/include/virt-create.yml myhosts=bugzilla2fedmsg:bugzilla2fedmsg_stg"
- name: dole out the generic configuration
hosts: bugzilla2fedmsg:bugzilla2fedmsg_stg
user: root
gather_facts: True
vars_files:
- /srv/web/infra/ansible/vars/global.yml
- "/srv/private/ansible/vars.yml"
- /srv/web/infra/ansible/vars/{{ ansible_distribution }}.yml
roles:
- base
- rkhunter
- nagios_client
- hosts
- ipa/client
- sudo
- collectd/base
- fedmsg/base
pre_tasks:
- import_tasks: "{{ tasks_path }}/yumrepos.yml"
tasks:
- import_tasks: "{{ tasks_path }}/motd.yml"
handlers:
- import_tasks: "{{ handlers_path }}/restart_services.yml"
- name: dole out the service-specific config
hosts: bugzilla2fedmsg:bugzilla2fedmsg_stg
user: root
gather_facts: True
roles:
- bugzilla2fedmsg
- role: collectd/fedmsg-service
process: moksha-hub
vars_files:
- /srv/web/infra/ansible/vars/global.yml
- "/srv/private/ansible/vars.yml"
- "{{ vars_path }}/{{ ansible_distribution }}.yml"
handlers:
- import_tasks: "{{ handlers_path }}/restart_services.yml"