infrastructure/ansible
1
0
Fork 0
Code Pull requests 7 Activity Actions
ansible/inventory/host_vars/proxy110.iad2.fedoraproject.org

40 lines
986 B
Org Mode
Raw Normal View History

iad2: add proxy10/101/110 Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2020-05-24 17:18:33 -07:00
---
proxy110.iad2.fedoraproject.org moved to linux-system-roles networking
2021-03-19 15:50:42 +00:00
datacenter: iad2
dns1: 10.3.163.33
dns2: 10.3.163.34
dns_search1: "iad2.fedoraproject.org"
dns_search2: "vpn.fedoraproject.org"
dns_search3: "fedoraproject.org"
eth0_ipv4: 10.3.163.77
eth0_ipv4_gw: 10.3.163.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
freezes: true
has_ipv4: yes
f37 uplift Upgraded proxies and builders to f37. We have a reduced timeframe to get this done before the holidays, so this time we just upgraded them in place. Usually we do a full reinstall. We will try and do that next cycle. Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2022-11-30 16:31:23 -08:00
ks_repo: http://10.3.163.35/pub/fedora/linux/releases/37/Server/x86_64/os/
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
ks_url: http://10.3.163.35/repo/rhel/ks/kvm-fedora
proxy110.iad2.fedoraproject.org moved to linux-system-roles networking
2021-03-19 15:50:42 +00:00
mac0: 52:54:00:04:49:7a
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
- autoconnect: yes
proxy110.iad2.fedoraproject.org moved to linux-system-roles networking
2021-03-19 15:50:42 +00:00
ip:
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
address:
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
- "{{ eth0_ipv4 }}/{{ eth0_ipv4_nm }}"
dhcp4: no
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
dns:
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
- "{{ dns1 }}"
- "{{ dns2 }}"
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
dns_search:
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
- "{{ dns_search1 }}"
- "{{ dns_search2 }}"
- "{{ dns_search3 }}"
gateway4: "{{ eth0_ipv4_gw }}"
mac: "{{ mac0 }}"
name: eth0
state: up
type: ethernet
iad2: add proxy10/101/110 Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2020-05-24 17:18:33 -07:00
nrpe_procs_crit: 1400
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
nrpe_procs_warn: 1200
# This is consumed by the roles/fedora-web/main role
sponsor: redhat
vmhost: vmhost-x86-06.iad2.fedoraproject.org
volgroup: /dev/vg_guests
iad2: add proxy10/101/110 Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2020-05-24 17:18:33 -07:00
vpn: true
Copy permalink