Hi All, Thanks for all the hard work and contributions from both the devs and greatly appreciate all the volunteer contributions. I think we are finally at a stage where we can make a release. Can we all run a last sprint to finish the release logistics? I volunteer to be the release manager for first two releases and will document all the steps as I learn. Please step in (at a later time) if you like to volunteer for subsequent releases.
Please note that I am doing this first time and highly likely I will not be able get it right first time, but we are in the safe hands of vastly experienced mentors and rest assured I will also be on top of this release and will learn along the way. Here are the high priority steps, please volunteer to nail them down: * Cleanup JIRA Fix Version 0.1 Incubating - http://s.apache.org/rj I see that most of the issues are already addressed but I did not verify each of these issues. So can you all please go through this list and resolve the ones which are resolved and change Fix Version to 0.2 version if it is not addressed. If you realize that an issue is not resolved but is a show stopper for this release, please start a email discussion (one per issue). * Verify issues which are resolved (but not yet closed) and either re-open the ticker if not resolved, if correctly fixed, then please close them. * Update website with roadmap and release landing pages. Thanks, Suresh On Oct 16, 2011, at 12:45 AM, Suresh Marru wrote: > Thanks to Lahiru for the initiative on the release, we took some time, but > the code looks nice and clean and improved. Now that we have the foundation, > we can probably get to quick releases. It will be nice if we plan for the > first 5 releases. How about starting this month, we go on a monthly schedule, > with off number of releases focusing on the feature enhancements and the even > number focusing on the bug fixes and improving tests and documentation of its > predecessor release? > > 0.1-INCUBATING - October 30th - Code imported from donations is cleaned up, > added simple build and tests, easy documentation. > 0.2-INCUBATING - November 30th - Bug fix release of 0.1, minimal feature > addition, more focus on improving tests, documentation and profiling. > 0.3-INCUBATING - December 30th - Improvements to registry usage, learn from > JCR/Jackrabbit experience and stratergize a long term registry roadmap. - > Engage target users and broaden the community with this release. > 0.4-INCUBATING - January 30th - Bug fix, tests and documentation > improvements. Apply feedback with integration to end users. > 0.5-INCUBATING - February - A release with production readiness and based on > community engagement and expansion, ready to march into the finish line for > graduation. > > I personally feel that we will be at alpha quality for first release, a > pre-beta for second. By third we need to get to beta quality and announce for > readiness to be integrated into initial set of end user communities. WIth the > friendly user feedback and integration experiences 4th release can be a > pre-stable release. 5th release has to be a major one, and we should be able > to ensure confidence to the community to integrate into production > environments. > > If we succeed in this plan, we should be able to start making a case for > graduation, with an assumption that we will engage and grow both developer > and user communities. > > Thoughts? > > Suresh > > On Sep 29, 2011, at 11:54 AM, Suresh Marru wrote: > >> Hi All, >> >> We should get a consensus on the release features and document the road map >> on the website and march towards a release. I will start the draft, please >> look through and comment: >> >> I will define the feature list of Release 0.1-Incubating by means of a >> tutorial we should document on the website. >> >> Airavata Modules for the release: >> GFac-Axis2: An axis2 web service which can consume user defined command line >> descriptions and generate axis2 application web services. >> XBaya - A desktop (and webstart by JNLP) application which lets users to >> construct, execute and monitor workflow executions. >> XBaya is also used in this release as a user management, application >> management and data browser. In the future these UI's will be web gadgets to >> be deployed into containers like Apache Rave. >> Workflow Interpreter: Axis2 wrapper around XBaya dynamic executor. This is a >> simple and interactive workflow execution engine. Future releases will >> support Apache ODE in addition to interpreter service. >> WS-Messenger: WS-Eventing/WS-Notification based messaging system. >> Registry-API: A thick client registry API for Airavata to put and get >> documents. Current JCR implementation is supported by Jack-Rabbit. >> >> Build & Deploy: >> We should have a one single maven build which builds and deploys all >> services to a axis2 tomcat container. We should have shell scripts to launch >> xbaya. >> >> All tutorials have the pre requite of build and deploy steps. >> >> 5 minute Airavata Tutorial: >> 1) Create/Login to Jack-Rabbit account from XBaya >> 2) Construct a sample workflow with included sample math axis2 services. >> 3) Store and retrieve the workflow from registry >> 4) Execute the workflow with monitoring through events >> 5) View workflow execution summary and inputs and outputs from registry >> browser. >> >> 15 minute Airavata Tutorial: >> 1) Create/Login to Jack-Rabbit account from XBaya >> 2) Identify sample command line applications and provide descriptions to >> register applications to registry. >> 3) Construct workflow with the registered and generated application services. >> 4) Execute workflow invoking the newly created axis2 application services. >> 5) View workflow execution summary and inputs and outputs from registry >> browser. >> >> 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. >> >> 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 >> >
