auter VS upstream_sync

For your couple of Linux servers, if you have their repositories sorted out, look at auter. Really easy to setup and schedule servers and especially when it's just a few of them.

I'm quite fond of Auter. I've been using it to automate patching of about 250 servers (RHEL, but Auter supports Ubuntu as well). It's quite flexible and easily extendable via its hooks. You can use Ansible or similar to deploy the config and cronjob to all your hosts, and then just sit back and watch it do its thing. No GUI, though.

How about auter? Auter link It's a github project built by people I work with, and it has some very nice configuration options available. We've configured environments that autoreboot for kernel updates but not everything else, options for not patching a group of systems if a different group failed for some reason (to keep from taking down all redundant systems in a patching run), unlimited automation options and scripting. In the dept I'm with now, we use a commercial product but we're really leaning into moving to Ansible. This is because it's easier to manage multiple envs with playbooks, than it would be to write all the customization into scripts for auter (and we're not allowed to completely automate the patching process in the new dept).

If you need to manage your Linux repositories in-house, look at upstream_sync for RHEL and RHEL-clones. Look at debmirror for Debian and Debian-clones. If you have both, you can get debmirror for RHEL and RHEL-clones from EPEL, which would allow you to run both from one server.

Get x16 RHEL developer subscriptions. Use just x01 to setup a local repository and upstream_sync to pull down content. Fix the reposync options in upstream_sync to properly support RHEL 8 modular data. Configure all your RHEL servers to point to your local repository. Viola! You're now commiting fraud at an effectively limitless scale and, one day, IBM will show up to rape your butthole.

Check this out: upstream_sync

For RPM-based distros, like Alma, CentOS, RHEL, and Rocky, you can use something like this to more easily manage pulling content in your RHEL/RHEL-clone local repository server. Try to add your content into something like /repo/daily/distro_name/. Note, you will need to make a few changes to theupstream_syncscript to allow it to handle EL 8 modular metadata. It's like two additional flags under thecreaterepo` section ... I'll see if I can find them.

Start here. You need access to Red Hat CDN; otherwise known as a subscription and related certificate. You don't need that for CentOS or OEL (public). You just need to know what repositories you want to pull from.

upstream_sync for yum content (see here