airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sanjaya Medonsa <sanjaya...@gmail.com>
Subject Re: Configuration management for Airavata integration with OODT file Manager server
Date Mon, 06 May 2013 00:47:27 GMT
Thanks Chris! I'll proceed with the proposed approach for the moment.

Best Regards,
Sanjaya


On Sat, May 4, 2013 at 9:00 PM, Mattmann, Chris A (398J) <
chris.a.mattmann@jpl.nasa.gov> wrote:

> I think I'll know better once I see some examples, Sanjaya,
> so looking forward to them, please proceed.
>
> Cheers,
> Chris
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.a.mattmann@nasa.gov
> WWW:  http://sunset.usc.edu/~mattmann/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
>
>
>
>
> -----Original Message-----
> From: Sanjaya Medonsa <sanjayamrt@gmail.com>
> Reply-To: "dev@airavata.apache.org" <dev@airavata.apache.org>
> Date: Saturday, May 4, 2013 6:52 AM
> To: "dev@airavata.apache.org" <dev@airavata.apache.org>,
> "dev@oodt.apache.org" <dev@oodt.apache.org>
> Subject: Configuration management for Airavata integration with OODT file
> Manager server
>
> >Hi,
> >Airavata integration with FileManager to stage file prior to excute
> >workflow task is based on the class PGETaskInstance of the OODT CAS-PGE
> >module. PGETaskInstance takes both dynamic metadata and workflow
> >configuration as an input and it combines them to create PgeMetaData
> >object. Main purpose of the Airavata integration with OODT is to stage
> >input files and ingest output data back to file manager server and
> >Metadata
> >catalog. Since workflow configuration is managed by Airavata itself, it is
> >possible to configure only dynamic Metadata which should configure items
> >such as QUERY_CLIENT_TRANSFER_SERVICE_FACTORY and
> >QUERY_FILE_MANAGER_URL(Then static Metadata is represented by Metadata
> >object which doesn't have any properties. Presence of both dynamic and
> >static Metadata is mandatory in PgeMetadata implementation). Please let me
> >know if you see any drawback with this approach of allowing to configure
> >only dynamic Metadata for Airavata integration with FileManagerServer to
> >stage files and making static Metadata empty.
> >I would like to see some sample configuration files for dynamic and static
> >Metadata.
> >
> >Best Regards,
> >Sanjaya
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message