Sorry, 2022-2016=6 years old. This is why I let the computers do the arithmetic....
On Tue, Aug 16, 2022 at 10:19 AM Andrew Reid <andrew.ce.r...@gmail.com> wrote: > Wondering if I should reply from an alt for this, but.... in my case, it's > not so much "less well-funded" as "less well-organized". > > I have some small clusters that, for convenience, run the Debian-packaged > version of SLURM. Debian 9 reached the end of LTS June, 30, 2022, and > packaged version 16.05 of SLURM, which we were running on some systems > right up until that point, when it was eight years old. > > More generally, the Debian-packaged version tends to be a year or two > behind at distro-release time, and Debian LTS lifetimes can be five years, > so you can get into a window late in the distro lifecycle where things are > pretty old. > > But, to be clear, my expectation for support, which was the actual > question, is pretty much zero. I'm juggling my time and tasks with my eyes > open, and if I find myself in a corner where some software doesn't run > because the version mismatch between OpenMPI and SLURM is too big, my first > line of attack will be to do the required upgrades -- I'm pretty unlikely > to look for support. Also, there's a selection effect, usually the *reason* > the cluster has not been upgraded is that users want to keep running their > legacy software on it, so as a practical matter, I do not often find myself > in the version-mismatch corner. > > Pardon my rambling, the upshot is, some lazy/disorganized people rely on > third-party packagers, and do get pretty far behind. > > On Tue, Aug 16, 2022 at 9:54 AM Jeff Squyres (jsquyres) via users < > users@lists.open-mpi.org> wrote: > >> I have a curiosity question for the Open MPI user community: what version >> of SLURM are you using? >> >> I ask because we're honestly curious about what the expectations are >> regarding new versions of Open MPI supporting older versions of SLURM. >> >> I believe that SchedMD's policy is that they support up to 5-year old >> versions of SLURM, which is perfectly reasonable. But then again, there's >> lots of people who don't have support contracts with SchedMD, and therefore >> don't want or need support from SchedMD. Indeed, in well-funded >> institutions, HPC clusters tend to have a lifetime of 2-4 years before they >> are refreshed, which fits nicely within that 5-year window. But in less >> well-funded institutions, HPC clusters could have lifetimes longer than 5 >> years. >> >> Do any of you run versions of SLURM that are more than 5 years old? >> >> -- >> Jeff Squyres >> jsquy...@cisco.com >> > > > -- > Andrew Reid / andrew.ce.r...@gmail.com > -- Andrew Reid / andrew.ce.r...@gmail.com