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

49 lines
1.2 KiB
Org Mode
Raw Normal View History

Add proxy02. Drop second ip.
2015-02-21 22:28:28 +00:00
---
proxy02.fedoraproject.org moved to linux-system-roles networking
2021-03-19 15:50:42 +00:00
datacenter: internetx
Try using network_connections for proxy02 to get it to rewrite ifcfg correctly Signed-off-by: Stephen Smoogen <smooge@smoogespace.com>
2021-03-31 14:25:33 -04:00
dns1: 8.8.8.8
dns2: 8.8.4.4
proxy02.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"
proxy02: correct some network vars Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2022-06-01 13:58:47 -07:00
eth0_ipv4_ip: 85.236.55.6
Try using network_connections for proxy02 to get it to rewrite ifcfg correctly Signed-off-by: Stephen Smoogen <smooge@smoogespace.com>
2021-03-31 14:25:33 -04:00
eth0_ipv4_gw: 85.236.55.1
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_nm: 28
proxy02: correct some network vars Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2022-06-01 13:58:47 -07:00
eth0_ipv6_ip: "2001:4178:2:1269::fed2"
problem with proxy02 is with dns. switch to ip address and see if that fixes it.
2020-01-07 17:17:04 +00:00
eth0_ipv6_gw: "2001:4178:2:1269::1"
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: true
Move a bunch of machines to f38 Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2023-05-17 17:35:26 -07:00
ks_repo: http://38.145.60.16/pub/fedora/linux/releases/38/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
rkhunter: adjust for rhel9 Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2022-06-01 12:02:17 -07:00
max_mem_size: 65536
mem_size: 24576
Try using network_connections for proxy02 to get it to rewrite ifcfg correctly Signed-off-by: Stephen Smoogen <smooge@smoogespace.com>
2021-03-31 14:25:33 -04: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
Try using network_connections for proxy02 to get it to rewrite ifcfg correctly Signed-off-by: Stephen Smoogen <smooge@smoogespace.com>
2021-03-31 14:25:33 -04: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:
proxy02: correct some network vars Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2022-06-01 13:58:47 -07:00
- "{{ eth0_ipv4_ip }}/{{ eth0_ipv4_nm }}"
- "{{ eth0_ipv6_ip }}/{{ eth0_ipv6_nm }}"
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
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 }}"
proxy02: fix mac address to be whatever ansible facts has Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2022-06-01 14:19:26 -07:00
mac: "{{ ansible_default_ipv4.macaddress }}"
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
name: eth0
type: ethernet
nrpe_procs_crit: 1400
nrpe_procs_warn: 1200
rkhunter: adjust for rhel9 Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2022-06-01 12:02:17 -07:00
num_cpus: 4
Add proxy02. Drop second ip.
2015-02-21 22:28:28 +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: proxy02.fedoraproject.org
# This is consumed by the roles/fedora-web/main role
sponsor: internetx
rkhunter: adjust for rhel9 Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2022-06-01 12:02:17 -07:00
vmhost: internetx02.fedoraproject.org
volgroup: /dev/vg_guests
ok maybe this will work..maybe this will die in a fire
2017-01-08 23:07:48 +00:00
vpn: true
Copy permalink