ansible/inventory/host_vars/rabbitmq03.stg.iad2.fedoraproject.org

---
eth0_ipv4_gw: 10.3.166.254
eth0_ipv4_ip: 10.3.166.80
vmhost: vmhost-x86-05.stg.iad2.fedoraproject.org
volgroup: /dev/vg_guests
Add staging rabbitmq cluster machines. Signed-off-by: Kevin Fenzi <kevin@scrye.com> 2020-08-31 14:30:57 -07:00			`---`
rabbitmq / staging: just make gw match prod Signed-off-by: Kevin Fenzi <kevin@scrye.com> 2022-01-25 15:54:26 -08:00			`eth0_ipv4_gw: 10.3.166.254`
mass vm host_vars edit for default network connection 2022-01-19 14:18:12 -08:00			`eth0_ipv4_ip: 10.3.166.80`
inventory: rabbitmq03.stg: move to vmhost-x86-05 Signed-off-by: Kevin Fenzi <kevin@scrye.com> 2020-08-31 14:55:16 -07:00			`vmhost: vmhost-x86-05.stg.iad2.fedoraproject.org`
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			`volgroup: /dev/vg_guests`