580cd252c5
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>
18 lines
377 B
Text
18 lines
377 B
Text
---
|
|
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]
|