Fair point. If there's anyone out there who's unwilling to reply publicly, please feel free to reply directly to me.
Specifically: we want to know if Open MPI v5.0.0 stops supporting < SLURM 2017.11 is going to be a problem. -- Jeff Squyres jsquy...@cisco.com ________________________________ From: Tim Carlson <timothy.carl...@pnnl.gov> Sent: Wednesday, August 17, 2022 11:34 AM To: Open MPI Users <users@lists.open-mpi.org> Cc: Jeff Squyres (jsquyres) <jsquy...@cisco.com> Subject: Re: [OMPI users] Oldest version of SLURM in use? To be honest, I only upgrade SLURM when there is a feature I absolutely have to have, or a big bug that needs to be fixed. Like when GRES was introduced, and we started using GPUs. Updating SLURM and then going to find all the binaries that have been running for years and need to be relinked (or binary edited) to a new PMI library is painful. I’m guessing there are plenty of folks on the OpenMPI list who are less than willing to reply as they are certainly running versions of SLURM previous to 20.11 that have been summarily yanked from schedmd’s download site due to the security flaw that was discovered. All that being said, it is true that we still have ancient project clusters tucked away that have limited users and are fairly static in terms of the software stack. I’d be fibbing if I said all of my SLURM installations are from this decade. Tim -- Tim Carlson Team Lead – HPC/ML/Q, Research Computing Computing & Information Technology Directorate Pacific Northwest National Laboratory | www.pnnl.gov<http://www.pnnl.gov/> 509.371.6435 | t...@pnnl.gov<mailto:t...@pnnl.gov> From: users <users-boun...@lists.open-mpi.org> on behalf of "Jeff Squyres (jsquyres) via users" <users@lists.open-mpi.org> Reply-To: Open MPI Users <users@lists.open-mpi.org> Date: Wednesday, August 17, 2022 at 8:18 AM To: Open MPI Users <users@lists.open-mpi.org> Cc: "Jeff Squyres (jsquyres)" <jsquy...@cisco.com> Subject: Re: [OMPI users] Oldest version of SLURM in use? Check twice before you click! This email originated from outside PNNL. These are great data points! I'd love to hear from others, too. -- Jeff Squyres jsquy...@cisco.com ________________________________ From: users <users-boun...@lists.open-mpi.org> on behalf of Andrew Reid via users <users@lists.open-mpi.org> Sent: Tuesday, August 16, 2022 10:21 AM To: Open MPI Users <users@lists.open-mpi.org> Cc: Andrew Reid <andrew.ce.r...@gmail.com> Subject: Re: [OMPI users] Oldest version of SLURM in use? 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<mailto: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<mailto: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<mailto:jsquy...@cisco.com> -- Andrew Reid / andrew.ce.r...@gmail.com<mailto:andrew.ce.r...@gmail.com> -- Andrew Reid / andrew.ce.r...@gmail.com<mailto:andrew.ce.r...@gmail.com>