ansible/inventory/group_vars/ipsilon

---
# 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']
ipa_host_group: ipsilon
ipa_host_group_desc: Ipsilon SSO application
lvm_size: 20000
mem_size: 4096
num_cpus: 2
# for systems that do not match the above - specify the same parameter in
# the host_vars/$hostname file
tcp_ports: [80, 443]
ipsilon: create ipsilon01.stg vm Right now ipsilon is running in openshift, but sadly in order to work with ipa instead of fas as it's backend it needs to use sssd and pam stack. That does not work in a container, so move it back to a vm at least for now until we sort out what we want to do. Signed-off-by: Kevin Fenzi <kevin@scrye.com> 2020-09-24 14:03:11 -07: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']`
			`ipa_host_group: ipsilon`
			`ipa_host_group_desc: Ipsilon SSO application`
ipsilon: create ipsilon01.stg vm Right now ipsilon is running in openshift, but sadly in order to work with ipa instead of fas as it's backend it needs to use sssd and pam stack. That does not work in a container, so move it back to a vm at least for now until we sort out what we want to do. Signed-off-by: Kevin Fenzi <kevin@scrye.com> 2020-09-24 14:03:11 -07:00			`lvm_size: 20000`
			`mem_size: 4096`
			`num_cpus: 2`
			`# 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: [80, 443]`