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

35 lines
786 B
Org Mode
Raw Normal View History

fix backup01 not ansiblinbg. IT HELPS IF YOU COMMIT THE HOSTS FILE STEPHE
2020-05-26 11:03:01 -04:00
---
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
datacenter: iad2
Batch update of buildvm-s390x* Ansible host_vars files for linux-system-roles/network conversion.
2021-08-23 16:23:17 -07:00
dns1: 10.3.163.33
dns2: 10.3.163.34
dns_search1: "iad2.fedoraproject.org"
dns_search2: "fedoraproject.org"
backup01: new server Pushing this now as it's an outage of our backups and I want to get it going asap. It's only affecting backup01. Add dhcp entries for backup01's mgmt and eth0 interface. Use eth0 instead of eno1. Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2023-03-06 14:10:43 -08:00
eth0_ipv4: 10.3.163.40
eth0_ipv4_gw: 10.3.163.254
eth0_ipv4_nm: 24
eth0_mac: "{{ mac0 }}"
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
grokmirror_topdir: /fedora_backups/grokmirror
has_ipv4: yes
backup01: new server Pushing this now as it's an outage of our backups and I want to get it going asap. It's only affecting backup01. Add dhcp entries for backup01's mgmt and eth0 interface. Use eth0 instead of eno1. Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2023-03-06 14:10:43 -08:00
mac0: 6c:fe:54:57:4d:00
Batch update of buildvm-s390x* Ansible host_vars files for linux-system-roles/network conversion.
2021-08-23 16:23:17 -07: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
ip:
address:
backup01: new server Pushing this now as it's an outage of our backups and I want to get it going asap. It's only affecting backup01. Add dhcp entries for backup01's mgmt and eth0 interface. Use eth0 instead of eno1. Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2023-03-06 14:10:43 -08:00
- "{{ eth0_ipv4 }}/{{ eth0_ipv4_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
dns:
- "{{ dns1 }}"
- "{{ dns2 }}"
dns_search:
- "{{ dns_search1 }}"
- "{{ dns_search2 }}"
backup01: new server Pushing this now as it's an outage of our backups and I want to get it going asap. It's only affecting backup01. Add dhcp entries for backup01's mgmt and eth0 interface. Use eth0 instead of eno1. Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2023-03-06 14:10:43 -08:00
gateway4: "{{ eth0_ipv4_gw }}"
mac: "{{ eth0_mac }}"
name: eth0
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
state: up
type: ethernet
backup01: new server Pushing this now as it's an outage of our backups and I want to get it going asap. It's only affecting backup01. Add dhcp entries for backup01's mgmt and eth0 interface. Use eth0 instead of eno1. Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2023-03-06 14:10:43 -08:00
mtu: 9000
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_crit: 1400
nrpe_procs_warn: 1200
weblate_backup_topdir: /fedora_backups/misc/weblate
Copy permalink