You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airavata.apache.org by sm...@apache.org on 2012/05/15 04:44:43 UTC
svn commit: r1338515 - in /incubator/airavata/trunk: INSTALL README
RELEASE_NOTES
Author: smarru
Date: Tue May 15 02:44:42 2012
New Revision: 1338515
URL: http://svn.apache.org/viewvc?rev=1338515&view=rev
Log:
Updating meta files with 0.3 release info
Modified:
incubator/airavata/trunk/INSTALL
incubator/airavata/trunk/README
incubator/airavata/trunk/RELEASE_NOTES
Modified: incubator/airavata/trunk/INSTALL
URL: http://svn.apache.org/viewvc/incubator/airavata/trunk/INSTALL?rev=1338515&r1=1338514&r2=1338515&view=diff
==============================================================================
--- incubator/airavata/trunk/INSTALL (original)
+++ incubator/airavata/trunk/INSTALL Tue May 15 02:44:42 2012
@@ -23,157 +23,3 @@ The airavata website has instructions fo
* For basic understanding of how Airavata works - http://incubator.apache.org/airavata/documentation/system/airavata-in-5-minutes.html
* Advanced understanding of Airavata - http://incubator.apache.org/airavata/documentation/system/airavata-in-10-minutes.html
* Advanced tutorial to provide understanding of how to run sample workflows distributed with Airavata - http://incubator.apache.org/airavata/documentation/system/advanced-workflow-samples.html
-
-Frequently Asked Questions
---------------------------
-Common questions and how-to's are listed at - http://incubator.apache.org/airavata/documentation/howto/howto.html
-
-Advanced Configuration (Only needed if default configurations need to be changed)
-=======================
-
-Configuring GFac Service
-------------------------
-Given below are the configurations for GFac service to be loaded during axis2 startup. Default configuration file can be
-found at <extracted location>/standalone-server/conf/repository.properties.
-
-Configuration Description
-============================= ====================================
-
-jcr.class Your JCR Implementation factory class. Currently we support only Jackrabbit in future we
-(org.apache.jackrabbit.rmi. hope to support other JCR implementations too.(So with this release you do not have to change this parameter).
-repository.RmiRepositoryFactory)
-
-repository.url This is the url of your repository.. Currently this should be the url of your Jackrabbit repository.
-(http://localhost:8081)
-
-
-jcr.user This is the jackrabbit admin user name - If you have change the jackrabbit user name in your jackrabbit instance
-(admin) you have to change this parameter.
-
-jcr.pass This is the jackrabbit admin password - If you have change the jackrabbit default password in your jackrabbit instance
-(admin) you have to change this parameter.
-
-
-scheduler.class Schedular class you want to use.. if you have your own class put that jar in to <extracted location>/standalone-server/lib folder and change this parameter.
-(org.apache.airavata.core.
-gfac.scheduler.impl.SchedulerImpl)
-
-
-datachain.classes Data Service plugin classes.. if you have your own class put that jar in to <extracted location>/standalone-server/lib folder and change this parameter.
-(org.apache.airavata.core.
-gfac.extension.data.RegistryDataService)
-
-prechain.classes Pre execution Plugins classes. For example, GridFTP Input Staging. You have to specify all the classes one by one for the same parameter.
-
-postchain.classes Post execution Plugins classes. For example, GridFTP Output Staging, if you have your own class put that jar in to <extracted location>/standalone-server/lib folder and change this parameter
-
-
-
-Configure WS-Messenger messageBroker service.
-----------------------------------------------
-Given below are the configurations for message broker service. configuration file should be named as
-"msgBroker.properties". This should be included in the class path (e.g. <extracted location>/standalone-server/conf) when broker starts.
-
-Configuration Description
-============================= ====================================
-broker.jdbc.driver Database driver.
-broker.jdbc.url Url string used to connect the database
-broker.start.delivery.thread If set to true message delivery thread will be started.
-(true/false) Applicable when only running broker. User must set this to 'false'
- if he wishes run message deliver component separately ( e.g. messenger servlet).
-broker.socket.timeout Connection timeout in milliseconds.Set this to '0' if user wishes connections never to be timed out.
- (not recommended)4000
-broker.storage.type Specifies message, subscriptions should be stored in a database or not. memory or persistent
-(memory/persistent)
-broker.delivery.method Specifies what mechanism to be used deliver messages.
-(serial,parallel,pcrew) serial: single threaded delivery
- parallel: dynamic thread pool based delivery
- pcrew: fixed thread pool based delivery
- serial , parallel or pcrew
-broker.msg.delivery.retries Number of message delivery failures before a url become black listed (default is 2) 2
-consumer.expiration.time.gap Time period (in seconds) a url will be kept blacklisted (default is 5 seconds) 5
-sending.batch.size Maximum number of messages to be send to a one consumer/url at time. applicable if 'broker.delivery.method' is 'pcrew'(default is 10)10
-sending.thread.pool.size Size of the thread pool. only applicable if 'broker.delivery.method' is 'pcrew'. (default is 4) 4
-
-
-Configure WS-Messenger messagebox service
------------------------------------------
-Configuration Description
-msgBox.jdbc.driver Database driver.
-msgBox.jdbc.url Url string used to connect the data base
-msgBox.usedatabase If set to 'true' use MySql database. If set to 'false' use inmemory implementation.
-(true,false) In this scenario database settings i.e-broker.jdbc.url is not required.
-
-Run Ws-messenger
------------------
-1. User has the option to run broker in several modes. Steps for each mode is given below.
-
-Run standalone version supplied with binary distribution
----------------------------------------------------------
-
-1. Unzip binary distribution.
-
-2. Change default configurations if needed.
-
-- configuration files is located at:
- <extracted location>/standalone-server/conf/msgBroker.properties
- <extracted location>/standalone-server/conf/msgBox.properties
-
- Run axis2 server by running the command:
- Linux -
- <extracted location>/standalone-server/bin/axis2server.sh
- Windows -
- <extracted location>/standalone-server/bin/axis2server.bat
-
-Run Ws-messenger using axis2 servlet
--------------------------------------
-(Tested on tomcat v 6.0.20 & axis2 v1.5.1)
-1. Copy broker aar file to axis2 distribution accordingly.
-2. Create database tables (Scripts can be found <extracted location>/bin/database_scripts)
-3. Set configurations appropriately and copy configuration file ( named msgBroker.properties) to
-
- <Axis-servlet>/webapps/axis2/WEB-INF/classes
-
-Note: a sample configuration file is located at:
-
-<extracted location>/standalone-server/conf/msgBroker.properties
-<extracted location>/standalone-server/conf/msgBox.properties
-
-4. Start tomcat server.
-
-5. For more information follow how to deploy Apache Axis2 as a Web Application.
-
-
-Run Ws-messenger using a external axis2 distribution
-----------------------------------------------------
-
-1. Copy broker aar file to following location:
- <AXIS2_DIST_HOME>/repository/services
-
-2. Copy msgBroker.properties and msgBroker.properties file to <AXIS2_DIST_HOME>/conf
-
- Configure msgBroker.properties with broker.start.delivery=false
-
-3. Start axis2 server.
-
-4. Run message delivery component separately.
-
-5. Deploy messenger servlet on tomcat.
-
-Note: messenger servlet can be found at <extracted_location>/messenger directory.
-
-6. Set configurations appropriately.
-
- <TOMECAT_HOME>/webapps/messenger/WEB-INF/classes/msgBroker.properties
- <TOMECAT_HOME>/webapps/messenger/WEB-INF/classes/msgBox.properties
-
-Note: Point to the correct database you want to pick the messages and do the message delivery, and check the
-property axis2.repository to the correct location.
-
-7. Start tomcat.
-
-
-Run Samples
------------
-To Run samples go to <extracted location>/samples and refer the sample level README files.
-
Modified: incubator/airavata/trunk/README
URL: http://svn.apache.org/viewvc/incubator/airavata/trunk/README?rev=1338515&r1=1338514&r2=1338515&view=diff
==============================================================================
--- incubator/airavata/trunk/README (original)
+++ incubator/airavata/trunk/README Tue May 15 02:44:42 2012
@@ -25,7 +25,8 @@ does indicate that the project has yet t
Release Notes
=============
-0.2-INCUBATNG is the first release of Airavata, 0.1-INCUBATNG was attempted but the vote was cancelled. This notes covers both the releases. This release focuses on improving test cases and stability of code, cleaning up of donated code, packaging all components into modular architecture, documentation, and removal of non-compatible license dependencies. For detailed tasks list, please see RELEASE_NOTES.
+0.3-INCUBATNG is the second release of Airavata (skipped 0.1-INCUBATNG). This release focuses on improving test cases
+and stability of code, documentation. For detailed tasks list, please see RELEASE_NOTES.
Building from source
====================
@@ -39,7 +40,6 @@ Known Issues in This Release
This is the base release and is focused on a good foundation and less on features. This
version is not recommended for production usage.
-
Airavata Binary Distribution Directory Structure
================================================
Modified: incubator/airavata/trunk/RELEASE_NOTES
URL: http://svn.apache.org/viewvc/incubator/airavata/trunk/RELEASE_NOTES?rev=1338515&r1=1338514&r2=1338515&view=diff
==============================================================================
--- incubator/airavata/trunk/RELEASE_NOTES (original)
+++ incubator/airavata/trunk/RELEASE_NOTES Tue May 15 02:44:42 2012
@@ -2,6 +2,58 @@ Apache Airavata Change Log
See http://issues.apache.org/jira/browse/AIRAVATA-* (where * is the number of the issue below)
+Apache Airavata Version 0.3-INCUBATING Released on 2012-05-14
+=============================================================
+
+** New Feature
+ * [AIRAVATA-100] - Workflow Execution Context Header schema
+ * [AIRAVATA-305] - Allow users to configure provenacne Writer Thread pool size and shutdown the thread pool during service shutdown
+ * [AIRAVATA-348] - Need Maven profiles for building Airavata clients.
+
+** Task
+ * [AIRAVATA-106] - Adding a Sample which demonstares the usage of XMLBean generated POJO classes
+ * [AIRAVATA-301] - create documentation for how to use XBayaClient with a sample code
+ * [AIRAVATA-302] - Document the xbaya.properties file entries used in WorkflowInterpreter service in detail
+ * [AIRAVATA-303] - Document how to invoke echo service in one of the super computers (ranger)
+
+** Sub-task
+ * [AIRAVATA-291] - Test Foreach when workflow interpreter is running without the ws-messenger
+ * [AIRAVATA-292] - Long running stress evaluation of workflow interpreter without the ws-messenger
+ * [AIRAVATA-407] - name all module jars with airavata prefix
+
+** Improvement
+ * [AIRAVATA-253] - Remove weps.jar
+ * [AIRAVATA-263] - Improve WorkflowInterpreter to run multiple jobs in parallel
+ * [AIRAVATA-267] - minimize the default size of XBaya Window
+ * [AIRAVATA-273] - Providing multiple port suppor for EndForEach Node
+ * [AIRAVATA-274] - Threads get created during a long run of Interpreter service
+ * [AIRAVATA-279] - xml serialization error in 10 minute tutorial
+ * [AIRAVATA-285] - Remove messenger to attic
+ * [AIRAVATA-293] - Allow users to configure the time interval to delete old messageboxes
+ * [AIRAVATA-294] - Create new api method to initialize the XBaya client without the notificaton listner
+ * [AIRAVATA-319] - Move the XBayaClient to a separate module
+ * [AIRAVATA-398] - remove src and target folders from binary distribution of samples
+
+** Bug
+ * [AIRAVATA-266] - Fix intermittent test failures in XBaya test cases
+ * [AIRAVATA-269] - Hyphen replacement is not working properly
+ * [AIRAVATA-272] - XBaya UI Application Description saving - executable selection doens't work properly
+ * [AIRAVATA-275] - PUBLISHER threads are not interrupted after the workflow inovacation
+ * [AIRAVATA-276] - Unnecessary QueueName element in ApplicationDescription dialog
+ * [AIRAVATA-283] - Old messagebox deletion doesn't work
+ * [AIRAVATA-286] - Registry API random test failures
+ * [AIRAVATA-295] - In a long run messagePuller threads are not killing completely
+ * [AIRAVATA-297] - New Deployment Description panel "save" button
+ * [AIRAVATA-310] - Not able to edit existing service description
+ * [AIRAVATA-311] - New Deployment Description panel layout issue
+ * [AIRAVATA-312] - Host Description Advanced Options panel layout issue
+ * [AIRAVATA-378] - Update Gram Configuration Dialog to accept Static Working Directory option
+ * [AIRAVATA-389] - jobs fails with lack of memory in batch submission
+ * [AIRAVATA-399] - Improve GramProvider to support transfer of local files
+
+** Test
+ * [AIRAVATA-239] - Create a Edit distance based dot product and cartisian product ForEach test case
+
Airavata Version 0.2-INCUBATING Released on 2012-04-22
======================================================