infrastructure/ansible
1
0
Fork 0
Code Pull requests 7 Activity Actions
ansible/inventory/host_vars/buildhw-x86-04.iad2.fedoraproject.org

33 lines
639 B
Org Mode
Raw Normal View History

add host_vars for the rest of the buildhw-x64-XX servers
2020-06-26 12:45:47 -04:00
---
datacenter: iad2
updated a batch of servers
2021-03-22 15:53:04 +02:00
dns1: 10.3.163.33
dns2: 10.3.163.34
eth0_ipv4: 10.3.169.34
eth0_ipv4_gw: 10.3.169.254
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
has_ipv4: yes
updated a batch of servers
2021-03-22 15:53:04 +02:00
has_ipv6: no
mac0: 14:9e:cf:61:a5:07
mac1: 14:9e:cf:61:a5:0a
network_connections:
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
- ip:
address:
- "{{ eth0_ipv4 }}/{{ eth0_ipv4_nm }}"
dhcp4: no
dns:
- "{{ dns1 }}"
- "{{ dns2 }}"
dns_search:
- iad2.fedoraproject.org
- fedoraproject.org
gateway4: "{{ eth0_ipv4_gw }}"
mac: "{{ mac0 }}"
name: eth0
buildhw-x86: all these hosts are 10G and should use a 9000 mtu The last time they were re-installed they defaulted to 1500 and it's causing some problems for some of them at least (01-08 for sure). Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2023-04-03 14:47:31 -07:00
mtu: 9000
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
state: up
type: ethernet
- autoconnect: yes
mac: "{{ mac1 }}"
name: eth1
state: down
type: ethernet
Copy permalink