ansible/inventory/group_vars/kerneltest

---
# 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
  - can_send:
      - kerneltest.release.edit
      - kerneltest.release.new
      - kerneltest.upload.new
    group: apache
    owner: root
    service: kerneltest
ipa_client_shell_groups:
  - sysadmin-noc
  - sysadmin-veteran
ipa_host_group: kerneltest
lvm_size: 20000
mem_size: 4096
num_cpus: 2
primary_auth_source: ipa
tcp_ports: [80]
# Definining these vars has a number of effects
# 1) mod_wsgi is configured to use the vars for its own setup
# 2) iptables opens enough ports for all threads for fedmsg
# 3) roles/fedmsg/base/ declares enough fedmsg endpoints for all threads
wsgi_fedmsg_service: kerneltest
wsgi_procs: 2
wsgi_threads: 1
Setup kerneltest01 prod node. 2014-07-01 21:41:38 +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			`# 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`
			`- can_send:`
			`- kerneltest.release.edit`
			`- kerneltest.release.new`
			`- kerneltest.upload.new`
			`group: apache`
			`owner: root`
			`service: kerneltest`
			`ipa_client_shell_groups:`
			`- sysadmin-noc`
			`- sysadmin-veteran`
			`ipa_host_group: kerneltest`
Setup kerneltest01 prod node. 2014-07-01 21:41:38 +00:00			`lvm_size: 20000`
iad2: kerneltest01.iad2: turns out 1gb memory is not enough Signed-off-by: Kevin Fenzi <kevin@scrye.com> 2020-06-01 19:25:02 -07:00			`mem_size: 4096`
			`num_cpus: 2`
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			`primary_auth_source: ipa`
			`tcp_ports: [80]`
Add kerneltest to the dynamic fedmsg endpoints stuff. 2015-06-16 20:48:36 +00:00			`# Definining these vars has a number of effects`
			`# 1) mod_wsgi is configured to use the vars for its own setup`
			`# 2) iptables opens enough ports for all threads for fedmsg`
			`# 3) roles/fedmsg/base/ declares enough fedmsg endpoints for all threads`
			`wsgi_fedmsg_service: kerneltest`
			`wsgi_procs: 2`
			`wsgi_threads: 1`