Hi Elisabetta, Ole Holm Nielsen <[email protected]> writes:
> On 10/03/2017 03:29 PM, Elisabetta Falivene wrote: >> I've been asked to upgrade our slurm installation. I have a slurm 2.3.4 on a >> Debian 7.0 wheezy cluster (1 master + 8 nodes). I've not installed it so I'm >> a >> bit confused about how to do this and how to proceed without destroying >> anything. >> >> I was thinking to upgrade at least to Jessie (Debian 8) but what about Slurm? >> I've read carefully the upgrading section >> (https://slurm.schedmd.com/quickstart_admin.html) of the doc, reading that >> the >> upgrade must be done incrementally and not jumping from 2.3.4 to 17, for >> example. > > Yes, you may jump max 2 versions per upgrade. > Quoting https://slurm.schedmd.com/quickstart_admin.html#upgrade > >> Slurm daemons will support RPCs and state files from the two previous minor >> releases (e.g. a version 16.05.x SlurmDBD will support slurmctld daemons and >> commands with a version of 16.05.x, 15.08.x or 14.11.x). > > >> Stil is not clear to me precisely how to do this. How would you proceed if >> asked to upgrade a cluster you just don't know nothing about? What would you >> check? What version of o.s. and slurm would you choose? What would you >> backup? >> And how would you proceed? >> >> Any info is gold! Thank you > > My 2 cents of information: > > My Slurm Wiki explains how to upgrade Slurm on CentOS 7: > https://wiki.fysik.dtu.dk/niflheim/Slurm_installation#upgrading-slurm > > Probably the general method is the same for Debian. Ole's pages on Slurm are indeed very useful (Thanks, Ole!). I just thought I point out that the limitation on only upgrading by 2 major versions is for the case that you are upgrading a production system and don't want to lose any running jobs. If you are upgrading the whole operating system, you are probably planning a downtime anyway and so there won't be any such jobs. In this case, there shouldn't in theory be a problem - although I must admit that I wouldn't be that surprised if converting the database from 2.3.4 to, say, 17.02.7 didn't go 100% smoothly. However, Debian users who just rely on Debian packages are always going to face this problem of large version jumps between Debian releases, and so it would be useful for the community to know how well this works. Cheers, Loris -- Dr. Loris Bennett (Mr.) ZEDAT, Freie Universität Berlin Email [email protected]
