Hi Suresh, Please find the current status according to the below tutorial task list.
>> 5 minute Airavata Tutorial: >> 1) Create/Login to Jack-Rabbit account from XBaya - Still we cannot create >> logins due to issue in Jackrabbit Currently we are using default admin/admin >> login to run the samples and do tests. >> 2) Construct a sample workflow with included sample math axis2 services. >> (YES) >> 3) Store and retrieve the workflow from registry (YES, just finished with >> registry workflow deleting). >> 4) Execute the workflow with monitoring through events (YES) >> 5) View workflow execution summary and inputs and outputs from registry >> browser. Can store the inputs/outputs in to registry Viewing part is not yet >> done. >> > > +1 > > For 5 minute thing, how about providing a script which starts Axis2 > Instance, Jackrabbit together, currently we have two separate scripts for > that ? > >> >> 15 minute Airavata Tutorial: >> 1) Create/Login to Jack-Rabbit account from XBaya - (Same as 5 min Step 1) >> 2) Identify sample command line applications and provide descriptions to >> register applications to registry. (This is having few issues before we can >> fully utilize the feature). >> 3) Construct workflow with the registered and generated application >> services. (YES) >> 4) Execute workflow invoking the newly created axis2 application services. >> (YES) >> 5) View workflow execution summary and inputs and outputs from registry >> browser.(Same as 5 Min Step 5) >> > We have following tasks left before the feature freeze. 1. Fixing Account creation issue in Jackrabbit - Lahiru. 2. Implement Viewing workflow inputs and outputs in XBaya - I think Patnacha is working on this. 3. Fixing the issues in saving/retrieving Application Description/Service Description document - Saminda is working on it and he is providing patches for this.. 4. Finishing Registry browser - This is not a task required to finish the tutorials. After fixing these issue we can start writing two tutorials and start working release process. Please suggest if there are more to be done for the tutorial. Regards Lahiru Please note that I am listing the simple steps to start with. Once agreeable >> to every one, we should all document detailed developer information, like >> how the execution from xbaya is going to go to workflow intepreter and then >> gfac and so on. >> >> Once we agree upon the features, we should also iterate on the timelines >> for release and rough estimates for future releases. >> > > I hope to start working in documentation in google docs(I will send a mail > once I start with links) so that everyone can see and do modifications. > > Thanks > Lahiru > >> >> Cheers, >> Suresh >> >> >> >> On May 13, 2011, at 8:37 AM, Suresh Marru wrote: >> >> > Hi All, >> > >> > All of us clearly know what Airavata software is about in varying >> details, but at the same time I realize not every one of us on the list >> have a full understanding of the architecture as a whole and sub-components. >> Along with inheriting the code donation, I suggest we focus on bringing >> every one to speed by means of high level and low level architecture >> diagrams. I will start a detailed email thread about this task. In short, >> currently the software assumes understanding of e-Science in general and >> some details of Grid Computing. Our first focus should be to bring the >> software to a level any java developer can understand and contribute. Next >> the focus can be to make it easy for novice users. >> > >> > I thought a good place to start might be to list out the high level >> goals and then focus on the first goal with detailed JIRA tasks. I am >> assuming you will steer us with a orthogonal roadmap to graduation. I hope I >> am not implying we need to meet the following goals to graduate, because >> some of them are very open ended. Also, please note that Airavata may have >> some of these features already, I am mainly categorizing so we will have a >> focused effort in testing, re-writing or new implementations. >> > >> > Airavata high level feature list: >> > >> > Phase 1: Construct, Execute and monitor workflows from pre-deployed web >> services. The workflow enactment engine will be the inherent Airavata >> Workflow Interpreter. Register command line applications as web services, >> construct and execute workflows with these application services. The >> applications may run locally, on Grid enabled resources or by ssh'ing to a >> remote resource. The client to test this phase workflows can be Airavata >> Workflow Client (XBaya) running as a desktop application. >> > >> > Phase 2: Execute all of phase 1 workflows on Apache ODE engine by >> generating and deploying BPEL. Develop and deploy gadget interfaces to >> Apache Rave container to support application registration, workflow >> submission and monitoring components. Support applications running on >> virtual machine images to be deployed to Amazon EC2, EUCALYPTUS and similar >> infrastructure-as-a-service cloud deployments. >> > >> > Phase 3: Expand the compute resources to Elastic Map Reduce and Hadoop >> based executions. Focus on the data and metadata catalog integration like >> Apache OODT. >> > >> > I will stop here, to allow us to discuss the same. Once we narrow down >> on the high level phase 1 goals, I will start a detailed discussion on where >> the code is now and the steps to get to goal1. >> > >> > Comments, Barbs? >> > >> > Suresh >> >> > > > -- > System Analyst Programmer > PTI Lab > Indiana University > > -- System Analyst Programmer PTI Lab Indiana University
