Infrastructure/ansible
1
0
Fork 0
Code Issues Pull requests 6 Projects Releases Packages Wiki Activity Actions
ansible/inventory/host_vars/proxy14.fedoraproject.org

50 lines
1.3 KiB
Org Mode
Raw Normal View History

update files to put basics for proxy13/proxy14 into being
2016-12-01 17:46:58 +00:00
---
proxy14.fedoraproject.org moved to linux-system-roles networking
2021-03-19 15:50:42 +00:00
datacenter: rdu-cc
proxy14: define dns for virt-install Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2021-07-15 14:52:05 -07:00
dns: 8.8.8.8
Fix some problems with the previous git merge with the proxy host_vars. Add in a public_hostname for all proxies
2021-03-31 16:44:17 -04:00
dns1: 8.8.8.8
dns2: 8.8.4.4
proxy14.fedoraproject.org moved to linux-system-roles networking
2021-03-19 15:50:42 +00:00
dns_search1: "vpn.fedoraproject.org"
dns_search2: "fedoraproject.org"
eth0_ipv4: 8.43.85.67
eth0_ipv4_gw: 8.43.85.254
Fix some problems with the previous git merge with the proxy host_vars. Add in a public_hostname for all proxies
2021-03-31 16:44:17 -04:00
eth0_ipv6: "2620:52:3:1:dead:beef:cafe:fed7"
eth0_ipv6_gw: "2620:52:3:1:ffff:ffff:ffff:fffe"
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_ipv6_nm: 64
freezes: true
has_ipv4: yes
has_ipv6: yes
proxies: move all proxies to f35 Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2022-02-20 17:22:05 -08:00
ks_repo: http://38.145.60.16/pub/fedora/linux/releases/35/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://38.145.60.16/repo/rhel/ks/kvm-fedora
try to standardize the proxy configs
2021-03-31 16:25:36 -04:00
mac0: "52:54:00:19:67:0C"
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
max_mem_size: 32768
mem_size: 16384
proxy14.fedoraproject.org moved to linux-system-roles networking
2021-03-19 15:50:42 +00: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
- autoconnect: yes
proxy14.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 }}"
- "{{ eth0_ipv6 }}/{{ eth0_ipv6_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 }}"
- 2001:4860:4860::8888
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 }}"
gateway4: "{{ eth0_ipv4_gw }}"
gateway6: "{{ eth0_ipv6_gw }}"
mac: "{{ ansible_default_ipv4.macaddress }}"
name: eth0
type: ethernet
nrpe_procs_crit: 1400
nrpe_procs_warn: 1200
num_cpus: 8
update files to put basics for proxy13/proxy14 into being
2016-12-01 17:46:58 +00:00
postfix_group: vpn
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
public_hostname: proxy14.fedoraproject.org
# This is consumed by the roles/fedora-web/main role
sponsor: redhat
vmhost: vmhost-x86-cc05.rdu-cc.fedoraproject.org
volgroup: /dev/rhel_vmhost-x86-05
ok maybe this will work..maybe this will die in a fire
2017-01-08 23:07:48 +00:00
vpn: true
Reference in a new issue Copy permalink