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

49 lines
1.3 KiB
Org Mode
Raw Normal View History

metrics-for-apps: added two temporary worker vms 04,05 Signed-off-by: David Kirwan <dkirwan@redhat.com>
2021-08-10 11:37:36 +09:00
---
datacenter: iad2
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: "{{ dns1 }}"
metrics-for-apps: added two temporary worker vms 04,05 Signed-off-by: David Kirwan <dkirwan@redhat.com>
2021-08-10 11:37:36 +09:00
dns1: 10.3.163.33
dns2: 10.3.163.34
dns_search1: "stg.iad2.fedoraproject.org"
added default network connection for group_vars/staging + fixed *stg* dns_search1...3
2022-01-26 11:52:32 -08:00
dns_search2: "iad2.fedoraproject.org"
metrics-for-apps: added two temporary worker vms 04,05 Signed-off-by: David Kirwan <dkirwan@redhat.com>
2021-08-10 11:37:36 +09:00
dns_search3: "fedoraproject.org"
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_ip: "{{eth0_ipv4}}"
metrics-for-apps: added two temporary worker vms 04,05 Signed-off-by: David Kirwan <dkirwan@redhat.com>
2021-08-10 11:37:36 +09:00
eth0_ipv4: 10.3.166.123
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_gw: 10.3.166.254
freezes: false
metrics-for-apps: added two temporary worker vms 04,05 Signed-off-by: David Kirwan <dkirwan@redhat.com>
2021-08-10 11:37:36 +09:00
gw: "{{ eth0_ipv4_gw }}"
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
has_ipv4: yes
lvm_size: 120g
metrics-for-apps: added two temporary worker vms 04,05 Signed-off-by: David Kirwan <dkirwan@redhat.com>
2021-08-10 11:37:36 +09:00
mac0: "{{ 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
max_mem_size: 16384
mem_size: 16384
metrics-for-apps: added two temporary worker vms 04,05 Signed-off-by: David Kirwan <dkirwan@redhat.com>
2021-08-10 11:37:36 +09: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
metrics-for-apps: added two temporary worker vms 04,05 Signed-off-by: David Kirwan <dkirwan@redhat.com>
2021-08-10 11:37:36 +09:00
ip:
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 }}"
dhcp4: no
metrics-for-apps: added two temporary worker vms 04,05 Signed-off-by: David Kirwan <dkirwan@redhat.com>
2021-08-10 11:37:36 +09: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 }}"
metrics-for-apps: added two temporary worker vms 04,05 Signed-off-by: David Kirwan <dkirwan@redhat.com>
2021-08-10 11:37:36 +09: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 }}"
- "{{ dns_search3 }}"
gateway4: "{{ eth0_ipv4_gw }}"
mac: "{{ mac0 }}"
name: eth0
state: up
type: ethernet
nm: 255.255.255.0
metrics-for-apps: added two temporary worker vms 04,05 Signed-off-by: David Kirwan <dkirwan@redhat.com>
2021-08-10 11:37:36 +09:00
nrpe_procs_crit: 1400
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_warn: 1200
num_cpus: 4
rhcos_ignition_file_url: "http://10.3.166.50/rhcos/worker.ign"
rhcos_install_img_url: "http://10.3.166.50/rhcos/rhcos-{{ rhcos_version }}-x86_64-metal.x86_64.raw.gz"
rhcos_install_rootfs_url: "http://10.3.166.50/rhcos/rhcos-{{ rhcos_version }}-x86_64-live-rootfs.x86_64.img"
rhcos_install_url: "http://10.3.166.50/rhcos/"
virt_install_command: "{{ virt_install_command_pxe_rhcos }}"
vmhost: vmhost-x86-07.stg.iad2.fedoraproject.org
volgroup: /dev/vg_guests
vpn: true
Copy permalink