Hi, > Am 04.08.2015 um 04:43 schrieb Michael Stauffer <mgsta...@gmail.com>: > > Hi agian, > > I've got my cluster almost back up after upgrading to Rocks 6.2. > > Regarding installing SoGE 8.1.8 - I'm wondering how to do this. Is it as > simple as yum-installing the rpm(s?) on the head and compute nodes, then > using the load_sge_config.sh script on the head node? I haven't found any > documentation on this. Thanks for any suggestions.
You have to run the usual installation procedure after installing the rpms. Then you can remove the default queue and any hostlists and load the former configuration. As there may be some new entries, the load of the configuration may fail. While some of the read-config-from-file commands will just neglect the missing entries, others ones which will complain about them. -- Reuti > > -M > > On Sat, Aug 1, 2015 at 2:49 PM, Michael Stauffer <mgsta...@gmail.com> wrote: > On Sat, Aug 1, 2015 at 1:47 PM, Reuti <re...@staff.uni-marburg.de> wrote: > > Am 31.07.2015 um 20:55 schrieb Michael Stauffer: > > > I haven't, I'm doing the upgrades tomorrow. > > > > I've looked at the scripts you mention and it looks different from > > util/upgrade_modules/save_sge_config.sh and > > util/upgrade_modules/load_sge_config.sh which have also been recommended to > > me. Seems the don't call each other. Any idea why there are two such paired > > scripts and which I should use? > > These are different types of backup/restore: > > The save/load_sge_config.sh you can use multiple times, although no update is > intended. Just to save/backup and restore a configuration - this will create > text files with the information gained by issuing SGE commands. > > With inst_sge backup/restore the classic or BDB files are saved as they are. > > With the update procedure all daemons on the exechosts will be updated to a > new version (although often an un-tar of the binaries is sufficient). > > inst_sge will also load a former saved configuration, which was done with > save_sge_config.sh by hand (depending on the command line options). > > === > > In your case I assumed you already have an empty SGE configuration, so that > no update on all machines of the binaries need to be performed. > > Yes. I'll be installing SoGE. I'll try the save/load_sge_config.sh method > first. Fingers crossed that the config load is the same between SoGE and OGS. > Thanks! > > -M > > > -- Reuti > > > > > > Thanks. > > > > -M > > > > On Fri, Jul 31, 2015 at 3:33 AM, Rémy Dernat <remy...@gmail.com> wrote: > > Have you tried ./inst_sge -rst on your fresh install after a backup of the > > previous Sge ( ./inst_sge -bup ) ? > > > > Le 29 juil. 2015 22:29, "Michael Stauffer" <mgsta...@gmail.com> a écrit : > > On Wed, Jul 29, 2015 at 4:01 PM, Reuti <re...@staff.uni-marburg.de> wrote: > > Hi, > > > > Am 29.07.2015 um 21:22 schrieb Michael Stauffer: > > > > > I'm upgrading a rocks 6.1 system to 6.2 this weekend. I'll be doing a > > > clean install of rocks. Both rocks 6.1 & 6.2 have OGS/GE 2011.11p1 (at > > > least as far as I can tell, 6.2 has the same version). > > > > Would it be possible to move to a newer version? AFAICS OGS didn't get much > > updates for some time now and I don't know about its current state. > > > > Thanks for the reply Reuit. Yes OGS seems very stagnant - the current > > version is from july 2012. > > > > In terms of a newer version, I figure you mean using Son of GE? I probably > > chose OGS when I setup this cluster a couple years ago because it came with > > an OGS roll. I imagine my setup should migrate easily to Son of GE? > > > > Univa GE Core looks old too, the master on github is 3 years old. > > > > I imagine other forks will work with Rocks but I've never tried and don't > > know about installation complications. I'll have to ask on the Rocks list. > > Does anyone here have experience using Son of GE on Rocks? > > > > > Could someone help me with the steps to do the migration of my SGE setup? > > > I have this so far: > > > > > > On the old rocks 6.1 install: > > > > > > 1) run /opt/gridengine/util/upgrade_modules/save_sge_config.sh and save > > > to external location > > > > > > On the new rocks 6.2 install: > > > > > > 1) copy over the output from save_sge_config.sh > > > 2) Now, do I run > > > > > > $SGE_ROOT/inst_sge -upd > > > > > > OR > > > > > > /opt/gridengine/util/upgrade_modules/load_sge_config.sh > > > > After you installed the new version (and maybe removed the usual all.q, > > defined host/hostgroups,...) this can be used to load the old configuration > > into the new empty SGE installation. But I remember that it may be > > necessary to run it more than once, in case there are some mutual > > references (like in the list of subordinated queues). > > > > The script can fail anyway, in case that there are new entries in the > > definition of objects in case you upgrade to a much newer version (well, > > these could be added by hand to the text files if its known what is > > missing). > > > > Yes I saw too that load_sge_config may need to be run twice. I'm less > > optimistic about this working if I switch to Son of GE - but if it fails I > > can recreate by hand if I have to. > > > > -M > > > > > > -- Reuti > > > > > > > > > > OR > > > > > > /opt/gridengine/util/upgrade_modules/inst_upgrade.sh > > > > > > Are there any options for these commands that I haven't been able to > > > figure out? Or do I so something else altogether? Thanks! > > > > > > -M > > > _______________________________________________ > > > users mailing list > > > users@gridengine.org > > > https://gridengine.org/mailman/listinfo/users > > > > > > > > _______________________________________________ > > users mailing list > > users@gridengine.org > > https://gridengine.org/mailman/listinfo/users > > > > _______________________________________________ users mailing list users@gridengine.org https://gridengine.org/mailman/listinfo/users
