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

69 lines
1.6 KiB
Text
Raw Normal View History

Add mailman01/02 to production.
2014-01-20 19:01:12 +00:00
---
# common items for the releng-* boxes
mailman: revert last change and add deployment_type, which was the actual error Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2019-11-21 03:48:24 +00:00
deployment_type: prod
Renamespace the fedmsg module.
2014-03-14 15:47:11 +00:00
# These are consumed by a task in roles/fedmsg/base/main.yml
Add mailman01/02 to production.
2014-01-20 19:01:12 +00:00
fedmsg_certs:
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
- can_send:
- logger.log
group: sysadmin
owner: root
service: shell
- can_send:
- mailman.receive
group: mailman
owner: mailman
service: mailman
ipa_client_shell_groups:
- sysadmin-tools
ipa_client_sudo_groups:
- sysadmin-tools
ipa_host_group: mailman
ipa_host_group_desc: Mailing list services
lvm_size: 250000
Mailman: the DB server is different in stg and prod
2014-02-03 11:11:15 +00:00
# Used by the mailman role
mailman: point to the db in iad2 from now on Signed-off-by: Pierre-Yves Chibon <pingou@pingoured.fr>
2020-06-11 17:08:06 +02:00
mailman_db_server: db01.iad2.fedoraproject.org
Update the Mailman role after addition of fedorahosted
2015-08-21 10:42:41 +00:00
mailman_domains:
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
- lists.fedoraproject.org
- lists.fedorahosted.org
- lists.pagure.io
Mailman: fix login variable names
2016-09-08 07:10:07 +00:00
mailman_login:
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
facebook:
display_name: Facebook
provider: facebook
Big Mailman update
2016-09-08 06:25:46 +00:00
github:
display_name: GitHub
provider: github
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
gitlab:
display_name: GitLab
provider: gitlab
Big Mailman update
2016-09-08 06:25:46 +00:00
google:
display_name: Google
provider: google
stackexchange:
display_name: StackExchange
provider: stackexchange
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
twitter:
display_name: Twitter
provider: twitter
max_mem_size: 32768
mem_size: 32768
nagios_Check_Services:
nrpe: true
swap: false
nrpe_check_postfix_queue_crit: 200
Setup check mail queue to handle machines that may have high queues
2014-10-09 20:18:10 +00:00
# by default, the number of emails in queue before we whine
Up some nagios checks for mailman01
2016-05-18 18:42:20 +00:00
nrpe_check_postfix_queue_warn: 100
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_crit: 500
Up some nagios checks for mailman01
2016-05-18 18:42:20 +00:00
# Number of processes for nagios
nrpe_procs_warn: 300
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
num_cpus: 4
# for systems that do not match the above - specify the same parameter in
# the host_vars/$hostname file
Up some nagios checks for mailman01
2016-05-18 18:42:20 +00: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
# Postfix main.cf
postfix_group: mailman
primary_auth_source: ipa
tcp_ports: [25, 80, 443,
# For outgoing fedmsg
3000, 3001, 3002, 3003]
Reference in a new issue Copy permalink