ansible/inventory/group_vars/os_proxies

---
custom_rules: [
  # Needed for keepalived
  '-A INPUT -d 224.0.0.0/8 -j ACCEPT', '-A INPUT -p vrrp -j ACCEPT',
  # machinectl api
  '-A INPUT -p tcp --dport 22623 --src 38.145.48.0/27 -j ACCEPT']
datacenter: cloud
host_group: cloud
lvm_size: 20000
mem_size: 8192
num_cpus: 4
tcp_ports: [
  # For os routers
  80, 443,
  # For ks8 api
  6443,
  # For haproxy status
  8080]
communishift: add some proxies. Signed-off-by: Kevin Fenzi <kevin@scrye.com> 2019-05-11 18:45:10 +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			`custom_rules: [`
			`# Needed for keepalived`
			`'-A INPUT -d 224.0.0.0/8 -j ACCEPT', '-A INPUT -p vrrp -j ACCEPT',`
			`# machinectl api`
			`'-A INPUT -p tcp --dport 22623 --src 38.145.48.0/27 -j ACCEPT']`
communishift: add some proxies. Signed-off-by: Kevin Fenzi <kevin@scrye.com> 2019-05-11 18:45:10 +00:00			`datacenter: cloud`
communistack: put os-proxies in cloud host_group to try and make nagios happy. Signed-off-by: Kevin Fenzi <kevin@scrye.com> 2019-05-12 16:56:53 +00:00			`host_group: cloud`
communishift: use the actual proper external ips and paths Signed-off-by: Kevin Fenzi <kevin@scrye.com> 2019-05-11 18:55:24 +00:00			`lvm_size: 20000`
			`mem_size: 8192`
			`num_cpus: 4`
communishift: Setup simple haproxy config and add firewall rules Note that we don't use the haproxy rule because it's very proxy specific. Signed-off-by: Kevin Fenzi <kevin@scrye.com> 2019-05-11 20:13:36 +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			`# For os routers`
			`80, 443,`
			`# For ks8 api`
			`6443,`
			`# For haproxy status`
			`8080]`