zlopez/ansible
1
0
Fork 0
forked from infra/ansible
Code Pull requests Activity
ansible/inventory/group_vars/batcave

75 lines
2.2 KiB
Text
Raw Permalink Normal View History

Setup a new batcave01 that will someday soon replace lockbox01
2015-08-19 20:14:31 +00:00
---
Fix ansible base
2015-09-25 20:03:51 +00:00
ansible_base: /srv/web/infra
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
# For the MOTD
# Neeed for rsync from log01 for logs.
Mass remove/replace iad2 -> rdu3, 10.3. -> 10.16. Signed-off-by: Nils Philippsen <nils@redhat.com>
2025-07-03 16:20:55 +02:00
custom_rules: ['-A INPUT -p tcp -m tcp -s 10.16.163.39 --dport 873 -j ACCEPT', '-A INPUT -p tcp -m tcp -s 192.168.1.59 --dport 873 -j ACCEPT']
Initial version of iptables to nftables conversion.
2024-10-04 16:46:26 -04:00
nft_custom_rules:
Cleanup nft merge. Chg osbuildapi and nft_custom_rules to use nft_table_filter. Signed-off-by: James Antill <james@and.org>
2026-05-01 12:23:28 -04:00
- 'add rule {{nft_table_filter}} INPUT ip saddr 10.16.163.39 tcp dport 873 counter accept'
- 'add rule {{nft_table_filter}} INPUT ip saddr 192.168.1.59 tcp dport 873 counter accept'
iptables: clean up osbuild and add a external block set scaffolding Setup osbuild so it only needs to exist on the specific builders in the osbuild channel, not all builders. Also, setup things so we can add a blocklist that will block external subnets/ip's if we need to do so. Currently it should just be an empty set, but we can implement it as needed/desired starting with the ips we already were blocking on just some hosts. Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2023-06-26 12:38:37 -07:00
#
# This host is externally reachable
#
external: true
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
freezes: true
ipa_client_shell_groups:
- fi-apprentice
- sysadmin-ask
- sysadmin-badges
- sysadmin-bot
- sysadmin-centos
- sysadmin-cloud
- sysadmin-copr
- sysadmin-coreos
- sysadmin-cvs
- sysadmin-datanommer
- sysadmin-debuginfod
batcave: add sysadmin-epel to groups Signed-off-by: Carl George <carlwgeorge@gmail.com>
2025-08-19 21:15:12 -05:00
- sysadmin-epel
gpu01: add new gpu01 machine in rdu3-iso This machine is in the rdu3 isolated network. For now, just setup a simple kickstart on one disk and a playbook that does the normal base role things. We can adjust from here. This machine has 1 nvme and another spinning rust device. Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2026-03-03 16:39:10 -08:00
- sysadmin-gpu
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
- sysadmin-koschei
- sysadmin-libravatar
- sysadmin-messaging
- sysadmin-noc
batcave01/bastion: add sysadmin-osbuild Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2023-07-10 15:45:48 -07:00
- sysadmin-osbuild
batcave01: add sysadmin-openscanhub Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2023-11-16 10:15:12 -08:00
- sysadmin-openscanhub
chore(batcave): add the new sysadmin group to vars Signed-off-by: Vít Smolík <me@smoliicek.cz>
2026-08-27 19:52:20 +02:00
- sysadmin-public-inbox
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
- sysadmin-qa
- sysadmin-retrace
- sysadmin-releasemonitoring
- sysadmin-releng
- sysadmin-tools
- sysadmin-upstreamfirst
- sysadmin-veteran
- sysadmin-web
ipa_host_group: batcave
ipa_host_group_desc: The Bat Cave
batcave: where batman hangs out working on the batcomputer Add a batcave01 in rdu3. Note that any changes made to this host before the cutover may be wiped out by syncing content from the old one, so probibly you shouldn't use it yet. Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2025-06-24 15:41:41 -07:00
lvm_size: 850000
mem_size: 32768
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
nfs_mount_opts: "rw,hard,bg,intr,noatime,nodev,nosuid,sec=sys,nfsvers=3"
Up max procs as the batcave has a fully functioning supercomputer.
2015-09-25 20:09:36 +00:00
nrpe_procs_crit: 1000
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: 900
batcave: where batman hangs out working on the batcomputer Add a batcave01 in rdu3. Note that any changes made to this host before the cutover may be wiped out by syncing content from the old one, so probibly you shouldn't use it yet. Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2025-06-24 15:41:41 -07:00
num_cpus: 16
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
primary_auth_source: ipa
tcp_ports: [80, 443, 8442, 8443]
vpn: true
disable swap checks on bvmhosts and batcave01 Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2022-11-16 17:46:22 -08:00
nagios_Check_Services:
swap: false
Zabbix: fix more hosts/groups for apache-status Signed-off-by: Greg Sutcliffe <fedora@emeraldreverie.org>
2026-01-26 14:18:01 +00:00
zabbix_macros:
'APACHE.STATUS.PORT': 443 # Proxies appear to ignore port 80 for apache-status
'APACHE.STATUS.SCHEME': https # but https://localhost seems to work instead
motd generic template added migrated notes from infra/hosts motd changes; excluding CSI infos removed csi_* vars from group_vars; converted csi_purpose & csi_relationship into notes fixed merge conflicts minor changes; var updating YAMLs & playbooks udpated YAMLs & playbooks again updated correctly; buildhw.yml fixing merge conflicts dest added in motd.yml
2025-01-06 13:04:00 +05:30
notes: |
Central management host for ansible
From the batcave batman ventures out to fight crime and protect gotham city!
batcave is the central management host for ansible.
It also is the infrastructure.fedoraproject.org website with various content.
It houses a number of infrastructure git repos.
This host relies on:
batcave: Update virthost in the MOTD. Signed-off-by: James Antill <james@and.org>
2025-11-18 15:54:15 -05:00
* The virthost it's hosted on (vmhost-x86-01.rdu3.fedoraproject.org)
motd generic template added migrated notes from infra/hosts motd changes; excluding CSI infos removed csi_* vars from group_vars; converted csi_purpose & csi_relationship into notes fixed merge conflicts minor changes; var updating YAMLs & playbooks udpated YAMLs & playbooks again updated correctly; buildhw.yml fixing merge conflicts dest added in motd.yml
2025-01-06 13:04:00 +05:30
Things that rely on this host:
* Things that access rhel/fedora/infra rpm repos, including builders and infra hosts.
* If this host is down, ansible runs cannot be made to update other hosts.
* If this host is down, crime may go up in gotham city.
Copy permalink