Commit Graph

12 Commits

Author SHA1 Message Date
Kevin Fenzi
5be96729ca builders/builders_stg: not external
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2025-04-28 11:26:03 -07:00
James Antill
68cbd3dc2c Turn nftables on everywhere.
Signed-off-by: James Antill <james@and.org>
2025-04-24 20:05:03 +00:00
James Antill
84a8bb3a82 Move all production builders to nftables.
Signed-off-by: James Antill <james@and.org>
2025-04-18 20:20:01 +00:00
Kevin Fenzi
8140d863f0 koji_builder: no longer install koji-containerbuild packages
These packages were used when we were building containers in OSBS, and
since we don't do that anymore, drop installing that anywhere.

Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2025-01-20 14:13:31 -08:00
Kevin Fenzi
00e7d2a28c typo: use the correct seperator
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2023-01-13 12:01:46 -08:00
Kevin Fenzi
4b2e6f8fe4 builders: exclude updating koji-containerbuild for now
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2023-01-13 10:30:51 -08:00
Kevin Fenzi
580cd252c5 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
Nils Philippsen
b5462742b1 ipa/client: enable for builders in prod
Also, revise special treatment for bkernel*, the `ipa/client` role
grants shell, sudo access for sysadmin-main by default, just ensure the
lists for additional groups are empty.

Signed-off-by: Nils Philippsen <nils@redhat.com>
2021-03-24 13:44:33 +01:00
Nils Philippsen
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
Stephen Smoogen
330a8e4a1d and this should make our mail easier to read 2018-08-27 22:44:58 +00:00
Kevin Fenzi
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
Kevin Fenzi
a8e58addc9 try moving this up a level to the overriding group 2017-05-01 21:28:33 +00:00