[ogsa-hpcp-wg] [SAGA-RG] Hosted applications

[Ravi Madduri]

There is some work being done in Globus as part of the gRAVI project.  
We do use JSDL to generate Grid Job templates for provisioning  
applications that are exposed as Grid services. We also integrated  
this work with Virtual workspaces where provisioning happens using EC2- 
style hosting mechanisms. Our goal was to generate a fully functional,  
secure grid service without writing a single line of code ( for the  
simplest usecase). More details can be found here:

http://dev.globus.org/wiki/Incubator/gRAVI

This is being used in the caBIG community and in the DoE community.  
More details here on the scidac website here : http://www.scidac.gov/

Regards


On Aug 25, 2008, at 12:24 PM, Steven Newhouse wrote:

> There is also a bit of overlap here with the Application Template  
> done in the HPC Profile WG.
>
> http://forge.gridforum.org/sf/docman/do/downloadDocument/projects.ogsa-hpcp-wg/docman.root.drafts.application_template/doc15034
>
> The main goal of this spec is to reduce the amount of info the user  
> has to specify in a JSDL document and let the system admin provide  
> (server side) the details needed to run a particular admin on a  
> local cluster.
>
> Steven
>
>> -----Original Message-----
>> From: saga-rg-bounces at ogf.org [mailto:saga-rg-bounces at ogf.org] On
>> Behalf Of Malcolm Illingworth
>> Sent: Monday, August 25, 2008 10:15 AM
>> To: 'SAGA RG'
>> Subject: Re: [SAGA-RG] Hosted applications
>>
>> Hi Thilo,
>>
>> I'm afraid its rather a contrived example. This would execute a bash
>> script
>> using the bash environment.
>>
>> The idea is that UNICORE supports "applications as a service". For
>> example,
>> imagine an application installed at a large number of sites.  
>> Different
>> sites
>> might install the application in different locations, eg for local
>> operating
>> reasons. To avoid the user having to know the location at each site,
>> UNICORE
>> can expose the application as a "service" at each site. So, another
>> contrived example could be as follows:
>>
>>  <jsdl:JobDescription>
>>        <jsdl:Application>
>>          <jsdl:ApplicationName>CPMD</jsdl:ApplicationName>
>>          <jsdl:ApplicationVersion>3.1.16</jsdl:ApplicationVersion>
>>          <jsdl1:POSIXApplication
>>  xmlns:jsdl1="http://schemas.ggf.org/jsdl/2005/11/jsdl-posix">
>>            <jsdl1:Environment
>> name="INPUT_DATA">mydata.dat</jsdl1:Environment>
>>          </jsdl1:POSIXApplication>
>>        </jsdl:Application>
>>      </jsdl:JobDescription>
>>
>> This would run a CPMD instance, without the user having to know the
>> exact or
>> even relative location of the application.
>>
>> Hope this makes things a bit clearer?
>>
>> Malcolm.
>> (ps perhaps this is overlapping with the service discovery API?)
>>
>>
>> -----Original Message-----
>> From: Thilo Kielmann [mailto:kielmann at cs.vu.nl]
>> Sent: 25 August 2008 17:39
>> To: Malcolm Illingworth
>> Subject: Re: [SAGA-RG] Hosted applications
>>
>> Malcolm,
>>
>> I am not fully understanding your example.
>> Can you please add what would actually be executed given this piece  
>> of
>> JSDL?
>>
>> I am wondering whether a relative path would be "good enough" or what
>> else
>> would be missing?
>> The "other end of the spectrum" would be to use the RPC package but
>> this
>> might be overkill.
>>
>> Curious...
>>
>>
>> Thilo
>>
>> On Mon, Aug 25, 2008 at 02:35:25PM +0100, Malcolm Illingworth wrote:
>>> From: Malcolm Illingworth <malcolm at epcc.ed.ac.uk>
>>> To: 'SAGA RG' <saga-rg at ogf.org>
>>> Subject: [SAGA-RG] Hosted applications
>>>
>>> Hi,
>>>
>>> My apologies if this is referring to an old discussion, but here  
>>> goes
>> ...
>>>
>>> UNICORE supports the concept of an "abstract" hosted application.
>> This
>>> means that an application is installed on a remote execution host,
>> and
>>> can be referred to via a name, rather than a path to the executable.
>>> In JSDL this would look something like:
>>>
>>> ==================================================
>>> <jsdl:JobDescription>
>>>       <jsdl:Application>
>>>         <jsdl:ApplicationName>Bash shell</jsdl:ApplicationName>
>>>         <jsdl:ApplicationVersion>3.1.16</jsdl:ApplicationVersion>
>>>         <jsdl1:POSIXApplication
>>> xmlns:jsdl1="http://schemas.ggf.org/jsdl/2005/11/jsdl-posix">
>>>           <jsdl1:Environment
>> name="SOURCE">input.sh</jsdl1:Environment>
>>>         </jsdl1:POSIXApplication>
>>>       </jsdl:Application>
>>>     </jsdl:JobDescription>
>>> ==================================================
>>>
>>> Any thoughts of how I could support this at the SAGA level? The SAGA
>>> job description defines an EXECUTABLE property, but I'm assuming  
>>> this
>>> has to be an actual path.
>>>
>>> Regards,
>>> Malcolm.
>>>
>>> ---------------------------------------------------- |epcc| -
>>>
>>> Malcolm Illingworth
>>> EPCC, University of Edinburgh
>>> James Clerk Maxwell Building
>>> Mayfield Road                   E-mail: malcolm at epcc.ed.ac.uk
>>> Edinburgh EH9 3JZ               Phone:  + 44 (0) 131 651 3388
>>> United Kingdom                  Fax:    + 44 (0) 131 650 6555
>>>
>>> -------------------------------------------------------------
>>>
>>> --
>>>  saga-rg mailing list
>>>  saga-rg at ogf.org
>>>  http://www.ogf.org/mailman/listinfo/saga-rg
>>
>>
>>
>> --
>> Thilo Kielmann
>> http://www.cs.vu.nl/~kielmann/
>>
>> --
>>  saga-rg mailing list
>>  saga-rg at ogf.org
>>  http://www.ogf.org/mailman/listinfo/saga-rg
>
> --
>  ogsa-hpcp-wg mailing list
>  ogsa-hpcp-wg at ogf.org
>  http://www.ogf.org/mailman/listinfo/ogsa-hpcp-wg

--
Ravi K Madduri
The Globus Alliance | Argonne National Laboratory | University of  
Chicago
http://www-unix.mcs.anl.gov/~madduri

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.ogf.org/pipermail/ogsa-hpcp-wg/attachments/20080825/f4ea645a/attachment-0001.html