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 ECB0D18AFC for ; Fri, 12 Jun 2015 13:11:07 +0000 (UTC) Received: (qmail 40928 invoked by uid 500); 12 Jun 2015 13:11:06 -0000 Delivered-To: apmail-airavata-dev-archive@airavata.apache.org Received: (qmail 40878 invoked by uid 500); 12 Jun 2015 13:11:06 -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 40852 invoked by uid 99); 12 Jun 2015 13:11:06 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Jun 2015 13:11:06 +0000 Received: from [192.168.2.23] (cpe-76-181-96-148.insight.res.rr.com [76.181.96.148]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 06B871A006D for ; Fri, 12 Jun 2015 13:10:54 +0000 (UTC) From: Suresh Marru Content-Type: multipart/alternative; boundary="Apple-Mail=_62EB888E-D0CE-4C55-981D-8D1458800489" Subject: [DISCUSS] Data models for 0.16 and beyond Message-Id: <3D22EC93-A7C0-4EDA-9C97-5B2E44AE927D@apache.org> Date: Fri, 12 Jun 2015 09:09:55 -0400 To: Airavata Dev Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) X-Mailer: Apple Mail (2.2098) --Apple-Mail=_62EB888E-D0CE-4C55-981D-8D1458800489 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi All, With the experience of adapting thrift data models for Airavata in past = couple of years, its time for us to revisit them. Most persistent = criticism has been the data models have been complex. Next the data = models and architecture evolved in parallel and the implementations did = not always match the intended models. In an effort to address these = issues, lets first discuss the minimal required data models. We need to confirm the models to the general principle of Experiments = deriving into a Process or a Workflow. For single application, a process = can be directly derived from Experiment Details. For workflows, multiple = process are created. Executing a process leads to creation of multiple = Tasks. Task is a general type which are enacted at run time based on a = generic execution sequence of environment setup, data input staging, = application execution and monitoring, data output staging and = environment cleanup. Please review the initial draft: = https://github.com/apache/airavata/tree/master/thrift-interface-descriptio= ns/airavata-data-models = Assume lazy consensus and update the models, lets literately review and = update these thrift IDL=E2=80=99s. We don=E2=80=99t yet need to dive = into code generation, until these are close to final. @Supun, may be you can start thinking on the data base representation on = these models and assume the details will change but the general = structure might remain. Cheers, Suresh= --Apple-Mail=_62EB888E-D0CE-4C55-981D-8D1458800489 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Hi All,

With the experience of adapting thrift data models for = Airavata in past couple of years, its time for us to revisit them. Most = persistent criticism has been the data models have been complex. Next = the data models and architecture evolved in parallel and the = implementations did not always match the intended models. In an effort = to address these issues, lets first discuss the minimal required data = models.

We = need to confirm the models to the general principle of Experiments = deriving into a Process or a Workflow. For single application, a process = can be directly derived from Experiment Details. For workflows, multiple = process are created. Executing a process leads to creation of multiple = Tasks. Task is a general type which are enacted at run time based on a = generic execution sequence of environment setup, data input staging, = application execution and monitoring, data output staging and = environment cleanup.

Please review the initial draft:
https://github.com/apache/airavata/tree/master/thrift-interface= -descriptions/airavata-data-models

Assume lazy consensus and update the = models, lets literately review and update these thrift IDL=E2=80=99s. We = don=E2=80=99t yet need to dive into code generation, until these are = close to final.

@Supun, may be you can start thinking on the data base = representation on these models and assume the details will change but = the general structure might remain.

Cheers,
Suresh
= --Apple-Mail=_62EB888E-D0CE-4C55-981D-8D1458800489--