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 6F29D10045 for ; Tue, 9 Jul 2013 21:21:26 +0000 (UTC) Received: (qmail 15129 invoked by uid 500); 9 Jul 2013 21:21:26 -0000 Delivered-To: apmail-airavata-dev-archive@airavata.apache.org Received: (qmail 15098 invoked by uid 500); 9 Jul 2013 21:21:26 -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 15088 invoked by uid 99); 9 Jul 2013 21:21:26 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Jul 2013 21:21:26 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of thejaka.amila@gmail.com designates 209.85.219.50 as permitted sender) Received: from [209.85.219.50] (HELO mail-oa0-f50.google.com) (209.85.219.50) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Jul 2013 21:21:22 +0000 Received: by mail-oa0-f50.google.com with SMTP id k7so8606149oag.37 for ; Tue, 09 Jul 2013 14:21:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=YiwqSvq5/c8b9r5J0cInQea1yK7c7J6rvPx7lonVGT8=; b=V6zAe4RZUyvgnXVw5qmJHuqB9NUas9cDxtxPydeR7N4LJG/6cukqo9mP/4lmKvk44N CycTVIf9w3bv4eAk9Qkc7GgHIBX8SpPnS9JUeRKkmExu1XG0z7wXe0QAT6BuZyvmi+3c iSd++1D3qSEoKsrRCsNyh7eBSC8mEtLHm0eJwZAfapVMj+T3KUWHklBwgY30YaI5xOGr AOUOlV6s+TLG9Q5vFNGE1xWAfZU8vhsnLBjWLPEIWKMXICTfrX8xZD2ABKdr8HFinxso 18wp3AqplBOs4M4fnFgeRxBXI5Nf1u09qlbM8KV7wbbyhBFHmT3XnUj8Qx76riX+SRVI SYjQ== MIME-Version: 1.0 X-Received: by 10.60.140.168 with SMTP id rh8mr25723650oeb.17.1373404861351; Tue, 09 Jul 2013 14:21:01 -0700 (PDT) Received: by 10.76.119.10 with HTTP; Tue, 9 Jul 2013 14:21:01 -0700 (PDT) Date: Tue, 9 Jul 2013 17:21:01 -0400 Message-ID: Subject: Upgrading JGlobus version 2.0.6-RC2 From: Amila Jayasekara To: dev@airavata.apache.org, users Content-Type: multipart/alternative; boundary=047d7b2e4c46e4cce504e11abc7b X-Virus-Checked: Checked by ClamAV on apache.org --047d7b2e4c46e4cce504e11abc7b Content-Type: text/plain; charset=ISO-8859-1 Hi All, Within next two days I am planning to upgrade JGlobus [1] version to 2.0.6-RC2. With the upgrade I am also planning to introduce following functionalities at GFac level. 1. Recovery mechanisms at GFac level a. Two phase commit b. Resuming Job monitoring after Airavata restarts 2. Job cancellation at GFac API level Some of the FAQs are answered below; a. Why upgrade ? We had been using cog-jglobus 1.8.0 for grid communication. This is a fairly old library and some of the functionalities are not supported. (E.g:- TLS communication, SHA2 support, Support to handle X509Certificates using Java objects) b. Why "RC2" ? We have tested 2.0.6-RC2 against functionalities we use within GFac. You may find these test cases in [2]. c. What are the areas tested ? Tests cover, myproxy operations, file transfer operations and job submission. Further these tests were ran against trestles, lonestar and stampede providers. d. From where we going to pick 2.0.6-RC2 jars ? Since 2.0.6-RC2 is not yet released we will add these jars as file system repo to trunk. Plan is to get JGlobus 2.0.6 release out before 0.9 release. Relevant Jira is in [3]. Comments/objections/concerns welcome. [1] https://github.com/jglobus/JGlobus [2] https://svn.apache.org/repos/asf/airavata/sandbox/grid-tools (See README for details) [3] https://issues.apache.org/jira/browse/AIRAVATA-883 --047d7b2e4c46e4cce504e11abc7b--