What's new in Apache Airavata 0.14
Jan 9, 2015
- Tasks:
- HostAddress in ComputationalResourceScheduling is required.
- Remove airavata-client-api dependency from other module
- Zookeeper Implementation to Advertise Available/up and running Airavata Services/Components
- Modify Airavata Distribution to Enable Separate Distributions for Orchestrator, Gfac and Xbaya.
- Replace legacy application descriptors used in gfac with app-catalog
- Sub-tasks:
- Support option with parameters for GramProvider
- Craft the Workflow Interpreter CPI
- Updated Xbaya to enable execution of a single application through thrift api
- Submit real time job count details to zookeeper
- Add a inmemory job count map to Orchestrator
- Add throtle-resources flag to airavata API
- Implement RabbitMQ publisher
- Provide a way to enable and disable Job count validation
- Cleanup Airavata property file for old service properties
- Remove connection to Workflow service from Xbaya
- Story:
- Update Airavata JGLOBUS and Unicore jar
- New Feature:
- Add ResourceJobManger add, update, get, delete methods to airavata-api
- Improvement:
- Support For-each for Local providers
- Implement logger in WorkflowInterpreter
- API need enhancement so user can set a user identifier into Context header
- Multiple Security context to run a grid job
- ActualParameter and DataObjectType have same objective
- Can we have a way of searching for all the projects, experiments in the gateway?
- Airavata API function to get Job details
- API function to get data transfer details.
- Input data transfer details are not updated
- Allow multiple client to move the data using same server
- Get partial results incase outputs are not produced.
- RabbitMQ messaging is not supported for SGE resources
- Update log messages to track life cycle of experiments , jobs and tasks.
- XBaya doesn't support multi-app workflows with new Thrift API
- Remove Registry.wsdl stub autogeneration
- Change return type of jobSubmission API methods to string
- Add API methods to get job submission information
- Bug:
- Error message not sent to Xbaya as fault
- Provide GridFTP URL incase of URL and URLArray type
- Unable to set a different gateway name other than "default"
- No free ports available to run GRAM provider and GridFTP transfers
- PersistenceException while executing BES or Gram Provider
- Update Client samples READMEs and INSTALL files
- Command for SLURM job cancel need correction
- Error details are saved twice which adding two records in the database
- Output path is not getting set to output context incase we scan output directory
- App catalog database connection timeout issue
- Orchestrator context does't set initial GFac instant list correctly in one of it's constructor.
- GSISSHAbstractCluster not throwing error if there is issue submitting job
- NullPointerException to create a SSH connection
- Rewrite CreateLaunchExperiment class in order to work with registerApplication method
- Experiment Status is updated to completed on job complete
- Host Aliases and IpAddresses not getting saved in Compute Resource Object
- AdvancedSCPInputHandler is not working if we need to transfer data to BigRed
- Experiment Status is not updated to Complete
- SCP to a newer version of Centos VM does not work
- SSHInputHandler cluster object is null
- Error message when configuring XBaya input parameter configuration
New in Apache Airavata 0.13 (Aug 11, 2014)
- Whats new in this release:
- A key addition in this release is addition of App catalog. The app catalog incorporates registering applications, computational resources and flexible use of job management and data movement protocols.
- More Details:
- Application Catalog
- Allow file transfer from the gateway to the resource through Airavata
- Craft data models for application catalog
- Database design for Application Catalog
- Implement App catalog open-jpa layer and resource layer
- Start app-catalog database with app catalog thrift service starts
- Adding test cases to test app-catalog cpi
- API Changes:
- AppCatalog API was added as described above.
- No changes were made to previously release API methods.
- Improvement made in this release:
- This release bundles a stable iteration of using Apache thrift as a framework to implement Airavata API.
- More Details:
- GFac Sample
- Integrate airavata credential store with GSISSH library in order to retrieve credentials
- Clone a created experiment in Orchestrator to launch on different host
- Integrate the SSH file transfer between the gateway and resources to the Gfac
- Application Catalog Design
- No error type defined for a missing Project
- Issues fixed in this release:
- Testing and bug fixing resulted in the following fixes.
- Stdout and stderr files are read as string and will be problem if the file are big
- Cleanup database sql scripts
- Host parameters not saved in the database
- Misleading error message in airavata server console when submitting a job to BR2
- Wrong exception given when certificate path is configured incorrectly
- GFacAPI logic to load input/output handlers is not working property
- Airavata 0.11 Source Build: Dependency Problems
- Update the Experiment Status
- JPARegistry tests are failing
- When entered gateway username and password user gets redirected to XSEDE user portal
- Cannot create Experiments using PHP Gateway
- Refresh button for Experiment Status page
- Cannot edit or view summery of experiments created with WRF application and its input files attached
- Cannot Save and Launch WRF experiment at the same time. It fails.
- Client Packages:
- A key client side focus of this releases is to validate Airavata functionality with PHP clients.
- a PHP Reference Gateway is developed to exercise API functionality.
- PHP command line samples also have been developed and tested against the API.
- An initial version of the C++ SDK was also contributed but is not yet fully tested.
- More Details:
- Create php Samples using Airavata Thrift API Client SDKs
- In PGA gateway, include creation time in Experiment Summary
- Upgrade Instructions:
- Airavata 0.13 should work with the previous 0.12 release.
- Older releases will need to be manually updated. Beyond 1.0, Airavata will maintain backward compatibility within
- major releases.
- Known Issues:
- Airavata 0.13 continous to be a stepping stone towards a stable 1.0 release. A known limitation is lack of a UI to register applications (using the app-catalog API).
- XBaya and the workflow capabilities are being integrated into the new architecture and do not yet work with this release. A subsequent release (0.14) will bring back workflows into a functioning.
- Documentation:
- This release was used as a tutorial to outreach apache airavata to science gateway developers.
- Tutorial documentation - https://cwiki.apache.org/confluence/display/AIRAVATA/XSEDE+2014+Tutorial
- Error data retrieval from the Airavata API
- Document Hands on tutorial material on PHP reference gateway
- Improve content coordination across website and wiki
New in Apache Airavata 0.11 (Jan 7, 2014)
- Improvement:
- Improve GFac stdout handling to cover output types
- JCR properties in GFAC's service.properties are obsolete
- Add credential store to the Airavata API
- Refactoring Integration Tests module to allow easy extendability and remove redundancy
- Task:
- Distribute JNLP With Releases
- Sub-task:
- Display status of experiments upfront in experiments list
- Update XBaya window to support file transfer
- Update Unicore client version
- Story:
- Update Airavata JGLOBUS and Unicore jar
- Bug:
- Reduce the size of war distributions
- Evaluating thrift based execution API
- GSISSH provider not fail on PBS Syntax errors
New in Apache Airavata 0.10 (Nov 9, 2013)
- Sub-task:
- GSISSH provider to run simple job manager commands provided by the user
- Input output data transfer using gsiscp or GridFTP
- Extending GFAC schema to support GSI hosts configurations
- Prepare release
- Bug:
- Cleanup configurations files
- Ensure Airavata can renew proxy for long running jobs.
- Tomcat port configuration accessing problem in certain older tomcat 7 version
- XBaya initialization fails when it is initialized from another client application
- GSISSHProviderTest is not working
- Regex in OutputUtils does not support space in output string
- When workflow fail it goes to workflow completed mode and not showing the red node
- Improvement:
- Enable CORS support in Airavata server
- Have a UserRegistry API to support user related operations
- [GSoC] JSON equivalent of XWF files
New in Apache Airavata 0.9 (Sep 24, 2013)
- New Feature:
- Integrate Credential Management service to Airavata Server
- Task:
- Negotiate with Apache Infra and increase the distribution size to 200 MB
- Prepare release
- Improvement:
- Remove invoker caching from Workflow interpreter
- Airavata API to get JOBID of GramJob based on workflow service node name
- Upgrade tomcat version used in integration-tests
- Upgrade JGlobus version to 2.0.6-RC2
- Handling of URI and URIArray containing different files with the same name should be handled correctly
- Bug:
- Confirming the airavata shutdown is completely graceful
- Airavata Client Exception handling
- Error message when I try to delete Application Service from Xbaya dashboard
- When registering urls in registry, we need to register based on transport protocol
- Xbaya does not give error messages when connecting to database with wrong credentials
- Fixing the provided samples
- Levenshtein distance sample is not working
- Fix the context root specified in the airavata-server.properties file for Airavata webapp
- Exception in jpa-registry when building in ubuntu with java 64 bit
- SSHProvider not working in trunk
- Scheduling info set from advanced options in client-side is not recovered properly at server-side
- Erroneous output is set as the input to the next node from the workflow interpreter
- EmbeddedInvoker is not parsing previous node output to the next node input correctly
- Experiment Data list return from getAllExperimentMetaInformation() method of provenance manager not sorted according to experiment submitted date
New in Apache Airavata 0.8 (Jul 17, 2013)
- New Feature:
- Introducing a HostScheduler interface and allow users to write their own HostSchedulers and register them with Airavata
- Task:
- Review gfac-core code
- Improvement:
- Delay in JobSubmissionListener after getting status from Gram
- Extending Gram RSL parameters to provide Job Name, email options
- Provide support to configure a new provider in gfac-config.xml
- Add a UI component to EC2 menu which allows a user to generate a key for EC2 communication
- Bug:
- WorkflowInterpreter had some memory leak which can be seen when send requests continuously upto 4000
- Xbaya attempt connection at a down Airavata Server
- Levenshtein Distance Sample Needs to be updated
- Airavata server populates incorrect URLs (GFac, interpretter ...) when HTTPS is enabled in tomcat
- Set host dynamically per service request
- EmbeddedGFacInvoker is not reading hostname from application scheduling context
- Tar data uploading using gridftp cient in GFAC is not complete
- In Airavata API, HPCSettings the maxWallTime is not working
- GridFTPOutputHandler is not able to download outputs from outputData folder incase of URI data type.
- Add support for GridFTP output file staging
- In GramRSLGenerator setOutputDataDirectory to context output path is not correct
- Not able to load property incase of provider properties defined in gfac-config.xml
- Error messages from Airavata API
- Use the username specifed in the workflow graph when sshing to the AMI instances
- Make credential-store specific table scripts lower case
- Error while trying to query the experiment data after few hours
- Integration tests are failing
- Renaming GFac Job related functions in the rest service and the rest client
- When the application aborts with return value of minus Status of failure is not reported in to registry
- ws-messenger services come to inconsistent state with a failure scenario
New in Apache Airavata 0.7 (Apr 16, 2013)
- Story:
- [AIRAVATA-530] - Implement a new Handler architecture
- New Feature:
- [AIRAVATA-315] - Provide an interface for Gateway administrator
- [AIRAVATA-316] - Provide a way to access the log for each experiment
- Improvement:
- [AIRAVATA-202] - Add EC2 Provider to Airavata
- [AIRAVATA-540] - There's no way to find final workflow outputs from notifications
- [AIRAVATA-780] - Add support to add multiple security context
- [AIRAVATA-782] - Add the EC2 Job Submission Schedular to the trunk
- [AIRAVATA-787] - Add support for Unicore and SSH provider in Xbaya UI
- Task:
- [AIRAVATA-471] - Add sample workflows to demonstrate the use of foreach construct
- [AIRAVATA-757] - Remove dependency to OA4MP snapshot jars once OA4MP 1.0.6 is released
- [AIRAVATA-803] - Run Amazon EC2 workflows through XBaya
- [AIRAVATA-804] - Fix the mechanism to keep the AWS secret key and access key within the workflow.
- Sub-task:
- [AIRAVATA-531] - Writing new Context classes to keep all the Context data
- [AIRAVATA-770] - Add Unicore provider to submit jobs
- [AIRAVATA-783] - Brief diagram about authentication framework
- Bug:
- [AIRAVATA-635] - Providing sample to configure workflow context header for each node
- [AIRAVATA-742] - Make authenticators.xml read default database configurations from airavata-server.properties
- [AIRAVATA-747] - SSH provider in EmbeddedGFacInvoker
- [AIRAVATA-748] - Dependencies missing for SSH provider
- [AIRAVATA-749] - Porting GSOC changes to Airavata trunk
- [AIRAVATA-750] - airavataAPI.getProvenanceManager().getExperimentDataList()
- [AIRAVATA-751] - Nullpointer exception in SSHProvider.getSession()
- [AIRAVATA-764] - Job should not be canceled if there is a job error.
- [AIRAVATA-765] - GridFTPOutputHandler need to return file url incase output type in URI
- [AIRAVATA-772] - Cannot start Airavata on Windows
- [AIRAVATA-773] - XBaya does not work on Windows
- [AIRAVATA-775] - Add the EC2 UI components to XBaya
- [AIRAVATA-778] - Xbaya workflow editor: "Airavata Registry" panel doesn't update after making changes
- [AIRAVATA-781] - Add a test case to gfac core to submit EC2 jobs
- [AIRAVATA-799] - Gram job data storing failing
- [AIRAVATA-801] - 10 mins sample failed in 0.7 RC2
- [AIRAVATA-809] - EC2 Instance Management window is not properly functioning due to backend issues
- [AIRAVATA-812] - Add documentation for EC2 job submissions through XBaya
- [AIRAVATA-813] - Incorrect instructions given in the wiki for Sample Workflow SimpleForEach
- [AIRAVATA-815] - Issues when terminating and starting instances/AMIs using Amazon instance management window
- [AIRAVATA-816] - Workflow Run sample fails because of wrong host
New in Apache Airavata 0.6 (Jan 31, 2013)
- New Feature
- Support for individual users in a community
- Add basic auth based authenticator to Airavata
- Add support to connect different types of user stores to authenticate Airavata REST API
- Change Airavata API (airavata-client) to use Airavata REST Service
- Change XBaya to use the Airavata Client
- Change XBaya to use Airavata Client for Workflow Launches
- Improvement
- Provide WorklfowNodeID in wokflowInvoked Notification
- Change default authenticating database to Derby
- Provide a utility method to set basic access headers in client side
- Use Embedded Tomcat as servlet container for Airavata
- Create a context class to store request specific properties
- Improving Application Manager API
- Add stop monitoring functionality for the Monitor object
- Improvements to the WorkflowManager API
- BPELScript log messages to parse wsdl should be of debug level
- Enable rest client to communicate over HTTPS
- Task
- Adding REST interface to Airavata Registry API
- Update LICENSE & NOTICE files in distribution
- Simplify runExperiment function overloading in Execution Manager
- Make the WorkflowContextHeaderBuilder transparent to the API User
- Move the registry related property data included on airavata-client and airavata-server properties files instead
- Generate a WAR distribution for Airavata Server at build time
- Sub-task
- Update Audit Notifier
- Update Performance Notifier
- Bug
- A notification is sent out with the description "Invoking a workflow" for each service invocation this is misleading.
- During workflow data saving node with a name of "experiments[1]" creating
- MsgBoxWsaResponsesCorrelator is creating an infinite thread and there's no way to interrupt that thread
- WorkflowInterpretorEventListener is accumulating - not properly shutting down
- Error in console when running a workflow- Not always
- Add new user displays user add to JCR registry
- Add different registry accessors to airavata-server.properties and update AiravataJPARegistry accordingly
- Make tests work with paths that include spaces (Fix build failure in tests due to paths with spaces)
- MsgBoxWsaResponseCorrelator thread is not returning
- Provide a sample how to push notification messages to someother endpoint after capturing them in airavata client
- Create Java REST client to REST service
- Cannot start Airavata if the installed path contains spaces
- Null pointer exception is thrown from REST service when calling the registry API
- Adding embedded tomcat as default server to Airavata
- Application Service menu get repeated in XBAya GUI
- Enable hash passwords in Airavata local user store and make SHA as default password hash method
- Failed login when connecting to an existing database
- Lonestar GridFTP URL is wrong in default host objects
- Not able to set HPC Configuration on New Application Deployment screen. Urgent!!
- Edit Application- Edit deployment link does not work
- Edit Application > Edit deployment > Scratch working directory empty
- Airavata-client needs database configuration in client side code which is wrong
- When executing workflow user is authenticated multiple times for the same session
- Edit Host Description dialog vanishes once one description get deleted
- Maven clean install does not remove existing target folders for xbaya-gui
- There are some dependencies missing in Airavata client distribution
- Updating the HPC Configuration Options
- XBaya doesn't return when backend gfac operation fail
- Cleaning up unnecessary dependencies from Xbaya distribution and airavata-client distribution
- Database setting are picked up from registry.properties.
- An exception while starting integration tests
- A valid SimpleMathService is not available for the 5 minute tutorial
- Airavata distributions are not installed to the maven repository
- OutputDataSettings does not have method to set node information.
- Advanced options are not saved when creating an application
- Multiple Workflow is invoked messages in the workflow
- Airavata startup fails when Airavata is pointed to a new database
New in Apache Airavata 0.5 (Jan 31, 2013)
- New Feature
- Add do-while support to Xbaya and workflow engine
- Hide workflow experiment ID from the user and allow user to add a user friendly experiment ID
- Add XBaya JNLP generation to the Airavata Build
- Implement StringArray incase output parameters are coming multiple times in STDOUT
- Replacing existing Jackrabbit registry with MySQL
- Improvement
- Consolidate XBaya Web Service Invoker Clients and Re-factor them to use Axis2
- XBaya not prompting Myproxy dialog for secure workflow invocation
- Managing Shutdown tasks using shutdown hooks
- Adding Embedded GFac feature in to ducumentation
- Add sample workflows to be shipped with Airavata to demonstrate grid job submissions
- Add scripts to run Airavata in Windows environment
- Some code is duplicated in AiravataJCRregistry
- Some improvements to "Airavata HowTo" doc
- Implementing Persistency Data Storage for Airavata
- Need to remove jackrabbit dependency from 0.5 build
- Cleanup XBaya Invokers and remove legacy security calls
- Cleanup all myproxy and gsi dependencies from XBaya
- Bug
- GridFTPFileTransferClient has file paths that refer to a local file paths need to generalize this
- After changing the username of jackrabbit still I can save service description
- ConcurrentModificationException during using RegistryAPI
- Deprecating xbaya engine running in the gui mode and make WorkflowInterpreter invocation by default
- No log file is creating during standalone mode run of Airavata server
- Input Output node data can not be retreived by using Airavata API's ProvananceManager
- Application Failed status is not updated in XBaya
- Monitor panel does not report final error when a node fails
- Error creating the database in Windows environment - When starting the Airavata Server
- getWorkflowExecutionByUser(...) method implementation is not correct
- Could not deploy WS-Messenger with MySQL
- minutes tutorial fails when running WS-Messenger with MySQL
- Improvements to AiravataJCRRegistry class
- ForEach does not work if Array size is 1
- Data type of workflow_graph and workflow_content of User_Workflow table and Published_Workflow table should be BLOB datatype
- Supporting derby by default for airavata
- Make run button of Xbaya to go through interpreter server by default
- GridFTP transfer does not set type to Binary for binary data
- Node deletion is giving some issues
- Error when try to open a workflow from filesystem
- Improving data retrieval time in provenance data
- Gram RSL generated is missing the jobtype parameter
- XBaya pom have Junit jar version but its not added to properties
- Warn user before closing XBaya
- Remove derby.sh and startNetworkServer scripts
- File transfer error getting masked to a general error
New in Apache Airavata 0.4 (Jan 31, 2013)
- New Feature
- Develop Gdirftp and and file transfer utils to GFac
- Support http url sameway gridftp url is supported in the GFac URI type
- Add while construct
- Allow workflow intepreter to start executing even when all the "Input Node" valuese are not set
- XRegistry entries transfer (from OGCE XRegistry to Airavata XRegistry)
- Integrate GFac with XBaya to run in embedded mode
- Creating temporary location based on the given executable location
- Adding default set of host descriptions during startup
- Allowing users disable some of the input Nodes in a workflow during Invocation
- Allowing users to specify the workflow name during XBaya startup and open the given workflow
- Create a getter on AiravataClient to read the location to save the output file
- Add XBaya JNLP generation to the Airavata Build
- Task
- Refactor XBaya
- Sub-task
- Create documentation for XRegistry to Airavata Registry migration tool
- Gram and GridFTP ERP's are not populated in XRegistry entries transfer
- Application temporary directory was not populated
- Service Inputs and outputs are not coming
- Verify different name spaces
- After migration of xregistry resources, Application Services are not listed in Component List
- Compare the OGCE Schema and Airavata Schema then add missing parts to airavata Schema
- Do-While GUI component
- Changing the workflow model for do-while
- Add Do-while handler for Workflow Interpreter
- Improvement
- Making the timeout value configurable in ws-messenger client package
- Add validation in to airavata before submitting jobs to Grid
- Xbaya Application description GUI
- Copying gridftp and urls in to Grid during input Staging
- Allowing users to configure the XBaya GUI placement in the screen
- Allowing users to give empty String and URL inputs for a workflow
- Workflow Execution Context should be used for all workflow executions
- Adding monitoring capability to AiravataClient
- GFac outputdata directory name should be customizable from application description
- Extension for Application Deployment Description to specify Hadoop provider specific parameters
- Create java docs with the build using maven
- Airavata API improvements
- Add a document describing Airavata Users to the website
- Service outputs as stdout and stderr
- Bug Fixes
- Threads get create continuously in WorkflowInterpreter during accessing registry
- Error while saving Gram Configuration
- Host description update doesn't work properly
- Huge Error message box comes when try to show an huge error
- GFac doesn't keep the order properly for application invocation
- Workflow loading when there's a URIParameterType is there in the workflow
- Wrong workflow is saving so during loading of the workflow it shows a weird input nodes without Edges
- Registry related commandline arguments are not picked up by the XBaya GUI
- Cannot configure input nodes by clicking on inputNodes
- Error while processing input from another node at Gfac-service
- gfac fails with ArrayInput types
- Service Description editing fails
- Notifications are not delivering sometimes when a workflow run in Interpreter Service mode
- Handling application exit codes and if its non zero through and error up to XBaya GUI
- Propagate GFac failures in to XBaya GUI properly and make the failure nodes red
- jackrabbit.log_IS_UNDEFINED
- Error when importing a workflow from file system
- GFAC is not creating outputData directory for GRAM Jobs
- outputData directory variable is set as inputData in Gram RSL
- GFAC does not support reading output data directly from outputData and set values into output array
- Sometimes Gfac notifications are not receiving to XBaya so the failures scenarios are not visible to the user
- Input type URIArray is not handled properly
- WorkflowInterpreter notification is broken
- Changing the host dynamically based on the request content
- Not able to Run a local service in GFAC from Xbaya
- workflow option doesn't work on trunk
- Workflow nodes are not becoming red when it failes but it receives the proper notification
- NPE while starting Airavata Server
- Saved workflow with EndWhile is loading the component wrong
- NPE when deploying Airavata on Tomcat
- Cannot add multipe hosts for a single service
- Gram Hosts are not showing properly in XBAya gui
- When connecting through XBaya to an Airavata which is deployed on tomcat, MessageBox and MessageBroker URLs are not propagated properly
- Test
- Add more test cases to cover ForEach construct functionality
New in Apache Airavata 0.3 (Jan 31, 2013)
- New Feature
- Workflow Execution Context Header schema
- Allow users to configure provenacne Writer Thread pool size and shutdown the thread pool during service shutdown
- Need Maven profiles for building Airavata clients.
- Task
- Adding a Sample which demonstares the usage of XMLBean generated POJO classes
- create documentation for how to use XBayaClient with a sample code
- Document the xbaya.properties file entries used in WorkflowInterpreter service in detail
- Document how to invoke echo service in one of the super computers (ranger)
- Sub-task
- Test Foreach when workflow interpreter is running without the ws-messenger
- Long running stress evaluation of workflow interpreter without the ws-messenger
- name all module jars with airavata prefix
- Improvement
- Remove weps.jar
- Improve WorkflowInterpreter to run multiple jobs in parallel
- minimize the default size of XBaya Window
- Providing multiple port suppor for EndForEach Node
- Threads get created during a long run of Interpreter service
- xml serialization error in 10 minute tutorial
- Remove messenger to attic
- Allow users to configure the time interval to delete old messageboxes
- Create new api method to initialize the XBaya client without the notificaton listner
- Move the XBayaClient to a separate module
- remove src and target folders from binary distribution of samples
- Bug
- Fix intermittent test failures in XBaya test cases
- Hyphen replacement is not working properly
- XBaya UI Application Description saving - executable selection doens't work properly
- PUBLISHER threads are not interrupted after the workflow inovacation
- Unnecessary QueueName element in ApplicationDescription dialog
- Old messagebox deletion doesn't work
- Registry API random test failures
- In a long run messagePuller threads are not killing completely
- New Deployment Description panel "save" button
- Not able to edit existing service description
- New Deployment Description panel layout issue
- Host Description Advanced Options panel layout issue
- Update Gram Configuration Dialog to accept Static Working Directory option
- jobs fails with lack of memory in batch submission
- Improve GramProvider to support transfer of local files
- Test
- Create a Edit distance based dot product and cartisian product ForEach test case
New in Apache Airavata 0.2 (Jan 31, 2013)
- New Feature
- Allow creating new account using XBaya GUI for Jackrabbit registry
- Task
- Creating a document how to deploy gfac-axis2 service on axis2
- Deprecate support for GPEL Client in XBaya
- Disable Jython Execution Menu
- Update the site documentation
- Create new document for advance workflow sample running
- Add the Complex-math-service and Levinshtine-distance-service to the maven build, in order to build axis2 service archives
- Improvement
- Workflow launch input box requires inserting xml wrapper elements
- Workflow Interpreter should go to pause if it waits on a failed service
- Popup save dialog when closing the workflow tab if changed
- Add more samples/workflows which demonstrates the use of basic constructs
- Allow user to browse the Application during definition of application description
- Review XBaya code
- Deprecate Stream component
- Ability to edit existing application/service and host descriptions
- Check App/Service/host descriptions before saving whether it overrides existing document
- Bug
- Workflow interpreter- Workflow already running
- WS-Notification monitoring tool is failing in airavata
- When adding a ServiceDescription through the UI sometimes the out parameter is not added
- Messagebox test should skip if a listener port cannot be started on machine due to firewall or system issues.
- XBaya Registry Test throws XML Parsing error
- XBaya console error: node does not have a parent
- SimpleMathService can be added 2 time but not more than that
- GramProvider Test is failing with new schema
- Application registration randomly sets application name to Application1
- Appearence of dynamic workflow run toolbar during workflow execution
- Inconsistency in managing of the Workflow instance status from GUI
- XBaya Registry Connection Error Message
- ressurect workflow test
- HostDescription is allowed to be saved over and over in HostDescriptionDialog
- CrossProductWorkflowTest fails with a NP
- Fixing a build failure in WorkflowTrackingTest
- Test
- Include a workflow tracking test that include the Messaging system
- Registry Delete test
- Registry Restart while XBaya is running Test