Return-Path: X-Original-To: apmail-airavata-dev-archive@www.apache.org Delivered-To: apmail-airavata-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 375E51007A for ; Sat, 4 May 2013 15:31:20 +0000 (UTC) Received: (qmail 26060 invoked by uid 500); 4 May 2013 15:31:20 -0000 Delivered-To: apmail-airavata-dev-archive@airavata.apache.org Received: (qmail 25879 invoked by uid 500); 4 May 2013 15:31:19 -0000 Mailing-List: contact dev-help@airavata.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@airavata.apache.org Delivered-To: mailing list dev@airavata.apache.org Received: (qmail 25864 invoked by uid 99); 4 May 2013 15:31:19 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 04 May 2013 15:31:19 +0000 X-ASF-Spam-Status: No, hits=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [128.149.139.109] (HELO mail.jpl.nasa.gov) (128.149.139.109) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 04 May 2013 15:31:13 +0000 Received: from mail.jpl.nasa.gov (ap-ehub-sp02.jpl.nasa.gov [128.149.137.149]) by smtp.jpl.nasa.gov (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r44FUpVD026664 (using TLSv1/SSLv3 with cipher AES128-SHA (128 bits) verified NO); Sat, 4 May 2013 08:30:52 -0700 Received: from AP-EMBX-SP40.RES.AD.JPL ([169.254.7.50]) by ap-ehub-sp02.RES.AD.JPL ([fe80::dd85:7b07:1e36:7e3c%15]) with mapi id 14.02.0342.003; Sat, 4 May 2013 08:30:52 -0700 From: "Mattmann, Chris A (398J)" To: "dev@airavata.apache.org" , "dev@oodt.apache.org" Subject: Re: Configuration management for Airavata integration with OODT file Manager server Thread-Topic: Configuration management for Airavata integration with OODT file Manager server Thread-Index: AQHOSM6/Kt9e9r/h7kiYsKvT57Ni+pj1JxgA Date: Sat, 4 May 2013 15:30:51 +0000 Message-ID: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.2.130206 x-originating-ip: [128.149.137.113] Content-Type: text/plain; charset="us-ascii" Content-ID: <1A2BC3C6CD5760499350EA36AF554529@ad.jpl> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Source-Sender: chris.a.mattmann@jpl.nasa.gov X-AUTH: Authorized X-Virus-Checked: Checked by ClamAV on apache.org 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 Reply-To: "dev@airavata.apache.org" Date: Saturday, May 4, 2013 6:52 AM To: "dev@airavata.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