ansible/inventory/host_vars/buildvm-a64-05.iad2.fedoraproject.org

---
datacenter: iad2
dns1: 10.3.163.33
dns2: 10.3.163.34
eth0_ip: 10.3.170.95
vmhost: bvmhost-a64-02.iad2.fedoraproject.org
iad2: lets add some a64 and a32 builders. Signed-off-by: Kevin Fenzi <kevin@scrye.com> 2020-06-03 10:18:41 -07:00			`---`
another batch of servers migrated 2021-03-25 19:01:37 +02:00			`datacenter: iad2`
			`dns1: 10.3.163.33`
			`dns2: 10.3.163.34`
buildvm: switch buildvm's back to getting networking set on install We don't want to use linux-systems-roles here because: 1) everytime we reinstall the mac address changes. 2) These get all the correct netowkring from the kickstart/initial install We do want to use linux-systems-roles for bare metal machines. Signed-off-by: Kevin Fenzi <kevin@scrye.com> 2021-05-25 14:08:37 -07:00			`eth0_ip: 10.3.170.95`
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			`vmhost: bvmhost-a64-02.iad2.fedoraproject.org`