Sounds great. May be one idea is to take the thrify route with the following priority:
1. Simple application execution using Orchestrator 2. Query for experiment and job status from registry 3. Fetch input, output provenance data from registry 4. Workflow execution using thrift api 5. Application Catalog (all the service, host and application descriptions) So based on your release list, hopefully we can shoot to have 1, 2 3 done for 0.12 and 4 and 5 for 0.13? Suresh On Jan 21, 2014, at 12:08 PM, Chathuri Wimalasena <[email protected]> wrote: > Hi Suresh, > > I think we can have at least the basic skeletons ready for the release. We > may not be able to have the complete thrift IDLs for registry though. Do you > think it is ok ? > > Regards, > Chathuri > > > On Tue, Jan 21, 2014 at 11:43 AM, Suresh Marru <[email protected]> wrote: > Hi Chathuri, > > For Thrift interfaces, do we want to focus on execution API only or do you > think we can get a version of Registry methods also into this release? > > Suresh > > On Jan 21, 2014, at 10:06 AM, Chathuri Wimalasena <[email protected]> > wrote: > > > Hi All, > > > > Its time to plan features for Airavata 0.12. Lets use this mail thread to > > discuss features that you would like to incorporate into Airavata 0.12. > > > > So please come up with realistic feature list (which we can finish within 6 > > weeks) for 0.12. Tentative target release date is Feb 28th. Here are some > > of the features that we need to incorporate into this release. > > • Finishing up Orchestrator component > > (https://issues.apache.org/jira/browse/AIRAVATA-964) > > • Thrift interfaces for airavata API > > Please add features you would like to add to 0.12. > > > > Thanks and Regards, > > Chathuri > >
