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 4C79E10067 for ; Fri, 10 Jan 2014 03:40:02 +0000 (UTC) Received: (qmail 11842 invoked by uid 500); 10 Jan 2014 03:39:57 -0000 Delivered-To: apmail-airavata-dev-archive@airavata.apache.org Received: (qmail 11756 invoked by uid 500); 10 Jan 2014 03:39:55 -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 11748 invoked by uid 99); 10 Jan 2014 03:39:54 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Jan 2014 03:39:54 +0000 X-ASF-Spam-Status: No, hits=2.5 required=5.0 tests=FREEMAIL_REPLY,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of danushka.menikkumbura@gmail.com designates 209.85.128.181 as permitted sender) Received: from [209.85.128.181] (HELO mail-ve0-f181.google.com) (209.85.128.181) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Jan 2014 03:39:47 +0000 Received: by mail-ve0-f181.google.com with SMTP id oy12so3118815veb.12 for ; Thu, 09 Jan 2014 19:39:26 -0800 (PST) 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=ZO4KJnE42jcFjm70dX/zVrBJ9/40hyjJkiXOH+l84/E=; b=S/N0KDV0QP/jAO5F5OBlzydWmsjQzwavEgUustK3AY1GHjoMmiLEiMEhb1Yf0VCJ7+ hEMBrsOPEW3Cfa5T80pWOk6GQbb63YPePE3Dn4buTIrokzd63wY34O4jqNo85SVyYvuf jEnIraejAzanjDRsgCeHVPLKYw+zTcMZxpMNl/VWp/o8VMy6NOb7Fa1hhigdfjb3J50Z EqQbokDfqq3ZKxJdQ3O++VVB4JgJWzqihirsn7DzVzXpU9drmcfncW8UtZcjxd+uS4WT 80Hgo0Qgn4CnyRuk8XON0F0vPFtxpT7j/e78mV+7EwCQsBe4oR1C8iYs2mow7uDnpBVY Veeg== X-Received: by 10.52.23.13 with SMTP id i13mr4998108vdf.0.1389325165978; Thu, 09 Jan 2014 19:39:25 -0800 (PST) MIME-Version: 1.0 Received: by 10.59.5.231 with HTTP; Thu, 9 Jan 2014 19:39:05 -0800 (PST) In-Reply-To: <3580177E-E641-4CE1-A781-EDD06094172F@apache.org> References: <52CC8398.7060706@iu.edu> <3580177E-E641-4CE1-A781-EDD06094172F@apache.org> From: Danushka Menikkumbura Date: Fri, 10 Jan 2014 09:09:05 +0530 Message-ID: Subject: Re: Gateway Developer Tutorial To: dev Content-Type: multipart/alternative; boundary=20cf307ca4f8fee9b704ef957859 X-Virus-Checked: Checked by ClamAV on apache.org --20cf307ca4f8fee9b704ef957859 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable That is quite impressive!. Lets have something similar please?. A one stop shop for most of the things that someone would want to know/learn. Lets come up with a list of things that we may want to have. I think we already have a nice introductory hangout session done for the last GSoC team. I suggest we start with that. Cheers, Danushka On Fri, Jan 10, 2014 at 12:57 AM, Suresh Marru wrote: > Good idea. We can do the free google hangout on air and preserve the > archive url=92s. Stratos has been successfully doing these [1] > > Suresh > [1] - http://stratos.incubator.apache.org/events/hangouts.html > On Jan 9, 2014, at 12:13 PM, Danushka Menikkumbura < > danushka.menikkumbura@gmail.com> wrote: > > > Correction. > > > > s/Webinar/Webcast/g > > > > Regards, > > Danushka > > > > > > On Thu, Jan 9, 2014 at 8:23 AM, Danushka Menikkumbura < > danushka.menikkumbura@gmail.com> wrote: > > Along similar lines, we should also think of having Webinars, hosted > slide decks, etc to help kick-start. It is good to have a set of Webinars > for a selected set of scenarios, starting from basics to a few advanced > ones IMO. > > > > Thanks, > > Danushka > > > > > > On Wed, Jan 8, 2014 at 4:15 AM, Marlon Pierce wrote: > > Definitely it should be localhost for the beginner. > > > > > > Marlon > > > > On 1/7/14 5:43 PM, Saminda Wijeratne wrote: > > > I'd say lets restrict ourselves to localhost for the demonstration > > > purposes. GRAM is just a configuration detail which the gateway admin= s > have > > > to deal with (not the gateway developers). > > > > > > > > > On Tue, Jan 7, 2014 at 3:48 PM, Sachith Withana > wrote: > > > > > >> The Sample Gateway example uses Gram. Should the guide be on using > Gram or > > >> localhost? > > >> > > >> Using Gram --> provides the details on how to configure the GRAM > > >> credentials in the server and the configuring the hosts ( descriptor= s) > > >> > > >> Using localhost --> it would be easier for the developer to test. > After > > >> getting the program to work in localhost, only minor changes are > required > > >> to get it running on Gram( or similar) > > >> > > >> > > >> On Tue, Jan 7, 2014 at 11:05 AM, Sachith Withana >wrote: > > >> > > >>> Thanks Amila. > > >>> > > >>> I will keep you all update on the progress. > > >>> > > >>> > > >>> On Mon, Jan 6, 2014 at 10:33 PM, Amila Jayasekara < > > >>> thejaka.amila@gmail.com> wrote: > > >>> > > >>>> Hi Sachith, > > >>>> > > >>>> Some answers inline. > > >>>> > > >>>> On Mon, Jan 6, 2014 at 1:27 PM, Sachith Withana < > swsachith@gmail.com>wrote: > > >>>> > > >>>>> Thank you all. > > >>>>> > > >>>>> So just to be clear, it would be better if we have the Simple > Gateway > > >>>>> Developer Guide using the sample gateway code? > > >>>>> > > >>>> I am +1 for this. But sample gateway uses credential store tokens. > > >>>> Therefore you need to slightly change sample gateway to invoke > workflow > > >>>> without credential store tokens. There are test cases in sample > gateway > > >>>> that does that and you should be able to easily implement this > > >>>> functionality. > > >>>> > > >>>> Objective of the gateway developer is to create a portal using > Airavata > > >>>> API to execute workflows in GRID and retrieve results. > > >>>> > > >>>> So in summary I would expect following points in the article. > > >>>> > > >>>> 1. The big picture. Basically the components that gateway develope= r > > >>>> going to interact and where they fit in the big picture. > > >>>> 2. Software components gateway developer needs to have (airavata > client > > >>>> distribution, airavata server distribution etc ...) > > >>>> 3. Client code explained in steps. (i.e. create connection to serv= er > > >>>> using Airavata Client, the order of creating descriptors, creating > > >>>> workflow, executing workflow, monitoring, retrieving results etc > ...) > > >>>> > > >>>> Thanks > > >>>> Amila > > >>>> > > >>>> > > >>>>> OR > > >>>>> Use two wiki articles , one explaining the big picture( as Amila > > >>>>> mentioned) and the other explaining a ground up simple gateway > guide. > > >>>>> > > >>>>> In the latter case where would the Sample gateway code fit in? > > >>>>> > > >>>>> We could use the 5 minute tutorial to construct a simple workflow > and > > >>>>> then use it with the guide. > > >>>>> > > >>>>> > > >>>>> > > >>>>> On Mon, Jan 6, 2014 at 1:20 PM, Raminder Singh < > > >>>>> raminderjsingh@gmail.com> wrote: > > >>>>> > > >>>>>> +1 for using sample gateway to start with and build over it. Add= ed > > >>>>>> advantage is integration with credential store which is an > important step > > >>>>>> for gateways going forward. > > >>>>>> > > >>>>>> Raminder > > >>>>>> > > >>>>>> On Jan 6, 2014, at 12:57 PM, Amila Jayasekara < > thejaka.amila@gmail.com> > > >>>>>> wrote: > > >>>>>> > > >>>>>> I would also suggest to explain the big picture first. i.e. wher= e > is > > >>>>>> the API client and where is the server, where are the resources > in a > > >>>>>> pictorial view. You may also can use sample gateway as a basis > for your > > >>>>>> guide. So that users has an actual code to look into. > > >>>>>> > > >>>>>> Thanks > > >>>>>> Thejaka Amila > > >>>>>> > > >>>>>> > > >>>>>> On Mon, Jan 6, 2014 at 12:23 PM, Saminda Wijeratne < > samindaw@gmail.com > > >>>>>>> wrote: > > >>>>>>> Sounds good Sachith. Few things to keep in mind. > > >>>>>>> > > >>>>>>> 1. Describe the simple problem which you are simulating a > > >>>>>>> solution for through a simple gateway. (eg: a scientist want= s > to run his > > >>>>>>> application with the input datasets then wait until it > finishes to view the > > >>>>>>> results) > > >>>>>>> 2. Might be a good idea to mention the obvious things for an > > >>>>>>> actual gateway which you are leaving-out of this tutorial fo= r > simplicity. > > >>>>>>> (eg: authentication, session management, file > upload/downloads etc.) > > >>>>>>> 3. You may have to specifically explain in brief things such > as > > >>>>>>> authentication requirements for the Airavata Server (althoug= h > the gateway > > >>>>>>> user doesn't require authentication). > > >>>>>>> 4. Identify the user groups clearly. For example the gateway > user > > >>>>>>> is the person who will be using the web portal. gateway > developer is the > > >>>>>>> person who develops the web portal. a gateway admin is the > person who > > >>>>>>> configures the web portal (in your simple gateway dev > tutorial gateway > > >>>>>>> admin need not be included but I think its useful to mention > who'd be > > >>>>>>> responsible for adding the workflows/descriptors perhaps > through XBaya for > > >>>>>>> this simple gateway) > > >>>>>>> > > >>>>>>> These are just things from top of my head. Feel free to get mor= e > > >>>>>>> clarifications on them... > > >>>>>>> > > >>>>>>> Saminda > > >>>>>>> > > >>>>>>> > > >>>>>>> On Mon, Jan 6, 2014 at 11:29 AM, Sachith Withana < > swsachith@gmail.com > > >>>>>>>> wrote: > > >>>>>>>> Hi Saminda, > > >>>>>>>> > > >>>>>>>> I'm going to organize it base on the three major components I > have > > >>>>>>>> shown in my diagram. > > >>>>>>>> Details wise, I would only include how the API could be used t= o > > >>>>>>>> create the gateway. Anything beyond the API will not be > explained since > > >>>>>>>> this is the simple gateway guide. I would explain those detail= s > in the > > >>>>>>>> elaborated version if required. Since the main expectation of > the gateway > > >>>>>>>> developer is to create a gateway and use Airavata API to use > the resources. > > >>>>>>>> So I thought details on "How to use" the API should be enough? > > >>>>>>>> > > >>>>>>>> Including downloadable samples would be a great idea. I would = do > > >>>>>>>> that. > > >>>>>>>> > > >>>>>>>> Here's the rough sketch. [1] > > >>>>>>>> > > >>>>>>>> [1] > > >>>>>>>> > https://cwiki.apache.org/confluence/display/AIRAVATA/Simple+Gateway+Devel= oper+Guide > > >>>>>>>> > > >>>>>>>> > > >>>>>>>> On Sat, Jan 4, 2014 at 10:26 PM, Saminda Wijeratne < > > >>>>>>>> samindaw@gmail.com> wrote: > > >>>>>>>> > > >>>>>>>>> Sachith, could you explain how are you going to organize simp= le > > >>>>>>>>> gateway guide? How far details are you planning to include in > it? Any > > >>>>>>>>> down-loadable samples would be tempting for a developers to > follow through > > >>>>>>>>> to the next steps. > > >>>>>>>>> > > >>>>>>>>> IMO I think you should start on a rough sketch/draft of the > wiki > > >>>>>>>>> page. Then it'll be easier for anyone to give feedback on it. > > >>>>>>>>> > > >>>>>>>>> Regards, > > >>>>>>>>> Saminda > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> On Sat, Jan 4, 2014 at 12:07 AM, Sachith Withana < > > >>>>>>>>> swsachith@gmail.com> wrote: > > >>>>>>>>> > > >>>>>>>>>> Hi all, > > >>>>>>>>>> > > >>>>>>>>>> Apache Airavata developer guide[1] is obsolete as mentioned = by > > >>>>>>>>>> Saminda in the Jira [2]. > > >>>>>>>>>> > > >>>>>>>>>> We are planning to update the Wiki Gateway developer guide s= o > that > > >>>>>>>>>> a gateway developer is able to create the gateways using the > latest > > >>>>>>>>>> Airavata API. > > >>>>>>>>>> > > >>>>>>>>>> We have divided the developer guide into two components > > >>>>>>>>>> 1. Simple Gateway developer guide > > >>>>>>>>>> 2. Elaborated Gateway developer guide > > >>>>>>>>>> > > >>>>>>>>>> In the simple gateway guide, we will be targeting new gatewa= y > > >>>>>>>>>> developers to use the API to create a simple yet complete > gateway. I have > > >>>>>>>>>> attached the design of a simple gateway and the guide will > help the > > >>>>>>>>>> developer in accomplishing those components with the use of > the Airavata > > >>>>>>>>>> API. > > >>>>>>>>>> This design contains a simple workflow with inputs. > > >>>>>>>>>> > > >>>>>>>>>> In the elaborated Gateway guide, we will take on executing > complex > > >>>>>>>>>> workflows with multiple number of nodes in different hosts > ...etc, getting > > >>>>>>>>>> status of the experiment at multiple levels ( Experiment > level, workflow > > >>>>>>>>>> level( multiple workflows under the same experiment is not > yet supported), > > >>>>>>>>>> Node Level, Application Level ...etc) > > >>>>>>>>>> > > >>>>>>>>>> Any suggestions are welcome. > > >>>>>>>>>> > > >>>>>>>>>> [1] > > >>>>>>>>>> > https://cwiki.apache.org/confluence/display/AIRAVATA/Airavata+Developer+G= uide > > >>>>>>>>>> [2] https://issues.apache.org/jira/browse/AIRAVATA-944-- > > >>>>>>>>>> Thanks, > > >>>>>>>>>> Sachith Withana > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>> > > >>>>>>>> -- > > >>>>>>>> Thanks, > > >>>>>>>> Sachith Withana > > >>>>>>>> > > >>>>>>>> > > >>>>>> > > >>>>> > > >>>>> -- > > >>>>> Thanks, > > >>>>> Sachith Withana > > >>>>> > > >>>>> > > >>> > > >>> -- > > >>> Thanks, > > >>> Sachith Withana > > >>> > > >>> > > >> > > >> -- > > >> Thanks, > > >> Sachith Withana > > >> > > >> > > > > > > > > --20cf307ca4f8fee9b704ef957859 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable
That is quite impressive!.

