ansible/inventory/group_vars/notifs_backend

---
# Define resources for this group of hosts here.
deployment_type: prod
# These are consumed by a task in roles/fedmsg/base/main.yml
fedmsg_certs:
  - # The shell cert needs to be allowed to send these too so it can do alembic
    # upgrades that trigger messages.
    can_send:
      - fmn.filter.update
      - fmn.preference.update
      - fmn.rule.update
      - fmn.confirmation.update
      - logger.log
    group: sysadmin
    owner: root
    service: shell
  - can_send:
      - fmn.filter.update
      - fmn.preference.update
      - fmn.rule.update
      - fmn.confirmation.update
    group: fedmsg
    owner: root
    service: fmn
# For performance measurement.. for now.  This can be removed whenever.
fedmsg_loglevel: DEBUG
lvm_size: 65536
max_mem_size: "{{ mem_size }}"
mem_size: 24576
num_cpus: 8
# 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]
Host definitions for the fmn prod nodes. 2014-01-24 19:47:07 +00:00			`---`
Killed trailing spaces in group/host vars with fire. Normally it's just a nitpick to not have trailing spaces on variables. However, for some things like mac address, it really matters. Bunches of buildhw's were failing ansibile because they were passing "mac address " to linux-system-roles networking and ansible was going 'huh, nope, I can't find that mac address here at all'. So, just blow all the tailing spaces away to avoid any other variables that hit this. Signed-off-by: Kevin Fenzi <kevin@scrye.com> 2021-05-04 08:52:52 -07:00			`# Define resources for this group of hosts here.`
Inventory group/host variables: Sort yaml This was done using yq ( https://mikefarah.gitbook.io/yq/operators/sort-keys ) Doing things this way makes it much easier to see if a variable is set in a file or if two hosts differ in what variables they set. Hopefully we can keep things sorted moving forward. Basically this means just sort a-z anything you add to any host or group vaiable and it will be in the right place. Additionally, this enforces 'normal' intent rules for all the variable files which we should also try and obey. 2 spaces for first level, 3 for next, etc. When in doubt you can run yq on it. This should cause NO actual vairable changes, it's all just readability fixing for humans, ansible parses it exactly the same. Signed-off-by: Kevin Fenzi <kevin@scrye.com> 2021-11-16 13:27:57 -08:00			`deployment_type: prod`
			`# These are consumed by a task in roles/fedmsg/base/main.yml`
			`fedmsg_certs:`
			`- # The shell cert needs to be allowed to send these too so it can do alembic`
			`# upgrades that trigger messages.`
			`can_send:`
			`- fmn.filter.update`
			`- fmn.preference.update`
			`- fmn.rule.update`
			`- fmn.confirmation.update`
			`- logger.log`
			`group: sysadmin`
			`owner: root`
			`service: shell`
			`- can_send:`
			`- fmn.filter.update`
			`- fmn.preference.update`
			`- fmn.rule.update`
			`- fmn.confirmation.update`
			`group: fedmsg`
			`owner: root`
			`service: fmn`
			`# For performance measurement.. for now. This can be removed whenever.`
			`fedmsg_loglevel: DEBUG`
add in hosts for notifs 2020-06-08 19:03:18 -04:00			`lvm_size: 65536`
set max mem size here too 2016-07-17 20:39:51 +00:00			`max_mem_size: "{{ mem_size }}"`
Inventory group/host variables: Sort yaml This was done using yq ( https://mikefarah.gitbook.io/yq/operators/sort-keys ) Doing things this way makes it much easier to see if a variable is set in a file or if two hosts differ in what variables they set. Hopefully we can keep things sorted moving forward. Basically this means just sort a-z anything you add to any host or group vaiable and it will be in the right place. Additionally, this enforces 'normal' intent rules for all the variable files which we should also try and obey. 2 spaces for first level, 3 for next, etc. When in doubt you can run yq on it. This should cause NO actual vairable changes, it's all just readability fixing for humans, ansible parses it exactly the same. Signed-off-by: Kevin Fenzi <kevin@scrye.com> 2021-11-16 13:27:57 -08:00			`mem_size: 24576`
Adjust notifs backend sizes 2016-07-17 20:32:50 +00:00			`num_cpus: 8`
Host definitions for the fmn prod nodes. 2014-01-24 19:47:07 +00:00			`# for systems that do not match the above - specify the same parameter in`
			`# the host_vars/$hostname file`
Inventory group/host variables: Sort yaml This was done using yq ( https://mikefarah.gitbook.io/yq/operators/sort-keys ) Doing things this way makes it much easier to see if a variable is set in a file or if two hosts differ in what variables they set. Hopefully we can keep things sorted moving forward. Basically this means just sort a-z anything you add to any host or group vaiable and it will be in the right place. Additionally, this enforces 'normal' intent rules for all the variable files which we should also try and obey. 2 spaces for first level, 3 for next, etc. When in doubt you can run yq on it. This should cause NO actual vairable changes, it's all just readability fixing for humans, ansible parses it exactly the same. Signed-off-by: Kevin Fenzi <kevin@scrye.com> 2021-11-16 13:27:57 -08:00			`tcp_ports: [3000, 3001, 3002, 3003, 3004, 3005]`