ansible/inventory/group_vars/packages

---
# Define resources for this group of hosts here.
# Neeed for rsync from log01 for logs.
custom_rules: ['-A INPUT -p tcp -m tcp -s 10.3.163.39 --dport 873 -j ACCEPT', '-A INPUT -p tcp -m tcp -s 192.168.1.59 --dport 873 -j ACCEPT']
# These are consumed by a task in roles/fedmsg/base/main.yml
fedmsg_certs:
  - can_send:
      - logger.log
    group: sysadmin
    owner: root
    service: shell
freezes: false
ipa_client_shell_groups:
  - sysadmin-noc
  - sysadmin-packages
  - sysadmin-veteran
  - sysadmin-web
ipa_client_sudo_groups:
  - sysadmin-noc
  - sysadmin-packages
  - sysadmin-veteran
  - sysadmin-web
ipa_host_group: packages
lvm_size: 100000
max_mem_size: 8192
mem_size: 8192
nfs_mount_opts: "rw,hard,bg,intr,noatime,nodev,nosuid,nfsvers=3"
num_cpus: 4
primary_auth_source: ipa
pythonsitelib: /usr/lib/python2.7/site-packages
tcp_ports: [80, 443,
  # This is for glusterd
  6996,
  # These 16 ports are used by fedmsg.  One for each wsgi thread.
  3000, 3001, 3002, 3003, 3004, 3005, 3006, 3007, 3008, 3009, 3010, 3011, 3012, 3013, 3014, 3015]
add host_vars and group_vars for various groups to set freezes: false 2013-05-13 21:20:26 +00:00			`---`
Update the packages group_vars to be more classic 2014-03-11 17:16:34 +01:00			`# Define resources for this group of hosts here.`
Enter log01, bravest of the brave 2014-07-18 20:42:00 +00:00			`# Neeed for rsync from log01 for logs.`
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			`custom_rules: ['-A INPUT -p tcp -m tcp -s 10.3.163.39 --dport 873 -j ACCEPT', '-A INPUT -p tcp -m tcp -s 192.168.1.59 --dport 873 -j ACCEPT']`
Renamespace the fedmsg module. 2014-03-14 15:47:11 +00:00			`# These are consumed by a task in roles/fedmsg/base/main.yml`
Update the packages group_vars to be more classic 2014-03-11 17:16:34 +01:00			`fedmsg_certs:`
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			`- can_send:`
			`- logger.log`
			`group: sysadmin`
			`owner: root`
			`service: shell`
add host_vars and group_vars for various groups to set freezes: false 2013-05-13 21:20:26 +00:00			`freezes: false`
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			`ipa_client_shell_groups:`
			`- sysadmin-noc`
			`- sysadmin-packages`
			`- sysadmin-veteran`
			`- sysadmin-web`
			`ipa_client_sudo_groups:`
			`- sysadmin-noc`
			`- sysadmin-packages`
			`- sysadmin-veteran`
			`- sysadmin-web`
			`ipa_host_group: packages`
			`lvm_size: 100000`
			`max_mem_size: 8192`
			`mem_size: 8192`
Give packages RW access to the fedora_app_packages volume Signed-off-by: Patrick Uiterwijk <puiterwijk@redhat.com> 2017-12-22 13:25:54 +00:00			`nfs_mount_opts: "rw,hard,bg,intr,noatime,nodev,nosuid,nfsvers=3"`
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			`num_cpus: 4`
			`primary_auth_source: ipa`
			`pythonsitelib: /usr/lib/python2.7/site-packages`
			`tcp_ports: [80, 443,`
			`# This is for glusterd`
			`6996,`
			`# These 16 ports are used by fedmsg. One for each wsgi thread.`
			`3000, 3001, 3002, 3003, 3004, 3005, 3006, 3007, 3008, 3009, 3010, 3011, 3012, 3013, 3014, 3015]`