Lets hav= e something similar please?. A one stop shop for most of the things that so= meone would want to know/learn. Lets come up with a list of things that we = may want to have. I think we already have a nice introductory hangout sessi= on done for the last GSoC team. I suggest we start with that.

Cheers,
Danushka


<= div class=3D"gmail_quote">On Fri, Jan 10, 2014 at 12:57 AM, Suresh Marru <= smarru@apache.org> wrote:
Good idea. We can do the free google hangout= on air and preserve the archive url=92s. Stratos has been successfully doi= ng these =A0[1]

Suresh
[1] - http://stratos.incubator.apache.org/events/hangouts.html<= /a>
On Jan 9, 2014, at 12:13 PM, Danush= ka Menikkumbura <danu= shka.menikkumbura@gmail.com> wrote:

> Correction.
>
> s/Webinar/Webcast/g
>
> Regards,
> Danushka
>
>
> On Thu, Jan 9, 2014 at 8:23 AM, Danushka Menikkumbura <danushka.menikkumbura@gmail.com&= gt; wrote:
> Along similar lines, we should also think of having Webinars, hosted s= lide decks, etc to help kick-start. It is good to have a set of Webinars fo= r a selected set of scenarios, starting from basics to a few advanced ones = IMO.
>
> Thanks,
> Danushka
>
>
> On Wed, Jan 8, 2014 at 4:15 AM, Marlon Pierce <marpierc@iu.edu> wrote:
> Definitely it should be localhost for the beginner.
>
>
> Marlon
>
> On 1/7/14 5:43 PM, Saminda Wijeratne wrote:
> > I'd say lets restrict ourselves to localhost for the demonstr= ation
> > purposes. GRAM is just a configuration detail which the gateway a= dmins have
> > to deal with (not the gateway developers).
> >
> >
> > On Tue, Jan 7, 2014 at 3:48 PM, Sachith Withana <swsachith@gmail.com> wrote:
> >
> >> The Sample Gateway example uses Gram. Should the guide be on = using Gram or
> >> localhost?
> >>
> >> Using Gram --> provides the details on how to configure th= e GRAM
> >> credentials in the server and the configuring the hosts ( des= criptors)
> >>
> >> Using localhost --> it would be easier for the developer t= o test. After
> >> getting the program to work in localhost, only minor changes = are required
> >> to get it running on Gram( or similar)
> >>
> >>
> >> On Tue, Jan 7, 2014 at 11:05 AM, Sachith Withana <swsachith@gmail.com>wrote:
> >>
> >>> Thanks Amila.
> >>>
> >>> I will keep you all update on the progress.
> >>>
> >>>
> >>> On Mon, Jan 6, 2014 at 10:33 PM, Amila Jayasekara < > >>> thejaka.amila@= gmail.com> wrote:
> >>>
> >>>> Hi Sachith,
> >>>>
> >>>> Some answers inline.
> >>>>
> >>>> On Mon, Jan 6, 2014 at 1:27 PM, Sachith Withana <<= a href=3D"mailto:swsachith@gmail.com">swsachith@gmail.com>wrote:
> >>>>
> >>>>> Thank you all.
> >>>>>
> >>>>> So just to be clear, it would be better if we hav= e the Simple Gateway
> >>>>> Developer Guide using the sample gateway code? > >>>>>
> >>>> I am +1 for this. But sample gateway uses credential = store tokens.
> >>>> Therefore you need to slightly change sample gateway = to invoke workflow
> >>>> without credential store tokens. There are test cases= in sample gateway
> >>>> that does that and you should be able to easily imple= ment this
> >>>> functionality.
> >>>>
> >>>> Objective of the gateway developer is to create a por= tal using Airavata
> >>>> API to execute workflows in GRID and retrieve results= .
> >>>>
> >>>> So in summary I would expect following points in the = article.
> >>>>
> >>>> 1. The big picture. Basically the components that gat= eway developer
> >>>> going to interact and where they fit in the big pictu= re.
> >>>> 2. Software components gateway developer needs to hav= e (airavata client
> >>>> distribution, airavata server distribution etc ...) > >>>> 3. Client code explained in steps. (i.e. create conne= ction to server
> >>>> using Airavata Client, the order of creating descript= ors, creating
> >>>> workflow, executing workflow, monitoring, retrieving = results etc ...)
> >>>>
> >>>> Thanks
> >>>> Amila
> >>>>
> >>>>
> >>>>> OR
> >>>>> Use two wiki articles , one explaining the big pi= cture( as Amila
> >>>>> mentioned) and the other explaining a ground up s= imple gateway guide.
> >>>>>
> >>>>> In the latter case where would the Sample gateway= code fit in?
> >>>>>
> >>>>> We could use the 5 minute tutorial to construct a= simple workflow and
> >>>>> then use it with the guide.
> >>>>>
> >>>>>
> >>>>>
> >>>>> On Mon, Jan 6, 2014 at 1:20 PM, Raminder Singh &l= t;
> >>>>> ramin= derjsingh@gmail.com> wrote:
> >>>>>
> >>>>>> +1 for using sample gateway to start with and= build over it. Added
> >>>>>> advantage is integration with credential stor= e which is an important step
> >>>>>> for gateways going forward.
> >>>>>>
> >>>>>> Raminder
> >>>>>>
> >>>>>> On Jan 6, 2014, at 12:57 PM, Amila Jayasekara= <thejaka.amila@gmail.com= >
> >>>>>> wrote:
> >>>>>>
> >>>>>> I would also suggest to explain the big pictu= re first. i.e. where is
> >>>>>> the API client and where is the server, where= are the resources in a
> >>>>>> pictorial view. You may also can use sample g= ateway as a basis for your
> >>>>>> guide. So that users has an actual code to lo= ok into.
> >>>>>>
> >>>>>> Thanks
> >>>>>> Thejaka Amila
> >>>>>>
> >>>>>>
> >>>>>> On Mon, Jan 6, 2014 at 12:23 PM, Saminda Wije= ratne <samindaw@gmail.com
> >>>>>>> wrote:
> >>>>>>> Sounds good Sachith. Few things to keep i= n mind.
> >>>>>>>
> >>>>>>> =A0 =A01. Describe the simple problem whi= ch you are simulating a
> >>>>>>> =A0 =A0solution for through a simple gate= way. (eg: a scientist wants to run his
> >>>>>>> =A0 =A0application with the input dataset= s then wait until it finishes to view the
> >>>>>>> =A0 =A0results)
> >>>>>>> =A0 =A02. Might be a good idea to mention= the obvious things for an
> >>>>>>> =A0 =A0actual gateway which you are leavi= ng-out of this tutorial for simplicity.
> >>>>>>> =A0 =A0(eg: authentication, session manag= ement, file upload/downloads etc.)
> >>>>>>> =A0 =A03. You may have to specifically ex= plain in brief things such as
> >>>>>>> =A0 =A0authentication requirements for th= e Airavata Server (although the gateway
> >>>>>>> =A0 =A0user doesn't require authentic= ation).
> >>>>>>> =A0 =A04. Identify the user groups clearl= y. For example the gateway user
> >>>>>>> =A0 =A0is the person who will be using th= e web portal. gateway developer is the
> >>>>>>> =A0 =A0person who develops the web portal= . a gateway admin is the person who
> >>>>>>> =A0 =A0configures the web portal (in your= simple gateway dev tutorial gateway
> >>>>>>> =A0 =A0admin need not be included but I t= hink its useful to mention who'd be
> >>>>>>> =A0 =A0responsible for adding the workflo= ws/descriptors perhaps through XBaya for
> >>>>>>> =A0 =A0this simple gateway)
> >>>>>>>
> >>>>>>> These are just things from top of my head= . Feel free to get more
> >>>>>>> clarifications on them...
> >>>>>>>
> >>>>>>> Saminda
> >>>>>>>
> >>>>>>>
> >>>>>>> On Mon, Jan 6, 2014 at 11:29 AM, Sachith = Withana <swsachith@gmail.com<= br> > >>>>>>>> wrote:
> >>>>>>>> Hi Saminda,
> >>>>>>>>
> >>>>>>>> I'm going to organize it base on = the three major components I have
> >>>>>>>> shown in my diagram.
> >>>>>>>> Details wise, I would only include ho= w the API could be used to
> >>>>>>>> create the gateway. Anything beyond t= he API will not be explained since
> >>>>>>>> this is the simple gateway guide. I w= ould explain those details in the
> >>>>>>>> elaborated version if required. Since= the main expectation of the gateway
> >>>>>>>> developer is to create a gateway and = use Airavata API to use the resources.
> >>>>>>>> So I thought details on "How to = use" the API should be enough?
> >>>>>>>>
> >>>>>>>> Including downloadable samples would = be a great idea. I would do
> >>>>>>>> that.
> >>>>>>>>
> >>>>>>>> Here's the rough sketch. [1]
> >>>>>>>>
> >>>>>>>> [1]
> >>>>>>>> https://cwiki.apache.org/confluence/display/AIRAVATA/Simple+Gateway+Devel= oper+Guide
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> On Sat, Jan 4, 2014 at 10:26 PM, Sami= nda Wijeratne <
> >>>>>>>> samindaw@gmail.com> wrote:
> >>>>>>>>
> >>>>>>>>> Sachith, could you explain how ar= e you going to organize simple
> >>>>>>>>> gateway guide? How far details ar= e you planning to include in it? Any
> >>>>>>>>> down-loadable samples would be te= mpting for a developers to follow through
> >>>>>>>>> to the next steps.
> >>>>>>>>>
> >>>>>>>>> IMO I think you should start on a= rough sketch/draft of the wiki
> >>>>>>>>> page. Then it'll be easier fo= r anyone to give feedback on it.
> >>>>>>>>>
> >>>>>>>>> Regards,
> >>>>>>>>> Saminda
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> On Sat, Jan 4, 2014 at 12:07 AM, = Sachith Withana <
> >>>>>>>>> swsachith@gmail.com> wrote:
> >>>>>>>>>
> >>>>>>>>>> Hi all,
> >>>>>>>>>>
> >>>>>>>>>> Apache Airavata developer gui= de[1] is obsolete as mentioned by
> >>>>>>>>>> Saminda in the Jira [2].
> >>>>>>>>>>
> >>>>>>>>>> We are planning to update the= Wiki Gateway developer guide so that
> >>>>>>>>>> a gateway developer is able t= o create the gateways using the latest
> >>>>>>>>>> Airavata API.
> >>>>>>>>>>
> >>>>>>>>>> We have divided the developer= guide into two components
> >>>>>>>>>> 1. Simple Gateway developer g= uide
> >>>>>>>>>> 2. Elaborated Gateway develop= er guide
> >>>>>>>>>>
> >>>>>>>>>> In the simple gateway guide, = we will be targeting new gateway
> >>>>>>>>>> developers to use the API to = create a simple yet complete gateway. I have
> >>>>>>>>>> attached the design of a simp= le gateway and the guide will help the
> >>>>>>>>>> developer in accomplishing th= ose components with the use of the Airavata
> >>>>>>>>>> API.
> >>>>>>>>>> This design contains a simple= workflow with inputs.
> >>>>>>>>>>
> >>>>>>>>>> In the elaborated Gateway gui= de, we will take on executing complex
> >>>>>>>>>> workflows with multiple numbe= r of nodes in different hosts ...etc, getting
> >>>>>>>>>> status of the experiment at m= ultiple levels ( Experiment level, workflow
> >>>>>>>>>> level( multiple workflows und= er the same experiment is not yet supported),
> >>>>>>>>>> Node Level, Application Level= ...etc)
> >>>>>>>>>>
> >>>>>>>>>> Any suggestions are welcome.<= br> > >>>>>>>>>>
> >>>>>>>>>> [1]
> >>>>>>>>>> https://cwiki.apache.org/confluence/display/AIRAVATA/Airavata+Developer= +Guide
> >>>>>>>>>> [2] https://issues.ap= ache.org/jira/browse/AIRAVATA-944--
> >>>>>>>>>> Thanks,
> >>>>>>>>>> =A0Sachith Withana
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>
> >>>>>>>> --
> >>>>>>>> Thanks,
> >>>>>>>> Sachith Withana
> >>>>>>>>
> >>>>>>>>
> >>>>>>
> >>>>>
> >>>>> --
> >>>>> Thanks,
> >>>>> =A0Sachith Withana
> >>>>>
> >>>>>
> >>>
> >>> --
> >>> Thanks,
> >>> Sachith Withana
> >>>
> >>>
> >>
> >> --
> >> Thanks,
> >> Sachith Withana
> >>
> >>
>
>
>


--20cf307ca4f8fee9b704ef957859--