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 3BE8110939 for ; Mon, 3 Feb 2014 19:53:17 +0000 (UTC) Received: (qmail 14241 invoked by uid 500); 3 Feb 2014 19:53:10 -0000 Delivered-To: apmail-airavata-dev-archive@airavata.apache.org Received: (qmail 14135 invoked by uid 500); 3 Feb 2014 19:53:09 -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 13965 invoked by uid 99); 3 Feb 2014 19:53:07 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Feb 2014 19:53:07 +0000 Date: Mon, 3 Feb 2014 19:53:07 +0000 (UTC) From: "Suresh Marru (JIRA)" To: dev@airavata.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AIRAVATA-991) Craft the Airavata 1.0 API MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AIRAVATA-991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Marru updated AIRAVATA-991: ---------------------------------- Issue Type: Story (was: New Feature) > Craft the Airavata 1.0 API > -------------------------- > > Key: AIRAVATA-991 > URL: https://issues.apache.org/jira/browse/AIRAVATA-991 > Project: Airavata > Issue Type: Story > Components: Airavata API > Affects Versions: 0.11 > Reporter: Suresh Marru > Assignee: Suresh Marru > Fix For: 1.0 > > > An important goal for Airavata 1.0 release is to draft a public facing API which includes subset of functionality exposed by the internal SPI and higher level functions which can be realized by one of more internal components. > Airavata clients have to be abstracted from internal component level details and would like to interact through API through higher order method. Some of the capabilities include abilities to Register gateways, computational credentials, register and manage applications, create, configure and launch experiments (binding them to applications/workflows), monitor real-time and poll based progress, query for generated data and analyze results. > These capabilities can be realized by one or more internal Airavata components and the API layers abstracts these out and maps appropriately. -- This message was sent by Atlassian JIRA (v6.1.5#6160)