[Swift-devel] sites.xml
Tiberiu Stef-Praun
tiberius at ci.uchicago.edu
Fri Mar 2 09:52:01 CST 2007
Given the deluge of information available these days, our goal should
move from providing the information to locating where the information
is already provided.
That means providing the idea, and linking to the full documentation.
For instance, I did not know where to search for GLOBUS::queue=ABC.
Apparently these parameters are connected to RSL. There are lots of
cases where these connections need to be made explicit for
new/unexperienced users.
Tibi
On 3/2/07, Mihael Hategan <hategan at mcs.anl.gov> wrote:
> On Fri, 2007-03-02 at 11:41 +0000, Ben Clifford wrote:
> > In bug 32, Mihael commented:
> >
> > > The handshake failure is caused by the fact that the url is not valid.
> > > GT4 does not use /jobmanager-xyz in the URL, and therefore the one you
> > > use is trying to access a non-WSRF URL in the container (which causes
> > > the GSI handshake to fail, because it gets some 404 page back).
> >
> > > This brings up a problem. The GT2 style job manager specification is
> > > clearly not portable. In cog, resources (aka services) have an
> > > additional jobManager attribute which can be used to portably specify
> > > job managers, and the providers take care of translating that into
> > > whatever the implementation requires. However, this would require a
> > > modification on the structure of the sites.xml file. I think it should
> > > be OK to add a jobManager attribute, while still allowing the
> > > /jobmanager-xyz thing for classic GRAM resources, but not for WS-GRAM.
> >
> > There's no real backwards compatibility reason to stick with anything like
> > the sites.xml format that we have now.
>
> Aside, perhaps, from the fact that the documentation is already written
> for that.
>
> > Some of the stuff is out of place
> > in there already and eventually it might warrant a big tidyup.
> >
> > Also, WS-GRAM (at least in theory) doesn't use URLs with a job-manager -
> > it uses an opaque EPR in the form of an XML blob. Alas, these are so
> > appallingly unusable that for the most part people have settled on rigid
> > structure for the EPRs when that rigid structure shouldn't be there. Roll
> > on the day when someone actually fixes that. Come back GT3. All is
> > forgiven.
> >
> > VDS already has a way to specify GRAM4 resources but I can't remember.
> > Maybe its similar to the one used by condor - they use this format for the
> > jobmanager string (it wrapped on paste - newlines are spaces):
> >
> > grid_resource = gt4
> > [https://]IPaddress[:port][/wsrf/services/ManagedJobFactoryService]
> > scheduler-string
> >
> > (according to
> > http://www.cs.wisc.edu/condor/manual/v6.8/5_3Grid_Universe.html#SECTION00632400000000000000)
> >
>
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>
--
Tiberiu (Tibi) Stef-Praun, PhD
Research Staff, Computation Institute
5640 S. Ellis Ave, #405
University of Chicago
http://www-unix.mcs.anl.gov/~tiberius/
More information about the Swift-devel
mailing list