From: Mary Thompson (mrthompson@lbl.gov)
Date: Tue Apr 02 2002 - 11:03:55 PST
Sam had installed slightly older versions of the code. I just copied
over the newer files from
/sandbox/slang/globus/beta2/gram/{jobmanager,protocol} and
build/installed them. It now works as expected thru a personal
gatekeeper.
The AkentiServer was up and running. The way you can test this is grep
the results of ps for "AkentiServer". If anyone needs to restart the
server, use /p/fusiongrid/mrthomps/akentiInstall/startAkentiServer.sh,
then look in logs/server.log and make sure there is a "Starting Akenti
Insecure Server at 8440" message.
I think I have set the policy files to match what the demo script is
running, namely that the executable that the job manager sees is
transp_enqueue. If that is wrong just give me call and I can fix it.
You will not be able to run other things like /bin/date and /bin/echo.
If that is a problem for testing I can map any specific list of
executables.
Mary
Wasef Masood wrote:
>
> Mary,
>
> Is there a dir which contains modifications that both you and kate
> made? It looks like your working dir on bluebeat:
> /p/fusiongrid/mrthomps/globus/gram/jobmanager
> has all the edits and we could build packages from this and modify the
> installation.
>
> Also, Did you take your code from the dir:
> /sandbox/slang/globus/beta2/gram/jobmanager/source/
>
> This was what Sam and I had worked on friday evening and tested it on
> binary beta1.
>
> Wasef Masood
> masood@mcs.anl.gov
> Distributed Systems Laboratory
> Mathematics and Computer Science Division
> Argonne National Laboratory
>
> On 1 Apr 2002, Sam Lang wrote:
>
> >
> > The modified jobmanager packages are now installed on top of the beta1
> > installation at:
> >
> > /opt/grid/globus-2.0
> >
> > It looks like there were some packaging files that didn't actually get
> > installed during the initial installation, so its kind of surprising to
> > me that the installation actually worked previously. In either case, I
> > had to build the unmodified jobmanager code first, and then built the
> > modified jobmanager code on top of that.
> >
> > I also went ahead an changed the jobmanager install code so that
> > AKENTI_LOCATION now needs to be set to the akentiDist directory, so
> > that:
> >
> > $AKENTI_LOCATION/release/<platform>/{include|lib}
> >
> > resolves to headers and libs. In the case of bluebeat, I've got:
> >
> > export AKENTI_LOCATION=/p/fusiongrid/mrthomps/akentiDist/
> >
> > It looks like the Akenti install code just works on linux and solaris
> > platforms, so the modified job manager code is the same.
> >
> > ----
> >
> > I did some testing, and things seem at least to run, although I can't
> > verify exactly if they are the correct things. Mary, when I use
> > /bin/date as the executable, it works (I get the date). This is the
> > opposite of what you said, so there may be something wrong here.
> > Although, when i set it to keep the jobmanager logs, it does say that
> > calling Akenti failed:
> >
> > 4/2 00:44:42 Akenti: calling Akenti
> > 4/2 00:44:42 Akenti: calling Akenti failed
> >
> > So that's as far as I've gotten - I'm going to hand off the rest of the
> > testing on bluebeat to Mary or Wasef. Let me know if there are any
> > other installation issues.
> >
> > ----
> >
> > For my future sanity, I ask (beg, if necessary) that everyone use CVS
> > from now on for modifying the akenti jobmanager code. The repository is
> > at /sandbox/slang/CVS on gainly. To check out the code is relatively
> > straightforward. If you are on gainly:
> >
> > export CVSROOT=/sandbox/slang/CVS
> > cvs co jobmanager
> >
> > If you are on a remote machine:
> >
> > export CVSROOT=username@gainly.mcs.anl.gov:/sandbox/slang/CVS
> > export CVS_RSH=ssh
> > cvs co jobmanager
> >
> > If necessary, I can give further instructions on using CVS, and adding
> > modified code to it. The host may change from gainly in the future,
> > I'll let you know if it does.
> >
> > -Sam
> >
This archive was generated by hypermail 2.1.4 : Mon Apr 15 2002 - 23:30:56 PDT