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

15 lines
378 B
Org Mode
Raw Normal View History

oci-registry/oci-candidate-registry: add to iad2 and try and move to f32. Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2020-05-24 10:09:23 -07: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
mass vm host_vars edit for default network connection
2022-01-19 14:18:12 -08:00
eth0_ipv4_gw: 10.3.169.254
eth0_ipv4_ip: 10.3.169.119
oci-registries: move all to f38 Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2023-05-15 14:16:00 -07:00
ks_repo: http://10.3.163.35/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://10.3.163.35/repo/rhel/ks/kvm-fedora
oci-registry/oci-candidate-registry: add to iad2 and try and move to f32. Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2020-05-24 10:09:23 -07:00
lvm_size: 120g
max_mem_size: 16384
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
mem_size: 16384
nrpe_procs_crit: 1000
nrpe_procs_warn: 900
oci-registry/oci-candidate-registry: add to iad2 and try and move to f32. Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2020-05-24 10:09:23 -07:00
num_cpus: 4
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
vmhost: bvmhost-x86-02.iad2.fedoraproject.org
volgroup: /dev/vg_guests
Copy permalink