1
0
Fork 0
forked from infra/ansible
Commit graph

28 commits

Author SHA1 Message Date
3fd14610c6 ipa/client: enable for mailman in prod
Signed-off-by: Nils Philippsen <nils@redhat.com>
2021-03-24 13:44:33 +01:00
dbbf94a411 ipa/client: configure global shell access and sudo
Almost global anyway, i.e. inside the VPN.

The ipa/client-based shell access and sudo rules are only effective for
staging right now, the respective playbook bits are masked out for prod.

- Assign Ansible host groups to IPA host groups, the latter don't care
  about 'stg' in the name and use dashes rather than underscores.
- Distill shell access groups from fas_client_groups in group and host
  vars.
- Let all `sysadmin-*` groups in the previous list run anything via sudo
  in the host group (except bastion & batcave).
- Remove `fas_client_groups` from staging host and group vars.
- Remove sudoers from staging host and group vars if only `sysadmin-*`
  groups have shell access.
- Set up `ipa_client_shell_groups` on bastion to be a super set of the
  same on batcave.

Newly created IPA host groups:
- autosign
- badges
- basset
- bastion
- batcave
- blockerbugs
- bodhi
- bugzilla2fedmsg
- busgateway
- datagrepper
- dbserver
- dns
- fedimg
- github2fedmsg
- ipa
- kernel-qa
- kerneltest
- kojibuilder
- kojihub
- kojipkgs
- logging
- mailman
- memcached
- mirrormanager
- nagios
- notifs
- oci-registry
- odcs
- openqa
- openqa-workers
- osbs
- packages
- pdc-web
- pkgs
- proxies
- rabbitmq
- releng-compose
- resultsdb
- secondary
- sign-bridge
- sundries
- value
- wiki

Signed-off-by: Nils Philippsen <nils@redhat.com>
2021-02-01 22:23:41 +00:00
db1a1bb8e6 mailman: point to the db in iad2 from now on
Signed-off-by: Pierre-Yves Chibon <pingou@pingoured.fr>
2020-06-11 17:08:12 +02:00
Stephen Smoogen
7a5297cd56 mailman for iad2 2020-06-10 13:06:25 -04:00
a58c8b9934 mailman: revert last change and add deployment_type, which was the actual error
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2020-04-24 21:34:16 +02:00
546b209246 mailman: Add username for fedora messaging
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2020-04-24 21:34:16 +02:00
b11f063508 Mailman: first step in adding lists.pagure.io 2018-06-15 14:51:19 +00:00
65e4e081e8 add a missing nrpe: true 2017-09-09 19:29:06 +00:00
8b5a273b10 try and teach nagios about hosts we want to monitor swap on and ones we do not want to 2017-09-09 19:11:06 +00:00
e9d3f13c52 Mailman: fix login variable names 2016-09-08 07:10:07 +00:00
7f27054e60 Big Mailman update 2016-09-08 06:27:00 +00:00
a7aeaa0378 Up some nagios checks for mailman01 2016-05-18 18:42:20 +00:00
47dfa809d5 Explicitly list all certs that can send the logger.log fedmsg message. 2015-12-03 19:30:08 +00:00
2cda638026 Give mailman3 more fedmsg endpoints. 2015-11-19 14:40:33 +00:00
5b5c83d4de Update the Mailman role after addition of fedorahosted 2015-08-21 10:43:32 +00:00
75d8024cf7 More resources for mailman01 now that it's in prod 2015-08-20 17:16:52 +00:00
385db6cec1 Declare who can send what mailman3 fedmsg stuff. 2015-06-12 19:50:45 +00:00
c9395f3872 Fix HyperKitty's URL 2014-10-17 09:12:08 +00:00
cb3a2bee6e Setup check mail queue to handle machines that may have high queues 2014-10-09 20:18:10 +00:00
444c0c8f62 Try to solve the conflict between role vars and global vars 2014-09-18 08:46:08 +00:00
473ce2c403 Also, open ports for fedmsg on the mailman boxes. 2014-07-23 16:41:37 +00:00
5d57028fd6 Set the postfix group for mailman servers 2014-07-21 17:52:39 +00:00
6fb0f86d59 Reinstall mailman prod instances as rhel7. 2014-06-24 21:12:14 +00:00
edbc9b21cf Renamespace the fedmsg module. 2014-03-14 15:47:11 +00:00
159115f3d3 Mailman: the DB server is different in stg and prod 2014-02-03 11:11:21 +00:00
e5aad94914 Add mailman01/02 to production. 2014-01-20 19:01:12 +00:00
38c1cb6f81 Fix group name 2013-08-13 02:43:03 +00:00
3a0857fdd8 Add mailman01.stg 2013-08-12 21:17:21 +00:00