[gridengine users] how to migrate OGS

Rémy Dernat remy.d1 at gmail.com
Fri Jul 31 07:33:17 UTC 2015


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" <mgstauff at gmail.com> a écrit :

> On Wed, Jul 29, 2015 at 4:01 PM, Reuti <reuti at 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 at gridengine.org
>> > https://gridengine.org/mailman/listinfo/users
>>
>>
>
> _______________________________________________
> users mailing list
> users at gridengine.org
> https://gridengine.org/mailman/listinfo/users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gridengine.org/pipermail/users/attachments/20150731/6c55116a/attachment.html>


More information about the users mailing list