2015-07-28 15:47 GMT+02:00 Andrew E. Bruno <[email protected]>: > > On Tue, Jul 28, 2015 at 06:30:09AM -0700, Marcin Stolarek wrote: > > 2015-07-28 15:08 GMT+02:00 Andrew E. Bruno <[email protected]>: > > > > > > > > We need to rename all the nodes in our cluster. Our thinking is to put > > > in a full-system reservation: > > > > > > scontrol create reservation nodes=ALL .. > > > > > > Take the nodes down and rename them. Then bring slurm backup configured > > > with the new names. > > > > > > What will happen when we bring slurm backup with all new node names? > > > Does the reservation store specific nodenames? or will the slurmdbd/ctl > > > handle this gracefully? > > > > > > Any suggestions on how best to rename all the nodes in a cluster? > > > > > > > As I understand you want to remove nodes and add new - with new names. > > In database/accounting this names have no special format, they are just > > "strings". > > So... old nodes (old names/ip's) from slurm.conf are going to be down and > > you need to add new entries to slurm.conf, but.... > > maybe I'm not getting what the problem is..? > > Wondering how the reservation will be handled.. when all the old names > go away. Are you suggesting just renaming the nodes directly in the db? >
but why you want to change anything in db? Historical jobs where running on nodes with old names. I haven't check this in code, but I'm pretty sure that "nodes=all" is changed to the list of all hosts configured in slurm.conf, so if you add new nodes (with new names) they are not going to be in previously created reservation. If you don't want to run jobs on the newly added nodes, you can change partition state to DOWN. cheers, marcin
