[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Testbed
Chip, Karen:
I try to understand better the requirements of your testbed suggestion. As
part of this I would like to point out to you that some solutions to your
problems already exist as part of the activities the Globus team pursues.
1) Java CoG can handle multiple credentials, a JSP interface is available
through JPDK, a Web interface based on CGI and HTML has been developed by
the Cactus group. Together with myProxy a convenient way to integrate this
in "dusty" web servers is possible.
2) I have to better understand what "running" Globus means. One way of
looking at this is Globus provides an Information service. A site may only
want to install this information service but not the rest of "Globus". It
is easy to integrate other information services within this Information
services, called MDS2. MDS2 has the security build in. If you do not want
to install MDS2 on your machine for one or the other reason, you have to
reimplement a service doing exactly this.
3) GSIFTP or GRIDFTP provide file staging abilities that can be performed on
web servers through the Java CoG Kit. A rewrite of JavaFilesynchronizer
could do simple replication.
4) We can technically submit remote jobs through web services.
Thus, I assume Globus will be considered as part of the testbed?
Nevertheless, I also difficulties understanding (4) in your original mail.
Example: if I do not know what system or infrastructure I, I can not make
the decision what information/commands I should submit to this
infrastructure. At least I must know my app is written in this
language/framework, it is compilable/runable on this platforms, I can send
this out to a broker that looks for resources matching my requirements.
Thanks
Gregor
---------- Forwarded message ----------
Date: Tue, 12 Jun 2001 15:49:18 -0400
From: Chip Watson <chip.watson@jlab.org>
To: Karen Schuchardt <kl_schuchardt@pnl.gov>
Cc: gce-wg@gridforum.org
Subject: Re: GCE testbed activity
Karen et al,
I'd be interested in some testbed / interoperability studies. I'm curious
about
what capabilities you would propose to be distributed. Our efforts are
targetted toward distribution of data, and then later distribution of batch
jobs. For a single site, we are working towards having the portal provide
a lot of information to a web browser to view and manipulate storage and
batch jobs, ultimately providing for configuring and launching science
applications w/o logging in to the site, just using secure web.
So, what might a testbed look like? Here's a few, based upon our near
term goals of basic infrastructure capability:
1) demonstrate security interoperability (accepting each others
certificates, even if signed by different CA's)
2) demo displaying status of a remote site, with info retrieved via web
services
i.e. PNL testbed portal showing status of machines at Jlab (which is not
running globus)
3) demonstrate requesting file staging or transfer using web services
4) demonstrate launching remote batch job (against system with foreign
or unknown infrastructure implementation) using web services
What is on your list?
Regards,
Chip
--
Chip Watson
High Performance Computing Group
Thomas Jefferson National Accelerator Facility
Tel: (757) 269-7101
http://www.jlab.org/~watson