ansible/inventory/group_vars/fedimg_stg

---
# These are consumed by a task in roles/fedmsg/base/main.yml
fedmsg_certs:
  - can_send:
      - logger.log
    group: sysadmin
    owner: root
    service: shell
  - can_send:
      - fedimg.image.test
      - fedimg.image.upload
      - fedimg.image.copy
      - fedimg.image.publish
    group: fedmsg
    owner: root
    service: fedimg
fedmsg_debug_loopback: True
# These people get told when something goes wrong.
fedmsg_error_recipients:
  - sysadmin-fedimg-members@fedoraproject.org
ipa_client_shell_groups:
  - sysadmin-releng
ipa_client_sudo_groups:
  - sysadmin-releng
ipa_host_group: fedimg
lvm_size: 20000
mem_size: 6144
num_cpus: 2
# for systems that do not match the above - specify the same parameter in
# the host_vars/$hostname file
tcp_ports: [
  # These are all for outgoing fedmsg.
  3000, 3001, 3002, 3003, 3004, 3005, 3006, 3007, 3008, 3009, 3010, 3011, 3012, 3013]
# Use infrastructure-tags-stg repo
testing: True
Inventory entries for new fedimg01 nodes. 2014-07-09 13:48:23 +00:00			`---`
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			`# These are consumed by a task in roles/fedmsg/base/main.yml`
			`fedmsg_certs:`
			`- can_send:`
			`- logger.log`
			`group: sysadmin`
			`owner: root`
			`service: shell`
			`- can_send:`
			`- fedimg.image.test`
			`- fedimg.image.upload`
			`- fedimg.image.copy`
			`- fedimg.image.publish`
			`group: fedmsg`
			`owner: root`
			`service: fedimg`
			`fedmsg_debug_loopback: True`
			`# These people get told when something goes wrong.`
			`fedmsg_error_recipients:`
			`- sysadmin-fedimg-members@fedoraproject.org`
			`ipa_client_shell_groups:`
			`- sysadmin-releng`
			`ipa_client_sudo_groups:`
			`- sysadmin-releng`
			`ipa_host_group: fedimg`
Inventory entries for new fedimg01 nodes. 2014-07-09 13:48:23 +00:00			`lvm_size: 20000`
			`mem_size: 6144`
			`num_cpus: 2`
			`# for systems that do not match the above - specify the same parameter in`
			`# the host_vars/$hostname file`
Fix iptables for fedmsg on fedimg hosts. 2015-08-06 20:37:22 +00:00			`tcp_ports: [`
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			`# These are all for outgoing fedmsg.`
			`3000, 3001, 3002, 3003, 3004, 3005, 3006, 3007, 3008, 3009, 3010, 3011, 3012, 3013]`
			`# Use infrastructure-tags-stg repo`
			`testing: True`