Chris, just FYI. From the RELEASE_NOTES file...
IMPORTANT NOTE: If using the slurmdbd (SLURM DataBase Daemon) you must update this first. The 2.2 slurmdbd will work with SLURM daemons of version 2.1.3 and above. You will not need to update all clusters at the same time, but it is very important to update slurmdbd first and having it running before updating any other clusters making use of it. No real harm will come from updating your systems before the slurmdbd, but they will not talk to each other until you do. Also at least the first time running the slurmdbd you need to make sure your my.cnf file has innodb_buffer_pool_size equal to at least 64M. You can accomplish this by adding the line So updating should work fine, just your clusters will need to be at least 2.1.3 to work correctly. If you update everything at the same time you shouldn't see any problems though. If you plan on running the DBD for a while before you update all your clusters any running 2.1.0 will not work, you will need at least 2.1.3. Danny > Exactly. Just upgrade the slurmdbd before anything else. > You should be able to upgrade slurm on your compute > clusters without losing any jobs or other state. > > Morris Jette > SchedMD LLC > > Quoting Chris Scheller <[email protected]>: > > > Jette, Moe wrote on Mon, Mar 07, 2011 at 03:24:08PM -0800: > >> There was a patch to SLURM v2.2 to support secondary groups. > > > > What is the upgrade path from 2.1.0 to 2.2? I saw notes about updating > > slurmdbd first but is it as simple as just shutting down the old > > slurmdbd and starting the new version or is there some migration of > > the db data/schema? > > > >> I am not aware of any current problems in supporting the > >> AllowGroups functionality. > >> The following patch can be used to list the uids in each of the > >> groups listed in an > >> AllowGroups parameter. That should help to show you what is happening. Note > >> that the code in this function has several different paths for > >> various operating > >> systems (AIX, Sun, OS X, Linux), so there might be some issue in support of > >> your particular OS. > >> > >> Index: src/slurmctld/partition_mgr.c > >> =================================================================== > >> --- src/slurmctld/partition_mgr.c (revision 22674) > >> +++ src/slurmctld/partition_mgr.c (working copy) > >> @@ -1300,8 +1300,10 @@ > >> "configured group %s", > >> grp_result->gr_mem[i], > >> group_name); > >> - else if (my_uid) > >> + else if (my_uid) { > >> group_uids[j++] = my_uid; > >> + info("group %s includes uid %u", > >> group_name, my_uid); > >> + } > >> } > >> } > >> } > >> @@ -1327,6 +1329,7 @@ > >> j++; > >> xrealloc(group_uids, ((j+1) * sizeof(uid_t))); > >> group_uids[j-1] = pwd_result->pw_uid; > >> + info("group %s includes uid %u", group_name, > >> pwd_result->pw_uid); > >> } > >> #ifdef HAVE_AIX > >> endpwent_r(&fp); > >> > >> > >> ________________________________________ > >> From: [email protected] > >> [[email protected]] On Behalf Of Chris Scheller > >> [[email protected]] > >> Sent: Monday, March 07, 2011 10:34 AM > >> To: [email protected] > >> Subject: [slurm-dev] AllowGroups > >> > >> I remember seeing a bug about AllowGroups and secondary groups prior > >> to the 2.2 release. Is the AllowGroups functionality completely broke > >> in previous versions? I'm running 2.1.0 and no matter primary group or > >> not I can't make this work. Every attempt gives me > >> > >> srun: error: Unable to allocate resources: User's group not permitted > >> to use this partition > >> > >> even thought the user has only one group(but the left over PAG id from > >> afs shows as a group) and the AllowGroups is set to that users gid. > >> > >> > >> > >> -- > >> Chris Scheller | http://www.pobox.com/~schelcj | JID: > >> [email protected] > >> ------------------------------------------------------------------------------ > >> Cabbage, n.: > >> A familiar kitchen-garden vegetable about as large and wise as > >> a man's head. > >> -- Ambrose Bierce, "The Devil's Dictionary" > >> > > > > -- > > Chris Scheller | http://www.pobox.com/~schelcj | jabber: [email protected] > > ---------------------------------------------------------------------------- > > Any small object that is accidentally dropped will hide under a larger > > object. > > > > > > >
