I’ve been running an HPC system for a science group for a while now and have built a couple of different systems based on common HPC infrastructures (ROCKS or Open HPC). These have been built on top of the rebuilt RHEL distros (mostly CentOS), but I don’t really need the level of stability that these provide and would actually like the sort of updates that you get from something like CentOS stream, so this seems like a time to try this.
The problem is that I haven’t found an HPC framework which would natively support this so I’m potentially going to have to roll my own. I don’t need anything fancy just some way to automatically deploy nodes and set up slurm to get jobs queued.
Any pointers to suitable frameworks or tools which would help with this and which aren’t tied to older distros?
The wiki article literally states in the first line.
“Rolling release, also known as rolling update or continuous delivery…”
You are just trying to argue for arguments sake. Just stop it. CentOS is a rolling release.
Centos is 100%, factually not a rolling release. Rolling releases don’t deploy based on version, they do it based on snapshot. That is quite literally the only defining characteristic of a rolling release and Centos does not share it. Centos deploys by version AKA a point release schedule. Centos 9. Centos 10. Centos 11. Actual rolling releases don’t have this characteristic. There isn’t an Arch 5, or an OpenSUSE Tumbleweed 23.1, or a Void Linux 4.8. There is just Arch, OpenSUSE Tumbleweed, and Void Linux. Maybe you have Arch 2023.29.6 snapshot but that is not the same thing.
“This is in contrast to a standard or point release development model which uses software versions that must be reinstalled over the previous version.”
This is exactly how Centos works. It’s also how Red Hat, Ubuntu and Debian work. Are Red Hat, Ubuntu and Debian rolling releases?