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

28 lines
846 B
Org Mode
Raw Normal View History

add in vars for db-qa boxes and fix fedmsg relay
2020-05-29 15:02:07 -04:00
---
# This is a generic list, monitored by collectd
databases:
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
- postgres
datacenter: iad2
db_backup_dir: ['/backups']
add in vars for db-qa boxes and fix fedmsg relay
2020-05-29 15:02:07 -04:00
# This is a more strict list, to be made publicly available
dbs_to_backup:
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
- postgres
effective_cache_size: "6GB"
mass vm host_vars edit for default network connection
2022-01-19 14:18:12 -08:00
eth0_ipv4_gw: 10.3.174.254
eth0_ipv4_ip: 10.3.174.55
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
host_backup_targets: ['/backups']
# kernel SHMMAX value
kernel_shmmax: 68719476736
ks_repo: http://10.3.163.35/pub/fedora/linux/releases/32/Server/x86_64/os/
ks_url: http://10.3.163.35/repo/rhel/ks/kvm-fedora-32-iad2
add in vars for db-qa boxes and fix fedmsg relay
2020-05-29 15:02:07 -04:00
# These are normally group variables, but in this case db servers are often different
lvm_size: 300000
max_mem_size: "{{ mem_size * 2 }}"
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
add in vars for db-qa boxes and fix fedmsg relay
2020-05-29 15:02:07 -04:00
num_cpus: 6
shared_buffers: "2GB"
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
sudoers: "{{ private }}/files/sudo/qavirt-sudoers"
tcp_ports: [5432, 443, 3306]
vmhost: qvmhost-x86-02.iad2.fedoraproject.org
volgroup: /dev/vg_guests
Copy permalink