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

50 lines
1.2 KiB
Org Mode
Raw Normal View History

Add proxy12 on ibiblio05
2015-10-09 17:00:14 +00:00
---
proxy12.fedoraproject.org moved to linux-system-roles networking
2021-03-19 15:50:42 +00:00
datacenter: ibiblio
ibiblio: move all hosts over to linux system roles and new ipv6 addresses ibiblio is moving it's ipv6 network and wants us to move our machines. The last commit did this, but these machines aren't using linux sytem roles, so it wouldn't change anything unless we reinstalled them. So, lets move them over and then run playbooks to reconfigure. Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2021-11-08 17:24:44 -08:00
dns1: 152.2.21.1
dns2: 152.2.153.100
proxy12.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: 152.19.134.198
eth0_ipv4_gw: 152.19.134.129
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: 25
Reconfigure IPv6 Reconfigure IPv6 Reconfigure IPv6 Reconfigure IPv6 Reconfigure IPv6 Reconfigure IPv6 Reconfigure IPv6 Reconfigure IPv6 Configure IPv6 Reconfigure IPv6 Reconfigure IPv6 Reconfigure IPv6 Reconfigure IPv6 Reconfigure IPv6 Reconfigure IPv6 Reconfigure IPv6 Reconfigure IPv6 Configure IPv6 Update IPv6 address for noc02 rule Update IPv6 address in confg for noc02 address change Update IPv6 address for proxy04 Update IPv6 address for torrent02
2021-09-24 22:59:07 -04:00
eth0_ipv6: "2600:2701:4000:5211:dead:beef:00da:bbd8"
eth0_ipv6_gw: "2600:2701:4000:5211::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: 104
freezes: true
has_ipv4: yes
has_ipv6: yes
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
try to standardize the proxy configs
2021-03-31 16:25:36 -04:00
mac0: "52:54:00:84:5d:9f"
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: 20000
mem_size: 16384
proxy12.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
proxy12.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: "{{ mac0 }}"
name: eth0
type: ethernet
nrpe_procs_crit: 1400
nrpe_procs_warn: 1200
num_cpus: 8
Add proxy12 on ibiblio05
2015-10-09 17:00:14 +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: proxy12.fedoraproject.org
# This is consumed by the roles/fedora-web/main role
sponsor: ibiblio
vmhost: ibiblio05.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