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

42 lines
818 B
Org Mode
Raw Normal View History

inventory: add buildhw-a64-19/20 - cavium thunder x2's Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2020-06-30 11:31:56 -07: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.170.140
eth0_ipv4_gw: 10.3.170.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: f4:e9:d4:cc:32:b2
mac1: f4:e9:d4:cc:32:b3
mac2: f4:e9:d4:f2:e9:6e
Killed trailing spaces in group/host vars with fire. Normally it's just a nitpick to not have trailing spaces on variables. However, for some things like mac address, it really matters. Bunches of buildhw's were failing ansibile because they were passing "mac address " to linux-system-roles networking and ansible was going 'huh, nope, I can't find that mac address here at all'. So, just blow all the tailing spaces away to avoid any other variables that hit this. Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2021-05-04 08:52:52 -07:00
mac3: f4:e9:d4:f2:e9:6f
updated a batch of servers
2021-03-22 15:53:04 +02:00
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
state: up
type: ethernet
- autoconnect: yes
mac: "{{ mac1 }}"
name: eth1
state: down
type: ethernet
- mac: "{{ mac2 }}"
name: eth2
state: down
type: ethernet
- mac: "{{ mac3 }}"
name: eth3
state: down
type: ethernet
Copy permalink