1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
|
---
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,
3004, 3005, 3006, 3007 ]
fas_client_groups: sysadmin-noc,sysadmin-badges,sysadmin-veteran
# These people get told when something goes wrong.
fedmsg_error_recipients:
- sysadmin-badges-members@fedoraproject.org
# 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: fedbadges
owner: root
group: fedmsg
can_send:
- fedbadges.badge.award
- fedbadges.person.rank.advance
# For the MOTD
csi_security_category: Low
csi_primary_contact: Badges admins - sysadmin-badges-members@fedoraproject.org
csi_purpose: Run fedmsg-hub with the fedbadges plugin to award badges (+ some crons)
csi_relationship: |
fedbadges integrates many different services..
* The fedbadges fedmsg-hub plugin relies on:
* the fedmsg bus, to deliver messages
* pkgdb, for queries about who owns what packages
* fas, to lookup what irc nick corresponds to what fas user.
* db-datanommer for the fedmsg history
* db01, for storing badge awards
* badges-web01 will be expecting to display badges entered into the tahrir
db on db01. So, if badges stop showing up there, the problem is likely
here.
* Locally, of note there exists:
* a git repo of badge rules and images to be synced here by ansible
to /usr/share/badges/
* a local file cache in /var/tmp/fedbadges-cache.dbm (not memcached, atm)
* Furthermore, there are a ton of cronjobs for awarding badges in
/usr/share/badges/cronjobs/ that depends on all sorts of third parties
(flickr, google+, libravatar, etc..).
|
