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 227DC110C4 for ; Sat, 31 May 2014 14:42:02 +0000 (UTC) Received: (qmail 674 invoked by uid 500); 31 May 2014 14:42:02 -0000 Delivered-To: apmail-airavata-dev-archive@airavata.apache.org Received: (qmail 625 invoked by uid 500); 31 May 2014 14:42:02 -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 611 invoked by uid 99); 31 May 2014 14:42:02 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 31 May 2014 14:42:02 +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 kamalasini@gmail.com designates 209.85.215.51 as permitted sender) Received: from [209.85.215.51] (HELO mail-la0-f51.google.com) (209.85.215.51) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 31 May 2014 14:41:57 +0000 Received: by mail-la0-f51.google.com with SMTP id gf5so1617993lab.24 for ; Sat, 31 May 2014 07:41:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=dL0jXXAlvthQJwPk4xo2du7Yca838zBKfN0sQ6JU7Wg=; b=o99TEnw4j0P6udRhjHPJ1PpXJHUV+L7vnGgCdwjpfC+z7Vjn9QRHdiHcB8dMSYx0W3 QUoYWRXPg1s4Qt7T7Nj+fDZcZ5ox45nnKtGK+oE3NyOnBdbpIUpKFfRkYFOe3TJmnX0C N3bPfPSFqQri9M0BFkwfjnN3e1whIKjVkK17/UAjQ4Z3cVZVV1ytHOB7kAa7aHpE4fjP We2wQuzN+BFROEKJdn8jQZEuXZBJZEnDfgcVYqPAMfgMvObkJsF2H5xh3YfrkfQM3BOu 1e4fvUghxqXh3OBExsd3JWggqZZ4iz1FESShJYctv1Exyc8c3cm6D1DNruO1pteXd61P m7rA== X-Received: by 10.112.34.210 with SMTP id b18mr17741014lbj.42.1401547296011; Sat, 31 May 2014 07:41:36 -0700 (PDT) MIME-Version: 1.0 Received: by 10.112.189.2 with HTTP; Sat, 31 May 2014 07:41:15 -0700 (PDT) In-Reply-To: References: From: Chathuri Wimalasena Date: Sat, 31 May 2014 10:41:15 -0400 Message-ID: Subject: Re: Application Catalog ER Diagram To: dev@airavata.apache.org Content-Type: multipart/alternative; boundary=14dae93d9380b6fcab04fab32806 X-Virus-Checked: Checked by ClamAV on apache.org --14dae93d9380b6fcab04fab32806 Content-Type: text/plain; charset=UTF-8 Hi Sachith, I already added the database scripts for mysql and derby and the JPA models according to application catalog data models. Did you have a look at them as well ? [1] https://github.com/apache/airavata/blob/master/modules/app-catalog/app-catalog-data/src/main/resources/appcatalog-derby.sql On Sat, May 31, 2014 at 9:56 AM, Sachith Withana wrote: > Hi all, > > I've attached an ER diagram I drafted on how the Application Catalog > should look like in my opinion. > > Please provide any comments or suggestions so that I can move on to > implementing it. > > Chathuri has already added the Job Management and Data Movement objects so > I excluded that in the design diagram. > > NOTE: This design assumes that we would be able to have the node details > as applications in a workflow so that the deployments would be handled per > application according to the deployment details we have in the > applications. > > -- > Thanks, > Sachith Withana > > --14dae93d9380b6fcab04fab32806 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Sachith,=C2=A0

I already added the d= atabase scripts for mysql and derby and the JPA models according to applica= tion catalog data models. Did you have a look at them as well ?
<= br>



On Sat, May 31, 2014 at 9:56 AM, Sachith Withana = <swsachith@gmai= l.com> wrote:
Hi all,

= I've attached an ER diagram I drafted on how the Application Catalog sh= ould look like in my opinion.

Please provide any comments or suggestions so that I ca= n move on to implementing it.

Chathuri has already added the Job Management and Data = Movement objects so I excluded that in the design diagram.=C2=A0
=
NOTE: This design assumes that we would be able to have the = node details as applications in a workflow so that the deployments would be= handled per application according to the deployment details we have in the= applications.=C2=A0

--
Thanks,
Sachith Withana


--14dae93d9380b6fcab04fab32806--