I followed these steps to install Slurm Install MUNGE for authentication. Make sure that all nodes in your cluster have the same munge.key. Make sure the MUNGE daemon, munged is started before you start the Slurm daemons. bunzip2 the distributed tar-ball and untar the files: tar --bzip -x -f slurm*tar.bz2 cd to the directory containing the Slurm source and type ./configure with appropriate options, typically --prefix= and --sysconfdir= Type make to compile Slurm. Type make install to install the programs, documentation, libraries, header files, etc.
-----Original Message----- From: Uwe Sauter [mailto:[email protected]] Sent: Wednesday, February 11, 2015 2:27 PM To: slurm-dev Subject: [slurm-dev] Re: Upgrade Slurm to latest version Depends on how you installed Slurm. Which distro / package manager? Self compiled? Am 11.02.2015 um 20:23 schrieb Los, Mark J: > I believe I am going to attempt a fresh install with version 14.11.3. Is > there a way to un-install the current version I have on the server before I > install the new version? > > -----Original Message----- > From: Uwe Sauter [mailto:[email protected]] > Sent: Wednesday, February 11, 2015 9:29 AM > To: slurm-dev > Subject: [slurm-dev] Re: Upgrade Slurm to latest version > > > Hi, > > as far as I know (and someone please correct me if I'm wrong) Slurm will > support the two latest minor releases. So 14.11 would support 2.6 but not 2.4 > so yes, an intermediate upgrade is necessary. > > If you could afford some downtime it should be possible to "just" do the > intermedaite upgrades to the Slurm Database for schema updates (probably best > to go 2.4 -> 2.6 -> 14.3 -> 14.11). slurmd and slurmctl then could be > upgraded directly. > > I don't know if it is necessary to make a new config file but if you'd like > to use new features you might want to consider starting over with a fresh > config. > > > Regards, > > Uwe > > > Am 11.02.2015 um 14:45 schrieb Los, Mark J: >> It looks like the upgrade document suggests an intermediate upgrade since I >> am currently at 2.2.4 and want to get to 14.11.3. What upgrade would you >> recommend or is it possible to go directly to 14.11.3? >> >> -----Original Message----- >> From: Uwe Sauter [mailto:[email protected]] >> Sent: Tuesday, February 10, 2015 4:01 PM >> To: slurm-dev >> Subject: [slurm-dev] Re: Upgrade Slurm to latest version >> >> >> Hi Mark, >> >> most of your questions are answered in the upgrade section of this page: >> http://slurm.schedmd.com/quickstart_admin.html >> >> If you have more questions after reading this, feel free to come back. >> >> >> Regards, >> >> Uwe >> >> >> >> >> Am 10.02.2015 um 20:47 schrieb Los, Mark J: >>> I have been asked to upgrade our current Slurm environment currently >>> at version 2.4.4 to version 14.11.3 and have a few questions before I >>> proceed. >>> >>> >>> >>> Can I go directly to version 14.11.3 or do I need to perform an >>> intermediate upgrade first since the gap between versions is quite large. >>> >>> >>> >>> Can I upgrade just one server at a time or do all of the servers >>> that currently run 2.4.4 need to be upgraded at the same time. >>> >>> >>> >>> Will the current slurm.conf file still be used or will a new >>> slurm.conf file be generated with the upgrade. >>> >>> >>> >>> If there is an problem with the upgrade, can I revert back to the >>> current version and how do I accomplish this. >>> >>> >>> >>> Is it ok to delete the old version (remove directories) once the new >>> version has been installed. >>> >>> >>> >>> Any information that you can provide me would be greatly appreciated. >>> >>> >>> >>> Regards >>> >>> >>> >>> Mark Los >>> >>> Federated Investors >>> >>> BISD, Computing Infrastructure >>> >>> 724-743-2308 – Work >>> >>> 412-334-3841 - Cell >>> >>> >>> >>> -------------------------------------------------------------------- >>> - >>> - >>> -- Unless notified to the contrary by the sender, the recipient >>> should consider the contents of this message including any >>> attachments to be confidential. If you are not the intended >>> recipient and have received this message in error, please contact >>> Federated Investors immediately by forwarding this email to >>> [email protected] and then delete this message from your >>> system. Saving, copying or disseminating an inadvertently received >>> email could violate state and Federal privacy laws. All emails >>> received by or sent from Federated may be provided to regulators or >>> law enforcement agencies, or used for other purposes consistent with >>> Federated's business interests. Thank you for your cooperation. >>> >> >> >> Unless notified to the contrary by the sender, the recipient should consider >> the contents of this message including any attachments to be confidential. >> If you are not the intended recipient and have received this message in >> error, please contact Federated Investors immediately by forwarding this >> email to [email protected] and then delete this message from your >> system. Saving, copying or disseminating an inadvertently received email >> could violate state and Federal privacy laws. All emails received by or sent >> from Federated may be provided to regulators or law enforcement agencies, or >> used for other purposes consistent with Federated's business interests. >> Thank you for your cooperation. >> > > > Unless notified to the contrary by the sender, the recipient should consider > the contents of this message including any attachments to be confidential. If > you are not the intended recipient and have received this message in error, > please contact Federated Investors immediately by forwarding this email to > [email protected] and then delete this message from your system. > Saving, copying or disseminating an inadvertently received email could > violate state and Federal privacy laws. All emails received by or sent from > Federated may be provided to regulators or law enforcement agencies, or used > for other purposes consistent with Federated's business interests. Thank you > for your cooperation. > Unless notified to the contrary by the sender, the recipient should consider the contents of this message including any attachments to be confidential. If you are not the intended recipient and have received this message in error, please contact Federated Investors immediately by forwarding this email to [email protected] and then delete this message from your system. Saving, copying or disseminating an inadvertently received email could violate state and Federal privacy laws. All emails received by or sent from Federated may be provided to regulators or law enforcement agencies, or used for other purposes consistent with Federated's business interests. Thank you for your cooperation.
