Infrastructure/ansible
1
0
Fork 0
Code Issues Pull requests 6 Projects Releases Packages Wiki Activity Actions
ansible/inventory/group_vars/dns

24 lines
630 B
Text
Raw Normal View History

First attempt at DNS in ansible
2014-12-06 22:46:11 +00:00
---
Killed trailing spaces in group/host vars with fire. Normally it's just a nitpick to not have trailing spaces on variables. However, for some things like mac address, it really matters. Bunches of buildhw's were failing ansibile because they were passing "mac address " to linux-system-roles networking and ansible was going 'huh, nope, I can't find that mac address here at all'. So, just blow all the tailing spaces away to avoid any other variables that hit this. Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2021-05-04 08:52:52 -07:00
# Define resources for this group of hosts here.
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
csi_primary_contact: Fedora Admins - admin@fedoraproject.org
csi_purpose: Domain Name Service
csi_security_category: High
ipa_client_shell_groups:
- sysadmin-dns
ipa_client_sudo_groups:
- sysadmin-dns
ipa_host_group: dns
ipa_host_group_desc: DNS servers
First attempt at DNS in ansible
2014-12-06 22:46:11 +00:00
lvm_size: 30000
mem_size: 2048
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
nagios_has_named: true
nrpe_procs_crit: 500
nrpe_procs_warn: 300
First attempt at DNS in ansible
2014-12-06 22:46:11 +00:00
num_cpus: 2
ipa/client: enable for dns in prod Signed-off-by: Nils Philippsen <nils@redhat.com>
2021-03-19 17:25:38 +01:00
primary_auth_source: ipa
add back sysadmin-dns to sudo on nameservers Signed-off-by: Ricky Elrod <codeblock@fedoraproject.org>
2015-08-13 21:58:21 +00:00
sudoers: "{{ private }}/files/sudo/sysadmin-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
tcp_ports: [53]
# for systems that do not match the above - specify the same parameter in
# the host_vars/$hostname file
udp_ports: [53]
Reference in a new issue Copy permalink