Return-Path: 
 <dev-return-12133-apmail-airavata-dev-archive=airavata.apache.org@airavata.apache.org>
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 A720D10D98
	for <apmail-airavata-dev-archive@www.apache.org>;
 Thu, 29 May 2014 08:15:48 +0000 (UTC)
Received: (qmail 1760 invoked by uid 500); 29 May 2014 08:15:48 -0000
Delivered-To: apmail-airavata-dev-archive@airavata.apache.org
Received: (qmail 1710 invoked by uid 500); 29 May 2014 08:15:48 -0000
Mailing-List: contact dev-help@airavata.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@airavata.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@airavata.apache.org>
List-Post: <mailto:dev@airavata.apache.org>
List-Id: <dev.airavata.apache.org>
Reply-To: dev@airavata.apache.org
Delivered-To: mailing list dev@airavata.apache.org
Received: (qmail 1703 invoked by uid 99); 29 May 2014 08:15:48 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 May 2014 08:15:48 +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 swsachith@gmail.com
 designates 74.125.82.42 as permitted sender)
Received: from [74.125.82.42] (HELO mail-wg0-f42.google.com) (74.125.82.42)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 May 2014 08:15:43 +0000
Received: by mail-wg0-f42.google.com with SMTP id y10so12109040wgg.1
        for <dev@airavata.apache.org>; Thu, 29 May 2014 01:15:21 -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=VufZelASzVVvJxk2Cbs5jip9LWjQehO32uXV8pcyoHs=;
        b=iE1GUQFXxc2wjqhpzwLVPupdvFySGaEVBkljwvr0tq0FbrUcsuWR50KnFW8GxvrPGd
         95QnuBWqBUkeKqYLYQf+ffnvx0TUyyHrBzc+zDvsNBgm2I2OVqyBK4FSCdUfGKD88pAc
         QExYlB+XEKfrCQPwoYfnV8rQiJkk7yBOUMHLC2pYZ2G/AK3qFNwea8E5m2/OCATSxqW3
         hv5EVvlmiPsWvZ2HNIYOnbxykTbLWUQmVeEExVYPjCKfwqitLeBvpX2KDPZr1VkcXiKq
         wUisg2fw6gN4UR18zsMb/E5+D3Khc4Y8cCsATDAWEmfV2xnpRcBpPAYf94EAu53xIJnd
         VSkg==
MIME-Version: 1.0
X-Received: by 10.180.72.15 with SMTP id z15mr9212610wiu.46.1401351321498;
 Thu, 29 May 2014 01:15:21 -0700 (PDT)
Received: by 10.217.94.201 with HTTP; Thu, 29 May 2014 01:15:21 -0700 (PDT)
Date: Thu, 29 May 2014 13:45:21 +0530
Message-ID: 
 <CAOpPrj9PwYJwctLbzgVOtJZK4ub+uCVRMo4KECiVMnC-3WM9cw@mail.gmail.com>
Subject: Workflow handling in the Application Catalog
From: Sachith Withana <swsachith@gmail.com>
To: dev@airavata.apache.org
Content-Type: multipart/alternative; boundary=001a11c2ab64b93a3404fa8587ba
X-Virus-Checked: Checked by ClamAV on apache.org

--001a11c2ab64b93a3404fa8587ba
Content-Type: text/plain; charset=UTF-8

Hi all,

When designing the Application Catalog for single Applications, I ran into
the issue of supporting workflows in the Application Catalog.

Should we store the workflows ( workflow files) and keep ids, which would
be the handles for those workflows?

We would have to keep track of the applications that are in that workflow
so that the deployment related data would be reused.

Similarly to the single Applications, the sharing and other features would
be available for the workflows as well.

Is there any more details that I should be concerned about when
implementing the aforementioned approach?

If we are planning to add searching capability with the workflows as well,
then we'd have to store the applications that are used in the workflows,
separately in the database as well instead of storing it as a whole.

Any suggestions/comments on the matter is highly appreciated.

-- 
Thanks,
Sachith Withana

--001a11c2ab64b93a3404fa8587ba
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi all,<div><br></div><div>When designing the Application =
Catalog for single Applications, I ran into the issue of supporting workflo=
ws in the Application Catalog.</div><div><br></div><div><div>Should we stor=
e the workflows ( workflow files) and keep ids, which would be the handles =
for those workflows?</div>
<div><br></div><div>We would have to keep track of the applications that ar=
e in that workflow so that the deployment related data would be reused.=C2=
=A0</div><div><br></div><div>Similarly to the single Applications, the shar=
ing and other features would be available for the workflows as well.=C2=A0<=
/div>
<div><br></div><div>Is there any more details that I should be concerned ab=
out when implementing the aforementioned approach?</div><div><br></div><div=
>If we are planning to add searching capability with the workflows as well,=
 then we&#39;d have to store the applications that are used in the workflow=
s, separately in the database as well instead of storing it as a whole.</di=
v>
<div><br></div><div>Any suggestions/comments on the matter is highly apprec=
iated.=C2=A0</div><div><br></div>-- <br><div dir=3D"ltr"><div><font style=
=3D"font-family:garamond,serif;color:rgb(0,0,0);background-color:rgb(255,25=
5,255)">Thanks,</font></div>
<font style=3D"font-family:garamond,serif;color:rgb(0,0,0);background-color=
:rgb(255,255,255)"></font><font style=3D"font-family:garamond,serif;backgro=
und-color:rgb(255,255,255);color:rgb(0,0,0)"></font><div style=3D"backgroun=
d-color:rgb(255,255,255)">
<font face=3D"garamond, serif">Sachith Withana<br></font><br></div></div>
</div></div>

--001a11c2ab64b93a3404fa8587ba--