[jira] [Resolved] (AIRAVATA-844) Documenting all the airavata-server.properties file properties in wiki.
[ https://issues.apache.org/jira/browse/AIRAVATA-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Gunathilake resolved AIRAVATA-844. - Resolution: Fixed I have documented the airavata-server.properties information and updated it related to 0.12 release. Documenting all the airavata-server.properties file properties in wiki. --- Key: AIRAVATA-844 URL: https://issues.apache.org/jira/browse/AIRAVATA-844 Project: Airavata Issue Type: Bug Affects Versions: 0.12 Reporter: Lahiru Gunathilake Assignee: Lahiru Gunathilake Priority: Critical $subject -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (AIRAVATA-942) GFAC SchedulerTest is obsolete
[ https://issues.apache.org/jira/browse/AIRAVATA-942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13955188#comment-13955188 ] ASF subversion and git services commented on AIRAVATA-942: -- Commit 460da0ef39ebf3a4b62f32148a7c4990d7d8214b in airavata's branch refs/heads/master from lahiru [ https://git-wip-us.apache.org/repos/asf?p=airavata.git;h=460da0e ] fixng AIRAVATA-942, no scheduling activity is there in gfac at this point GFAC SchedulerTest is obsolete -- Key: AIRAVATA-942 URL: https://issues.apache.org/jira/browse/AIRAVATA-942 Project: Airavata Issue Type: Improvement Reporter: Marlon Pierce Priority: Minor Fix For: 0.12 This test is completely commented out. The code depends on the obsolete registry implementation. It should be deleted. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (AIRAVATA-759) GSISSH-Grid security provider to run remote jobs
[ https://issues.apache.org/jira/browse/AIRAVATA-759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raminderjeet Singh updated AIRAVATA-759: Fix Version/s: 0.12 GSISSH-Grid security provider to run remote jobs Key: AIRAVATA-759 URL: https://issues.apache.org/jira/browse/AIRAVATA-759 Project: Airavata Issue Type: Epic Components: GFac Affects Versions: 0.10 Reporter: Raminderjeet Singh Assignee: Raminderjeet Singh Fix For: 0.12 Provider will help users to run/monitor batch jobs using grid security. Grid machines can have different job managers like PBS/SGE/SLURM so we need to create job scripts based on type of job manager. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (AIRAVATA-1082) Make SSH provider(Fork jobs) work with JCraft
[ https://issues.apache.org/jira/browse/AIRAVATA-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raminderjeet Singh updated AIRAVATA-1082: - Fix Version/s: (was: 0.13) 0.12 Make SSH provider(Fork jobs) work with JCraft - Key: AIRAVATA-1082 URL: https://issues.apache.org/jira/browse/AIRAVATA-1082 Project: Airavata Issue Type: Improvement Components: GFac Reporter: Raminderjeet Singh Assignee: Raminderjeet Singh Fix For: 0.12 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (AIRAVATA-1082) Make SSH provider(Fork jobs) work with JCraft
[ https://issues.apache.org/jira/browse/AIRAVATA-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raminderjeet Singh resolved AIRAVATA-1082. -- Resolution: Fixed Fixed with commits Make SSH provider(Fork jobs) work with JCraft - Key: AIRAVATA-1082 URL: https://issues.apache.org/jira/browse/AIRAVATA-1082 Project: Airavata Issue Type: Improvement Components: GFac Reporter: Raminderjeet Singh Assignee: Raminderjeet Singh Fix For: 0.12 -- This message was sent by Atlassian JIRA (v6.2#6252)
Cleaning up unused modules before the 0.12 release
Hi All, In 0.12 release we are not using following modules and what is our plan on these modules. Are we going to ship this sources with 0.12 release ? modules/xbaya modules/workflow-interpreter modules/ws-messenger/client modules/ws-messenger/commons modules/ws-messenger/distribution modules/ws-messenger/message-monitor modules/ws-messenger/messagebox modules/ws-messenger/messagebroker modules/ws-messenger/samples modules/rest/client modules/rest/mapping modules/rest/service modules/rest/webapp I think we should not ship these unused code in the release. Either we have to fix the trunk by moving these code to sandbox or to another branch or we have to branch 0.12 without these modules and make airavata compile and work and then release 0.12. WDYT ? Regards Lahiru -- System Analyst Programmer PTI Lab Indiana University
Re: Cleaning up unused modules before the 0.12 release
I also don't think we should ship these. Can we delete the REST module? It will always be in the 0.11 tag. One option for the remaining stuff (which we will return to, like the Workflow-Interpreter) is to leave them in the trunk/master and omit them from the 0.12 tag release. Marlon On 3/31/14 10:10 AM, Lahiru Gunathilake wrote: Hi All, In 0.12 release we are not using following modules and what is our plan on these modules. Are we going to ship this sources with 0.12 release ? modules/xbaya modules/workflow-interpreter modules/ws-messenger/client modules/ws-messenger/commons modules/ws-messenger/distribution modules/ws-messenger/message-monitor modules/ws-messenger/messagebox modules/ws-messenger/messagebroker modules/ws-messenger/samples modules/rest/client modules/rest/mapping modules/rest/service modules/rest/webapp I think we should not ship these unused code in the release. Either we have to fix the trunk by moving these code to sandbox or to another branch or we have to branch 0.12 without these modules and make airavata compile and work and then release 0.12. WDYT ? Regards Lahiru
Re: Cleaning up unused modules before the 0.12 release
Lahiru, I see two parts of this cleanup. The modules we will integrate back in the near future and the ones we will deprecate for good. I vote for deleting the ones like the registry rest modules and keep the ones like xbaya, interpreter and ws-messenger. Suresh On Mar 31, 2014, at 10:10 AM, Lahiru Gunathilake glah...@gmail.com wrote: Hi All, In 0.12 release we are not using following modules and what is our plan on these modules. Are we going to ship this sources with 0.12 release ? modules/xbaya modules/workflow-interpreter modules/ws-messenger/client modules/ws-messenger/commons modules/ws-messenger/distribution modules/ws-messenger/message-monitor modules/ws-messenger/messagebox modules/ws-messenger/messagebroker modules/ws-messenger/samples modules/rest/client modules/rest/mapping modules/rest/service modules/rest/webapp I think we should not ship these unused code in the release. Either we have to fix the trunk by moving these code to sandbox or to another branch or we have to branch 0.12 without these modules and make airavata compile and work and then release 0.12. WDYT ? Regards Lahiru -- System Analyst Programmer PTI Lab Indiana University
[jira] [Closed] (AIRAVATA-1004) airavata-server.properties in duplicate locations
[ https://issues.apache.org/jira/browse/AIRAVATA-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Gunathilake closed AIRAVATA-1004. airavata-server.properties in duplicate locations - Key: AIRAVATA-1004 URL: https://issues.apache.org/jira/browse/AIRAVATA-1004 Project: Airavata Issue Type: Bug Components: Airavata API, Distribution, Integration Tests Affects Versions: 0.12 Reporter: Raminderjeet Singh Priority: Critical Airavata server property file is in duplicate location and it caused Airavata-1001 as the files at 2 following locations were out of sync. ./modules/distribution/airavata-server/src/main/resources/conf/airavata-server.properties ./modules/rest/webapp/src/main/resources/airavata-server.properties. We need to fix this by having file at a single location and copy it as needed. Integration test were working fine as file used by integration test were updated with new properties but not the file in distribution. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (AIRAVATA-1066) GSISSH Monitoring error-Error retrieving the job status
[ https://issues.apache.org/jira/browse/AIRAVATA-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Gunathilake resolved AIRAVATA-1066. -- Resolution: Fixed This happens due to an error in qstat failing continuously 3 times. Now monitoring is different from the initial version so this issue is obsolete. GSISSH Monitoring error-Error retrieving the job status --- Key: AIRAVATA-1066 URL: https://issues.apache.org/jira/browse/AIRAVATA-1066 Project: Airavata Issue Type: Bug Components: Airavata Job Monitor Reporter: Raminderjeet Singh Assignee: Raminderjeet Singh Fix For: 0.12 I submitted a MPI job to Trestles and job is still in queue but at job monitoring failed with following error. [INFO] Job ID:1967610.trestles-fe1.local is QUEUED [ERROR] Error retrieving the job status [ERROR] Error retrieving the job status [ERROR] Tryied to monitor the job 3 times, so dropping of the the Job with ID: 1967610.trestles-fe1.local [ERROR] Error retrieving the job status -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (AIRAVATA-1066) GSISSH Monitoring error-Error retrieving the job status
[ https://issues.apache.org/jira/browse/AIRAVATA-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Gunathilake closed AIRAVATA-1066. GSISSH Monitoring error-Error retrieving the job status --- Key: AIRAVATA-1066 URL: https://issues.apache.org/jira/browse/AIRAVATA-1066 Project: Airavata Issue Type: Bug Components: Airavata Job Monitor Reporter: Raminderjeet Singh Assignee: Raminderjeet Singh Fix For: 0.12 I submitted a MPI job to Trestles and job is still in queue but at job monitoring failed with following error. [INFO] Job ID:1967610.trestles-fe1.local is QUEUED [ERROR] Error retrieving the job status [ERROR] Error retrieving the job status [ERROR] Tryied to monitor the job 3 times, so dropping of the the Job with ID: 1967610.trestles-fe1.local [ERROR] Error retrieving the job status -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (AIRAVATA-739) There should be a way to check whether the services are being up
[ https://issues.apache.org/jira/browse/AIRAVATA-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chathuri Wimalasena updated AIRAVATA-739: - Fix Version/s: (was: 0.12) 0.13 There should be a way to check whether the services are being up Key: AIRAVATA-739 URL: https://issues.apache.org/jira/browse/AIRAVATA-739 Project: Airavata Issue Type: Bug Components: GFac, Registry API, Workflow Interpreter, WS-Messenger Affects Versions: 0.6 Reporter: Chathuri Wimalasena Fix For: 0.13 There should be a way to check whether all the services are up. For example, in the registry API, there is a method called isActive () which we haven't implemented at the moment. In the similar manner, we need to have some functions to check whether other four services are being up and running. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (AIRAVATA-739) There should be a way to check whether the services are being up
[ https://issues.apache.org/jira/browse/AIRAVATA-739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13955238#comment-13955238 ] Chathuri Wimalasena commented on AIRAVATA-739: -- This issue might no longer valid for new architecture since we have all the services as Thrift services. There should be a way to check whether the services are being up Key: AIRAVATA-739 URL: https://issues.apache.org/jira/browse/AIRAVATA-739 Project: Airavata Issue Type: Bug Components: GFac, Registry API, Workflow Interpreter, WS-Messenger Affects Versions: 0.6 Reporter: Chathuri Wimalasena Fix For: 0.13 There should be a way to check whether all the services are up. For example, in the registry API, there is a method called isActive () which we haven't implemented at the moment. In the similar manner, we need to have some functions to check whether other four services are being up and running. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (AIRAVATA-1006) Craft the Registry 1.0 CPI
[ https://issues.apache.org/jira/browse/AIRAVATA-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chathuri Wimalasena updated AIRAVATA-1006: -- Fix Version/s: (was: 0.12) 1.0 Craft the Registry 1.0 CPI -- Key: AIRAVATA-1006 URL: https://issues.apache.org/jira/browse/AIRAVATA-1006 Project: Airavata Issue Type: Sub-task Reporter: Suresh Marru Fix For: 1.0 As the Airavata API is evolving towards 1.0 version, we need to refine the currently Registry API (and the current Airavata Client-Registry API) into a unified and well defined Registry CPI. This registry CPI is targeted to be invoked by the Airavata API functions and use of Registry by all internal Airavata internal components like Orchestrator, Workflow Interpreter and GFac. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (AIRAVATA-1060) Disable the obsolete modules from the trunk build
[ https://issues.apache.org/jira/browse/AIRAVATA-1060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Gunathilake resolved AIRAVATA-1060. -- Resolution: Fixed Disable the obsolete modules from the trunk build - Key: AIRAVATA-1060 URL: https://issues.apache.org/jira/browse/AIRAVATA-1060 Project: Airavata Issue Type: Task Reporter: Saminda Wijeratne Assignee: Suresh Marru Fix For: 0.12 With the introduction of the new Airavata architecture we have several modules becoming deprecated and some modules not targeted for the upcoming 0.12 release. We need to disable them from the build. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (AIRAVATA-1060) Disable the obsolete modules from the trunk build
[ https://issues.apache.org/jira/browse/AIRAVATA-1060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Gunathilake closed AIRAVATA-1060. Disable the obsolete modules from the trunk build - Key: AIRAVATA-1060 URL: https://issues.apache.org/jira/browse/AIRAVATA-1060 Project: Airavata Issue Type: Task Reporter: Saminda Wijeratne Assignee: Suresh Marru Fix For: 0.12 With the introduction of the new Airavata architecture we have several modules becoming deprecated and some modules not targeted for the upcoming 0.12 release. We need to disable them from the build. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (AIRAVATA-825) Airavata Client error in case workflow scheduling context is not right
[ https://issues.apache.org/jira/browse/AIRAVATA-825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Gunathilake closed AIRAVATA-825. --- Airavata Client error in case workflow scheduling context is not right -- Key: AIRAVATA-825 URL: https://issues.apache.org/jira/browse/AIRAVATA-825 Project: Airavata Issue Type: Bug Affects Versions: 0.8 Reporter: Raminderjeet Singh Assignee: Lahiru Gunathilake Fix For: 0.12 I am trying to set the hostname to run the application but if the hostname is not correct or registered, there is a null pointer error but the API does not return anything to client and its not possible to report this error to use. We need to improve the error message also. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (AIRAVATA-825) Airavata Client error in case workflow scheduling context is not right
[ https://issues.apache.org/jira/browse/AIRAVATA-825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Gunathilake resolved AIRAVATA-825. - Resolution: Invalid This is an obsolete issue. Airavata Client error in case workflow scheduling context is not right -- Key: AIRAVATA-825 URL: https://issues.apache.org/jira/browse/AIRAVATA-825 Project: Airavata Issue Type: Bug Affects Versions: 0.8 Reporter: Raminderjeet Singh Assignee: Lahiru Gunathilake Fix For: 0.12 I am trying to set the hostname to run the application but if the hostname is not correct or registered, there is a null pointer error but the API does not return anything to client and its not possible to report this error to use. We need to improve the error message also. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (AIRAVATA-901) Provide Update Notification to Registry clients caching data
[ https://issues.apache.org/jira/browse/AIRAVATA-901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13955261#comment-13955261 ] Lahiru Gunathilake commented on AIRAVATA-901: - Moved the issue to 0.13 since this is an important improvement to make the api usable with large dataset. Provide Update Notification to Registry clients caching data Key: AIRAVATA-901 URL: https://issues.apache.org/jira/browse/AIRAVATA-901 Project: Airavata Issue Type: Improvement Reporter: Suresh Marru Assignee: Chathuri Wimalasena Fix For: 0.13 Clients can fetch information from registry and cache it locally or in memory for performance reasons. They would like to be notified when update to this semi-static information happens. An use case like refreshing xbaya registry panel described in https://gateways.atlassian.net/browse/PARAMCHEM-114 will benefit from this feature. Kishore from Apache Helix community has mentioned similar registry client notification used within linked in with a possibility of being open sourced. We need to check if this is available in any helix components and re-use the software or the concept. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (AIRAVATA-762) Advanced Job scripts based on job manager type
[ https://issues.apache.org/jira/browse/AIRAVATA-762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Gunathilake reassigned AIRAVATA-762: --- Assignee: Lahiru Gunathilake Advanced Job scripts based on job manager type -- Key: AIRAVATA-762 URL: https://issues.apache.org/jira/browse/AIRAVATA-762 Project: Airavata Issue Type: Sub-task Components: GFac Affects Versions: 0.7 Reporter: Raminderjeet Singh Assignee: Lahiru Gunathilake Fix For: 0.12 Job manager like PBS/SGE/SLURM have different format of job script. Create a util method to create scripts for different format. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (AIRAVATA-964) Add single job support as a first class simple Apache Airavata Execution
[ https://issues.apache.org/jira/browse/AIRAVATA-964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Gunathilake updated AIRAVATA-964: Fix Version/s: (was: 0.12) Add single job support as a first class simple Apache Airavata Execution Key: AIRAVATA-964 URL: https://issues.apache.org/jira/browse/AIRAVATA-964 Project: Airavata Issue Type: Epic Components: Airavata Client, GFac Reporter: Suresh Marru Labels: Architecture Fix For: 0.13 Attachments: Airavata-Single-Job-Execution.png Currently Airavata supports single jobs by wrapping it as a single node task within a workflow. This wrapping is justified if workflow is the predominant use of Airavata and single application execution is a rare usage pattern. As Airavata is getting more usage, the simple execution but for large number of invocations and diverse applications is getting more widely used. Providing a first class way of a simple application execution will reduce the overhead in creating and managing workflows. But this takes away all the orchestration capabilities provided by the Workflow Interpreter. This Epic is to discuss a new component to Airavata which provides based job orchestration while persisting the request state to registry so the application management component (GFac) can be stateless and recover the job from a frequently checkpointed state from the registry -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (AIRAVATA-981) Download links for current release hashes etc must use main ASF server
[ https://issues.apache.org/jira/browse/AIRAVATA-981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Gunathilake resolved AIRAVATA-981. - Resolution: Fixed Based on these comments, this issue is fixed. Download links for current release hashes etc must use main ASF server -- Key: AIRAVATA-981 URL: https://issues.apache.org/jira/browse/AIRAVATA-981 Project: Airavata Issue Type: Bug Reporter: Sebb Assignee: Suresh Marru Fix For: 0.12 Attachments: AIRAVATA-981-Fix.patch, AIRAVATA-981.patch The download page [1] contains links for hashes and sigs, which is good. However these currently point to the archive server; they should point to the main ASF server instead [2], as is already done for the KEYS file. [1] http://airavata.apache.org/about/downloads.html [2] http://www.apache.org/dev/release-download-pages.html#links -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (AIRAVATA-981) Download links for current release hashes etc must use main ASF server
[ https://issues.apache.org/jira/browse/AIRAVATA-981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Gunathilake closed AIRAVATA-981. --- Download links for current release hashes etc must use main ASF server -- Key: AIRAVATA-981 URL: https://issues.apache.org/jira/browse/AIRAVATA-981 Project: Airavata Issue Type: Bug Reporter: Sebb Assignee: Suresh Marru Fix For: 0.12 Attachments: AIRAVATA-981-Fix.patch, AIRAVATA-981.patch The download page [1] contains links for hashes and sigs, which is good. However these currently point to the archive server; they should point to the main ASF server instead [2], as is already done for the KEYS file. [1] http://airavata.apache.org/about/downloads.html [2] http://www.apache.org/dev/release-download-pages.html#links -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (AIRAVATA-1092) Add an Integration test to check Airavata server startup and graceful shutdown
[ https://issues.apache.org/jira/browse/AIRAVATA-1092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Gunathilake updated AIRAVATA-1092: - Fix Version/s: (was: 0.12) 0.13 Add an Integration test to check Airavata server startup and graceful shutdown -- Key: AIRAVATA-1092 URL: https://issues.apache.org/jira/browse/AIRAVATA-1092 Project: Airavata Issue Type: Sub-task Reporter: Sachith Withana Fix For: 0.13 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (AIRAVATA-1092) Add an Integration test to check Airavata server startup and graceful shutdown
[ https://issues.apache.org/jira/browse/AIRAVATA-1092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13955274#comment-13955274 ] Lahiru Gunathilake commented on AIRAVATA-1092: -- We do not support graceful shutdown in 0.12 release. We have an intermittent issue with graceful shutdown. So moving this issue to 0.13. Add an Integration test to check Airavata server startup and graceful shutdown -- Key: AIRAVATA-1092 URL: https://issues.apache.org/jira/browse/AIRAVATA-1092 Project: Airavata Issue Type: Sub-task Reporter: Sachith Withana Fix For: 0.13 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (AIRAVATA-1053) Update Integration-test module
[ https://issues.apache.org/jira/browse/AIRAVATA-1053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Gunathilake updated AIRAVATA-1053: - Fix Version/s: (was: 0.12) 0.13 Update Integration-test module -- Key: AIRAVATA-1053 URL: https://issues.apache.org/jira/browse/AIRAVATA-1053 Project: Airavata Issue Type: Bug Reporter: Saminda Wijeratne Fix For: 0.13 Current integration test module focuses on deploying Airavata on a tomcat server and testing workflow executions against that server. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (AIRAVATA-1063) HostAddress in ComputationalResourceScheduling is required.
[ https://issues.apache.org/jira/browse/AIRAVATA-1063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13955276#comment-13955276 ] Lahiru Gunathilake commented on AIRAVATA-1063: -- Moved to 0.13 release. HostAddress in ComputationalResourceScheduling is required. --- Key: AIRAVATA-1063 URL: https://issues.apache.org/jira/browse/AIRAVATA-1063 Project: Airavata Issue Type: Task Reporter: Raminderjeet Singh Assignee: Raminderjeet Singh Fix For: 0.13 Client need to set resourceHostId for every request if the auto schedule is false. Another information, Airavata have hostName(gsi-trestles) and hostAddress in the registry descriptor. ComputationalResourceScheduling in create experiment expect resourceHostId but its really hostAddress not name. Make sure you send the hostAddress like trestles.sdsc.edu to make request works fine. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (AIRAVATA-1063) HostAddress in ComputationalResourceScheduling is required.
[ https://issues.apache.org/jira/browse/AIRAVATA-1063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Gunathilake updated AIRAVATA-1063: - Fix Version/s: (was: 0.12) 0.13 HostAddress in ComputationalResourceScheduling is required. --- Key: AIRAVATA-1063 URL: https://issues.apache.org/jira/browse/AIRAVATA-1063 Project: Airavata Issue Type: Task Reporter: Raminderjeet Singh Assignee: Raminderjeet Singh Fix For: 0.13 Client need to set resourceHostId for every request if the auto schedule is false. Another information, Airavata have hostName(gsi-trestles) and hostAddress in the registry descriptor. ComputationalResourceScheduling in create experiment expect resourceHostId but its really hostAddress not name. Make sure you send the hostAddress like trestles.sdsc.edu to make request works fine. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (AIRAVATA-1053) Update Integration-test module
[ https://issues.apache.org/jira/browse/AIRAVATA-1053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13955278#comment-13955278 ] Lahiru Gunathilake commented on AIRAVATA-1053: -- moved this issue to 0.13 because its remaining child issue has moved to 0.13 release. Update Integration-test module -- Key: AIRAVATA-1053 URL: https://issues.apache.org/jira/browse/AIRAVATA-1053 Project: Airavata Issue Type: Bug Reporter: Saminda Wijeratne Fix For: 0.13 Current integration test module focuses on deploying Airavata on a tomcat server and testing workflow executions against that server. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (AIRAVATA-1017) Craft data management models
[ https://issues.apache.org/jira/browse/AIRAVATA-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Gunathilake updated AIRAVATA-1017: - Fix Version/s: (was: 0.12) Craft data management models Key: AIRAVATA-1017 URL: https://issues.apache.org/jira/browse/AIRAVATA-1017 Project: Airavata Issue Type: Sub-task Reporter: Suresh Marru Fix For: 0.13 Attachments: registry_new.png This should include basic storing of user created projects, experiments and airavata generated metadata, monitoring data and inferred provenance data and finally place holder for error handling. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (AIRAVATA-949) Update release management page step 11
[ https://issues.apache.org/jira/browse/AIRAVATA-949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Gunathilake resolved AIRAVATA-949. - Resolution: Fixed This issue is resolved based on the comments. Update release management page step 11 -- Key: AIRAVATA-949 URL: https://issues.apache.org/jira/browse/AIRAVATA-949 Project: Airavata Issue Type: Improvement Reporter: Raminderjeet Singh Assignee: Suresh Marru Fix For: 0.12 Sign the binary artifacts need to be updated for signing 3 different distribution files for airavata-server, airavata-client and xbaya. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (AIRAVATA-964) Add single job support as a first class simple Apache Airavata Execution
[ https://issues.apache.org/jira/browse/AIRAVATA-964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Gunathilake closed AIRAVATA-964. --- Add single job support as a first class simple Apache Airavata Execution Key: AIRAVATA-964 URL: https://issues.apache.org/jira/browse/AIRAVATA-964 Project: Airavata Issue Type: Epic Components: Airavata Client, GFac Reporter: Suresh Marru Labels: Architecture Fix For: 0.13 Attachments: Airavata-Single-Job-Execution.png Currently Airavata supports single jobs by wrapping it as a single node task within a workflow. This wrapping is justified if workflow is the predominant use of Airavata and single application execution is a rare usage pattern. As Airavata is getting more usage, the simple execution but for large number of invocations and diverse applications is getting more widely used. Providing a first class way of a simple application execution will reduce the overhead in creating and managing workflows. But this takes away all the orchestration capabilities provided by the Workflow Interpreter. This Epic is to discuss a new component to Airavata which provides based job orchestration while persisting the request state to registry so the application management component (GFac) can be stateless and recover the job from a frequently checkpointed state from the registry -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (AIRAVATA-989) Clone a created experiment in Orchestrator to launch on different host
[ https://issues.apache.org/jira/browse/AIRAVATA-989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Gunathilake resolved AIRAVATA-989. - Resolution: Fixed This is part of the API and its supported. So closing this issue. Clone a created experiment in Orchestrator to launch on different host -- Key: AIRAVATA-989 URL: https://issues.apache.org/jira/browse/AIRAVATA-989 Project: Airavata Issue Type: Sub-task Components: Airavata Orchestrator Affects Versions: 0.11 Reporter: Raminderjeet Singh Assignee: Lahiru Gunathilake Fix For: 0.13 User is allowed to clone existing jobs and change host description if needed. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (AIRAVATA-964) Add single job support as a first class simple Apache Airavata Execution
[ https://issues.apache.org/jira/browse/AIRAVATA-964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Gunathilake resolved AIRAVATA-964. - Resolution: Fixed Resovling the parent issue since all the child issues are fixed. Add single job support as a first class simple Apache Airavata Execution Key: AIRAVATA-964 URL: https://issues.apache.org/jira/browse/AIRAVATA-964 Project: Airavata Issue Type: Epic Components: Airavata Client, GFac Reporter: Suresh Marru Labels: Architecture Fix For: 0.13 Attachments: Airavata-Single-Job-Execution.png Currently Airavata supports single jobs by wrapping it as a single node task within a workflow. This wrapping is justified if workflow is the predominant use of Airavata and single application execution is a rare usage pattern. As Airavata is getting more usage, the simple execution but for large number of invocations and diverse applications is getting more widely used. Providing a first class way of a simple application execution will reduce the overhead in creating and managing workflows. But this takes away all the orchestration capabilities provided by the Workflow Interpreter. This Epic is to discuss a new component to Airavata which provides based job orchestration while persisting the request state to registry so the application management component (GFac) can be stateless and recover the job from a frequently checkpointed state from the registry -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (AIRAVATA-1053) Update Integration-test module
[ https://issues.apache.org/jira/browse/AIRAVATA-1053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13955315#comment-13955315 ] Marlon Pierce commented on AIRAVATA-1053: - This should be a Story, not a Bug. Update Integration-test module -- Key: AIRAVATA-1053 URL: https://issues.apache.org/jira/browse/AIRAVATA-1053 Project: Airavata Issue Type: Bug Reporter: Saminda Wijeratne Fix For: 0.13 Current integration test module focuses on deploying Airavata on a tomcat server and testing workflow executions against that server. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Reopened] (AIRAVATA-964) Add single job support as a first class simple Apache Airavata Execution
[ https://issues.apache.org/jira/browse/AIRAVATA-964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Gunathilake reopened AIRAVATA-964: - Add single job support as a first class simple Apache Airavata Execution Key: AIRAVATA-964 URL: https://issues.apache.org/jira/browse/AIRAVATA-964 Project: Airavata Issue Type: Epic Components: Airavata Client, GFac Reporter: Suresh Marru Labels: Architecture Fix For: 0.12 Attachments: Airavata-Single-Job-Execution.png Currently Airavata supports single jobs by wrapping it as a single node task within a workflow. This wrapping is justified if workflow is the predominant use of Airavata and single application execution is a rare usage pattern. As Airavata is getting more usage, the simple execution but for large number of invocations and diverse applications is getting more widely used. Providing a first class way of a simple application execution will reduce the overhead in creating and managing workflows. But this takes away all the orchestration capabilities provided by the Workflow Interpreter. This Epic is to discuss a new component to Airavata which provides based job orchestration while persisting the request state to registry so the application management component (GFac) can be stateless and recover the job from a frequently checkpointed state from the registry -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (AIRAVATA-1053) Update Integration-test module
[ https://issues.apache.org/jira/browse/AIRAVATA-1053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saminda Wijeratne updated AIRAVATA-1053: Issue Type: Story (was: Bug) Update Integration-test module -- Key: AIRAVATA-1053 URL: https://issues.apache.org/jira/browse/AIRAVATA-1053 Project: Airavata Issue Type: Story Reporter: Saminda Wijeratne Fix For: 0.13 Current integration test module focuses on deploying Airavata on a tomcat server and testing workflow executions against that server. -- This message was sent by Atlassian JIRA (v6.2#6252)
Re: Cleaning up unused modules before the 0.12 release
+1 for deleting the Rest module. Generally I'm inclined towards keeping the other modules since they'll be needed in future and if we remove them now and add them later they will loose their commit history. That being said, we sort of did that already when we moved to git recently. Thus this could be one rare situation deleting at this point is justified? On Mon, Mar 31, 2014 at 10:22 AM, Suresh Marru sma...@apache.org wrote: Lahiru, I see two parts of this cleanup. The modules we will integrate back in the near future and the ones we will deprecate for good. I vote for deleting the ones like the registry rest modules and keep the ones like xbaya, interpreter and ws-messenger. Suresh On Mar 31, 2014, at 10:10 AM, Lahiru Gunathilake glah...@gmail.com wrote: Hi All, In 0.12 release we are not using following modules and what is our plan on these modules. Are we going to ship this sources with 0.12 release ? modules/xbaya modules/workflow-interpreter modules/ws-messenger/client modules/ws-messenger/commons modules/ws-messenger/distribution modules/ws-messenger/message-monitor modules/ws-messenger/messagebox modules/ws-messenger/messagebroker modules/ws-messenger/samples modules/rest/client modules/rest/mapping modules/rest/service modules/rest/webapp I think we should not ship these unused code in the release. Either we have to fix the trunk by moving these code to sandbox or to another branch or we have to branch 0.12 without these modules and make airavata compile and work and then release 0.12. WDYT ? Regards Lahiru -- System Analyst Programmer PTI Lab Indiana University
Re: Features for Airavata 0.12 release
Hi All, I volunteered to be the RM for 0.12 release and have been doing a bad job in pro-actively calling for a release time line. Given that this release is focusing on major re-architcture triggered by Thrift Migration, how about take a one-time exception and defer the release until little more time? In the past few months we have been simplifying the architecture quite a bit by introducing CPI’s and using thrift for API’s. The side effect was the delay but hoping this is all in a progressive direction towards 1.0. Concretely, my suggestion is for us to re-define release features and then plan the release. Any one have objection on deferring the release until we make a more cohesive features and also robust already added features with more integration tests? One outstanding feature I see missing is the application catalog. I will start on drafting the thrift models and start the discussions on it. Suresh On Jan 21, 2014, at 12:30 PM, Suresh Marru sma...@apache.org wrote: 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 kamalas...@gmail.com 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 sma...@apache.org 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 kamalas...@gmail.com 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
[jira] [Created] (AIRAVATA-1093) CIPRES Integration Test - Create/Update and Save Task
Saminda Wijeratne created AIRAVATA-1093: --- Summary: CIPRES Integration Test - Create/Update and Save Task Key: AIRAVATA-1093 URL: https://issues.apache.org/jira/browse/AIRAVATA-1093 Project: Airavata Issue Type: Story Reporter: Saminda Wijeratne Priority: Trivial Creating integration tests based on real use cases This JIRA will handle testing all the thrift client API functions relating to managing a Experiment equivalent of an Task in CIPRES gateway. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (AIRAVATA-1094) CIPRES Integration Test - Create Experiment
Saminda Wijeratne created AIRAVATA-1094: --- Summary: CIPRES Integration Test - Create Experiment Key: AIRAVATA-1094 URL: https://issues.apache.org/jira/browse/AIRAVATA-1094 Project: Airavata Issue Type: Sub-task Reporter: Saminda Wijeratne Priority: Trivial Create and modify an Experiment object in Airavata based on what a CIPRES user and the gateway would provide for a new Task. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (AIRAVATA-1094) CIPRES Integration Test 1 - Create Experiment
[ https://issues.apache.org/jira/browse/AIRAVATA-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saminda Wijeratne updated AIRAVATA-1094: Summary: CIPRES Integration Test 1 - Create Experiment (was: CIPRES Integration Test - Create Experiment) CIPRES Integration Test 1 - Create Experiment - Key: AIRAVATA-1094 URL: https://issues.apache.org/jira/browse/AIRAVATA-1094 Project: Airavata Issue Type: Sub-task Reporter: Saminda Wijeratne Priority: Trivial Create and modify an Experiment object in Airavata based on what a CIPRES user and the gateway would provide for a new Task. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (AIRAVATA-1095) CIPRES Integration Test 1 - Modify Experiment
Saminda Wijeratne created AIRAVATA-1095: --- Summary: CIPRES Integration Test 1 - Modify Experiment Key: AIRAVATA-1095 URL: https://issues.apache.org/jira/browse/AIRAVATA-1095 Project: Airavata Issue Type: Sub-task Reporter: Saminda Wijeratne Priority: Trivial Modify an already existing launched Experiment object (which was not launched) in Airavata based on what a CIPRES user and the gateway would provide for an existing Task (which was not launched). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (AIRAVATA-1093) CIPRES Integration Test 1 - Manage Unlaunched Experiments
[ https://issues.apache.org/jira/browse/AIRAVATA-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saminda Wijeratne updated AIRAVATA-1093: Summary: CIPRES Integration Test 1 - Manage Unlaunched Experiments (was: CIPRES Integration Test 1 - Create/Update and Save Task) CIPRES Integration Test 1 - Manage Unlaunched Experiments - Key: AIRAVATA-1093 URL: https://issues.apache.org/jira/browse/AIRAVATA-1093 Project: Airavata Issue Type: Story Reporter: Saminda Wijeratne Priority: Trivial Creating integration tests based on real use cases This JIRA will handle testing all the thrift client API functions relating to managing a Experiment equivalent of an Task in CIPRES gateway. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (AIRAVATA-1097) CIPRES Integration Test 1 - Delete Experiment
Saminda Wijeratne created AIRAVATA-1097: --- Summary: CIPRES Integration Test 1 - Delete Experiment Key: AIRAVATA-1097 URL: https://issues.apache.org/jira/browse/AIRAVATA-1097 Project: Airavata Issue Type: Sub-task Reporter: Saminda Wijeratne Priority: Trivial Delete an unlaunched experiment from Airavata -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (AIRAVATA-1093) CIPRES Integration Test 1 - Manage Unlaunched Experiments
[ https://issues.apache.org/jira/browse/AIRAVATA-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saminda Wijeratne updated AIRAVATA-1093: Description: Creating integration tests based on real use cases This JIRA will handle testing all the thrift client API functions relating to managing an unlaunched Experiment equivalent of an Task in CIPRES gateway. was: Creating integration tests based on real use cases This JIRA will handle testing all the thrift client API functions relating to managing a Experiment equivalent of an Task in CIPRES gateway. CIPRES Integration Test 1 - Manage Unlaunched Experiments - Key: AIRAVATA-1093 URL: https://issues.apache.org/jira/browse/AIRAVATA-1093 Project: Airavata Issue Type: Story Reporter: Saminda Wijeratne Priority: Trivial Creating integration tests based on real use cases This JIRA will handle testing all the thrift client API functions relating to managing an unlaunched Experiment equivalent of an Task in CIPRES gateway. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (AIRAVATA-1098) CIPRES Integration Test 2 - Manage Launched Experiments
Saminda Wijeratne created AIRAVATA-1098: --- Summary: CIPRES Integration Test 2 - Manage Launched Experiments Key: AIRAVATA-1098 URL: https://issues.apache.org/jira/browse/AIRAVATA-1098 Project: Airavata Issue Type: Story Environment: Creating integration tests based on real use cases This JIRA will handle testing all the thrift client API functions relating to usecase of handling the experiment lifecycle equivalent to CIPRES usecase of handling Run Task gateway user request. Reporter: Saminda Wijeratne Priority: Trivial -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (AIRAVATA-1099) CIPRES Integration Test 2 - List Unlaunched Experiments
Saminda Wijeratne created AIRAVATA-1099: --- Summary: CIPRES Integration Test 2 - List Unlaunched Experiments Key: AIRAVATA-1099 URL: https://issues.apache.org/jira/browse/AIRAVATA-1099 Project: Airavata Issue Type: Sub-task Reporter: Saminda Wijeratne Priority: Trivial List set of experiment which hasn't being launched yet which belongs to the gateway user. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (AIRAVATA-1099) CIPRES Integration Test 2 - List Experiments
[ https://issues.apache.org/jira/browse/AIRAVATA-1099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saminda Wijeratne updated AIRAVATA-1099: Summary: CIPRES Integration Test 2 - List Experiments (was: CIPRES Integration Test 2 - List Unlaunched Experiments) CIPRES Integration Test 2 - List Experiments Key: AIRAVATA-1099 URL: https://issues.apache.org/jira/browse/AIRAVATA-1099 Project: Airavata Issue Type: Sub-task Reporter: Saminda Wijeratne Priority: Trivial List set of experiment which hasn't being launched yet which belongs to the gateway user. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (AIRAVATA-1100) CIPRES Integration Test 2 - Launch Experiment
Saminda Wijeratne created AIRAVATA-1100: --- Summary: CIPRES Integration Test 2 - Launch Experiment Key: AIRAVATA-1100 URL: https://issues.apache.org/jira/browse/AIRAVATA-1100 Project: Airavata Issue Type: Sub-task Reporter: Saminda Wijeratne Priority: Trivial Launch an unlaunched experiment in Airavata -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (AIRAVATA-1101) CIPRES Integration Test 2 - Monitor Experiment
Saminda Wijeratne created AIRAVATA-1101: --- Summary: CIPRES Integration Test 2 - Monitor Experiment Key: AIRAVATA-1101 URL: https://issues.apache.org/jira/browse/AIRAVATA-1101 Project: Airavata Issue Type: Sub-task Reporter: Saminda Wijeratne Priority: Trivial Monitor experiment life cycle progress and experiment metadata. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (AIRAVATA-1102) CIPRES Integration Test 2 - List Experiment Intermediate Results
Saminda Wijeratne created AIRAVATA-1102: --- Summary: CIPRES Integration Test 2 - List Experiment Intermediate Results Key: AIRAVATA-1102 URL: https://issues.apache.org/jira/browse/AIRAVATA-1102 Project: Airavata Issue Type: Sub-task Reporter: Saminda Wijeratne Should be able to list what intermediate results are available through the current execution of the experiment. This would include file/directories created in the working directory of the remote job in the remote host and stdout and stderr content. (This wont include the workflow execution scenario since CIPRES does not have that use case yet) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (AIRAVATA-1102) CIPRES Integration Test 2 - List Experiment Intermediate Results
[ https://issues.apache.org/jira/browse/AIRAVATA-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saminda Wijeratne updated AIRAVATA-1102: Description: Should be able to list what intermediate results are available through the current execution of the experiment. This would include file/directories created in the working directory of the remote job in the remote host, stdout and stderr content and possibly metadata relating to intermediate results (eg: size and/or modified time of a file). (This wont include the workflow execution scenario since CIPRES does not have that use case yet) was: Should be able to list what intermediate results are available through the current execution of the experiment. This would include file/directories created in the working directory of the remote job in the remote host and stdout and stderr content. (This wont include the workflow execution scenario since CIPRES does not have that use case yet) CIPRES Integration Test 2 - List Experiment Intermediate Results Key: AIRAVATA-1102 URL: https://issues.apache.org/jira/browse/AIRAVATA-1102 Project: Airavata Issue Type: Sub-task Reporter: Saminda Wijeratne Should be able to list what intermediate results are available through the current execution of the experiment. This would include file/directories created in the working directory of the remote job in the remote host, stdout and stderr content and possibly metadata relating to intermediate results (eg: size and/or modified time of a file). (This wont include the workflow execution scenario since CIPRES does not have that use case yet) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (AIRAVATA-1103) CIPRES Integration Test 2 - Download Experiment Intermediate Results
Saminda Wijeratne created AIRAVATA-1103: --- Summary: CIPRES Integration Test 2 - Download Experiment Intermediate Results Key: AIRAVATA-1103 URL: https://issues.apache.org/jira/browse/AIRAVATA-1103 Project: Airavata Issue Type: Sub-task Reporter: Saminda Wijeratne Priority: Trivial Retrieve intermediate results of an experiment. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (AIRAVATA-1104) CIPRES Integration Test 2 - Notification when Experiment Completes/Fails
Saminda Wijeratne created AIRAVATA-1104: --- Summary: CIPRES Integration Test 2 - Notification when Experiment Completes/Fails Key: AIRAVATA-1104 URL: https://issues.apache.org/jira/browse/AIRAVATA-1104 Project: Airavata Issue Type: Sub-task Reporter: Saminda Wijeratne Register for status changes of an experiment. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (AIRAVATA-1106) CIPRES Integration Test 2 - Download final results
Saminda Wijeratne created AIRAVATA-1106: --- Summary: CIPRES Integration Test 2 - Download final results Key: AIRAVATA-1106 URL: https://issues.apache.org/jira/browse/AIRAVATA-1106 Project: Airavata Issue Type: Sub-task Reporter: Saminda Wijeratne Stream the downloaded results. This could be to the portal server or any other machine. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (AIRAVATA-1107) CIPRES Integration Test 2 - View Experiment Errors
Saminda Wijeratne created AIRAVATA-1107: --- Summary: CIPRES Integration Test 2 - View Experiment Errors Key: AIRAVATA-1107 URL: https://issues.apache.org/jira/browse/AIRAVATA-1107 Project: Airavata Issue Type: Sub-task Reporter: Saminda Wijeratne Incase if the experiments end up in error, the gateway should be able to query the errors relating to the experiment. The errors should be comprehensive enough for the gateway user or gateway admin or gateway developer to take manual steps to fix it or program against the error to resolve or send relevant notifications. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (AIRAVATA-1098) CIPRES Integration Test 2 - Manage Launched Experiments
[ https://issues.apache.org/jira/browse/AIRAVATA-1098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saminda Wijeratne updated AIRAVATA-1098: Description: Creating integration tests based on real use cases This JIRA will handle testing all the thrift client API functions relating to usecase of handling the experiment lifecycle equivalent to CIPRES usecase of handling Run Task gateway user request. CIPRES Integration Test 2 - Manage Launched Experiments --- Key: AIRAVATA-1098 URL: https://issues.apache.org/jira/browse/AIRAVATA-1098 Project: Airavata Issue Type: Story Reporter: Saminda Wijeratne Priority: Trivial Creating integration tests based on real use cases This JIRA will handle testing all the thrift client API functions relating to usecase of handling the experiment lifecycle equivalent to CIPRES usecase of handling Run Task gateway user request. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (AIRAVATA-1106) CIPRES Integration Test 2 - Download Experiment Final Results
[ https://issues.apache.org/jira/browse/AIRAVATA-1106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saminda Wijeratne updated AIRAVATA-1106: Summary: CIPRES Integration Test 2 - Download Experiment Final Results (was: CIPRES Integration Test 2 - Download final results) CIPRES Integration Test 2 - Download Experiment Final Results - Key: AIRAVATA-1106 URL: https://issues.apache.org/jira/browse/AIRAVATA-1106 Project: Airavata Issue Type: Sub-task Reporter: Saminda Wijeratne Stream the downloaded results. This could be to the portal server or any other machine. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (AIRAVATA-1111) CLONE - CIPRES Integration Test 2 - Monitor Experiment
Raminderjeet Singh created AIRAVATA-: Summary: CLONE - CIPRES Integration Test 2 - Monitor Experiment Key: AIRAVATA- URL: https://issues.apache.org/jira/browse/AIRAVATA- Project: Airavata Issue Type: Sub-task Reporter: Raminderjeet Singh Priority: Trivial Monitor experiment life cycle progress and experiment metadata. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (AIRAVATA-1117) CLONE - CIPRES Integration Test 2 - View Experiment Errors
Raminderjeet Singh created AIRAVATA-1117: Summary: CLONE - CIPRES Integration Test 2 - View Experiment Errors Key: AIRAVATA-1117 URL: https://issues.apache.org/jira/browse/AIRAVATA-1117 Project: Airavata Issue Type: Sub-task Reporter: Raminderjeet Singh Incase if the experiments end up in error, the gateway should be able to query the errors relating to the experiment. The errors should be comprehensive enough for the gateway user or gateway admin or gateway developer to take manual steps to fix it or program against the error to resolve or send relevant notifications. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (AIRAVATA-1114) CLONE - CIPRES Integration Test 2 - Notification when Experiment Completes/Fails
Raminderjeet Singh created AIRAVATA-1114: Summary: CLONE - CIPRES Integration Test 2 - Notification when Experiment Completes/Fails Key: AIRAVATA-1114 URL: https://issues.apache.org/jira/browse/AIRAVATA-1114 Project: Airavata Issue Type: Sub-task Reporter: Raminderjeet Singh Register for status changes of an experiment. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (AIRAVATA-1113) CLONE - CIPRES Integration Test 2 - Download Experiment Intermediate Results
Raminderjeet Singh created AIRAVATA-1113: Summary: CLONE - CIPRES Integration Test 2 - Download Experiment Intermediate Results Key: AIRAVATA-1113 URL: https://issues.apache.org/jira/browse/AIRAVATA-1113 Project: Airavata Issue Type: Sub-task Reporter: Raminderjeet Singh Priority: Trivial Retrieve intermediate results of an experiment. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (AIRAVATA-1110) CLONE - CIPRES Integration Test 2 - Launch Experiment
Raminderjeet Singh created AIRAVATA-1110: Summary: CLONE - CIPRES Integration Test 2 - Launch Experiment Key: AIRAVATA-1110 URL: https://issues.apache.org/jira/browse/AIRAVATA-1110 Project: Airavata Issue Type: Sub-task Reporter: Raminderjeet Singh Priority: Trivial Launch an unlaunched experiment in Airavata -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (AIRAVATA-1112) CLONE - CIPRES Integration Test 2 - List Experiment Intermediate Results
Raminderjeet Singh created AIRAVATA-1112: Summary: CLONE - CIPRES Integration Test 2 - List Experiment Intermediate Results Key: AIRAVATA-1112 URL: https://issues.apache.org/jira/browse/AIRAVATA-1112 Project: Airavata Issue Type: Sub-task Reporter: Raminderjeet Singh Should be able to list what intermediate results are available through the current execution of the experiment. This would include file/directories created in the working directory of the remote job in the remote host, stdout and stderr content and possibly metadata relating to intermediate results (eg: size and/or modified time of a file). (This wont include the workflow execution scenario since CIPRES does not have that use case yet) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (AIRAVATA-1116) CLONE - CIPRES Integration Test 2 - Download Experiment Final Results
Raminderjeet Singh created AIRAVATA-1116: Summary: CLONE - CIPRES Integration Test 2 - Download Experiment Final Results Key: AIRAVATA-1116 URL: https://issues.apache.org/jira/browse/AIRAVATA-1116 Project: Airavata Issue Type: Sub-task Reporter: Raminderjeet Singh Stream the downloaded results. This could be to the portal server or any other machine. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (AIRAVATA-1109) CLONE - CIPRES Integration Test 2 - List Experiments
Raminderjeet Singh created AIRAVATA-1109: Summary: CLONE - CIPRES Integration Test 2 - List Experiments Key: AIRAVATA-1109 URL: https://issues.apache.org/jira/browse/AIRAVATA-1109 Project: Airavata Issue Type: Sub-task Reporter: Raminderjeet Singh Priority: Trivial List set of experiment which belongs to the gateway user. Should be able to list Experiment by its state (Unlaunched/Launched/Completed/etc.) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (AIRAVATA-1108) Ultrascan Integration Test - Manage Launched Experiments
Raminderjeet Singh created AIRAVATA-1108: Summary: Ultrascan Integration Test - Manage Launched Experiments Key: AIRAVATA-1108 URL: https://issues.apache.org/jira/browse/AIRAVATA-1108 Project: Airavata Issue Type: Story Reporter: Raminderjeet Singh Priority: Trivial Creating integration tests based on real use cases This JIRA will handle testing all the thrift client API functions relating to usecase of handling the experiment lifecycle equivalent to CIPRES usecase of handling Run Task gateway user request. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (AIRAVATA-1109) Ultrascan Integration Test - List Experiments
[ https://issues.apache.org/jira/browse/AIRAVATA-1109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raminderjeet Singh updated AIRAVATA-1109: - Summary: Ultrascan Integration Test - List Experiments (was: CLONE - CIPRES Integration Test 2 - List Experiments) Ultrascan Integration Test - List Experiments -- Key: AIRAVATA-1109 URL: https://issues.apache.org/jira/browse/AIRAVATA-1109 Project: Airavata Issue Type: Sub-task Reporter: Raminderjeet Singh Priority: Trivial List set of experiment which belongs to the gateway user. Should be able to list Experiment by its state (Unlaunched/Launched/Completed/etc.) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (AIRAVATA-1112) Ultrascan Integration Test - List Experiment Intermediate Results
[ https://issues.apache.org/jira/browse/AIRAVATA-1112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raminderjeet Singh updated AIRAVATA-1112: - Summary: Ultrascan Integration Test - List Experiment Intermediate Results (was: CLONE - CIPRES Integration Test 2 - List Experiment Intermediate Results) Ultrascan Integration Test - List Experiment Intermediate Results -- Key: AIRAVATA-1112 URL: https://issues.apache.org/jira/browse/AIRAVATA-1112 Project: Airavata Issue Type: Sub-task Reporter: Raminderjeet Singh Should be able to list what intermediate results are available through the current execution of the experiment. This would include file/directories created in the working directory of the remote job in the remote host, stdout and stderr content and possibly metadata relating to intermediate results (eg: size and/or modified time of a file). (This wont include the workflow execution scenario since CIPRES does not have that use case yet) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (AIRAVATA-1111) Ultrascan Integration Test - Monitor Experiment
[ https://issues.apache.org/jira/browse/AIRAVATA-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raminderjeet Singh updated AIRAVATA-: - Summary: Ultrascan Integration Test - Monitor Experiment (was: CLONE - CIPRES Integration Test 2 - Monitor Experiment) Ultrascan Integration Test - Monitor Experiment Key: AIRAVATA- URL: https://issues.apache.org/jira/browse/AIRAVATA- Project: Airavata Issue Type: Sub-task Reporter: Raminderjeet Singh Priority: Trivial Monitor experiment life cycle progress and experiment metadata. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (AIRAVATA-1110) Ultrascan Integration Test - Launch Experiment
[ https://issues.apache.org/jira/browse/AIRAVATA-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raminderjeet Singh updated AIRAVATA-1110: - Summary: Ultrascan Integration Test - Launch Experiment (was: CLONE - CIPRES Integration Test 2 - Launch Experiment) Ultrascan Integration Test - Launch Experiment --- Key: AIRAVATA-1110 URL: https://issues.apache.org/jira/browse/AIRAVATA-1110 Project: Airavata Issue Type: Sub-task Reporter: Raminderjeet Singh Priority: Trivial Launch an unlaunched experiment in Airavata -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (AIRAVATA-1114) Ultrascan Integration Test - Notification when Experiment Completes/Fails
[ https://issues.apache.org/jira/browse/AIRAVATA-1114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raminderjeet Singh updated AIRAVATA-1114: - Summary: Ultrascan Integration Test - Notification when Experiment Completes/Fails (was: CLONE - CIPRES Integration Test 2 - Notification when Experiment Completes/Fails) Ultrascan Integration Test - Notification when Experiment Completes/Fails -- Key: AIRAVATA-1114 URL: https://issues.apache.org/jira/browse/AIRAVATA-1114 Project: Airavata Issue Type: Sub-task Reporter: Raminderjeet Singh Register for status changes of an experiment. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (AIRAVATA-1115) Ultrascan Integration Test - Notifications when Results available for Download
[ https://issues.apache.org/jira/browse/AIRAVATA-1115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raminderjeet Singh updated AIRAVATA-1115: - Summary: Ultrascan Integration Test - Notifications when Results available for Download (was: CLONE - CIPRES Integration Test 2 - Notifications when Results available for Download) Ultrascan Integration Test - Notifications when Results available for Download --- Key: AIRAVATA-1115 URL: https://issues.apache.org/jira/browse/AIRAVATA-1115 Project: Airavata Issue Type: Sub-task Reporter: Raminderjeet Singh Priority: Trivial Could be as same as AIRAVATA-1097 if we are keeping a status for results being downloaded to a per-determined location and we introduce another value to the status enum of the experiment. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (AIRAVATA-1116) Ultrascan Integration Test - Download Experiment Final Results
[ https://issues.apache.org/jira/browse/AIRAVATA-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raminderjeet Singh updated AIRAVATA-1116: - Summary: Ultrascan Integration Test - Download Experiment Final Results (was: CLONE - CIPRES Integration Test 2 - Download Experiment Final Results) Ultrascan Integration Test - Download Experiment Final Results --- Key: AIRAVATA-1116 URL: https://issues.apache.org/jira/browse/AIRAVATA-1116 Project: Airavata Issue Type: Sub-task Reporter: Raminderjeet Singh Stream the downloaded results. This could be to the portal server or any other machine. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (AIRAVATA-1108) Ultrascan Integration Test - Manage Launched Experiments
[ https://issues.apache.org/jira/browse/AIRAVATA-1108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raminderjeet Singh updated AIRAVATA-1108: - Description: Creating integration tests based on real use cases This JIRA will handle testing all the thrift client API functions relating to usecase of handling the experiment lifecycle equivalent to Ultrascan usecase of handling Run Task gateway user request. was: Creating integration tests based on real use cases This JIRA will handle testing all the thrift client API functions relating to usecase of handling the experiment lifecycle equivalent to CIPRES usecase of handling Run Task gateway user request. Ultrascan Integration Test - Manage Launched Experiments Key: AIRAVATA-1108 URL: https://issues.apache.org/jira/browse/AIRAVATA-1108 Project: Airavata Issue Type: Story Reporter: Raminderjeet Singh Priority: Trivial Creating integration tests based on real use cases This JIRA will handle testing all the thrift client API functions relating to usecase of handling the experiment lifecycle equivalent to Ultrascan usecase of handling Run Task gateway user request. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (AIRAVATA-1117) Ultrascan Integration Test - View Experiment Errors
[ https://issues.apache.org/jira/browse/AIRAVATA-1117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raminderjeet Singh updated AIRAVATA-1117: - Summary: Ultrascan Integration Test - View Experiment Errors (was: CLONE - CIPRES Integration Test 2 - View Experiment Errors) Ultrascan Integration Test - View Experiment Errors Key: AIRAVATA-1117 URL: https://issues.apache.org/jira/browse/AIRAVATA-1117 Project: Airavata Issue Type: Sub-task Reporter: Raminderjeet Singh Incase if the experiments end up in error, the gateway should be able to query the errors relating to the experiment. The errors should be comprehensive enough for the gateway user or gateway admin or gateway developer to take manual steps to fix it or program against the error to resolve or send relevant notifications. -- This message was sent by Atlassian JIRA (v6.2#6252)
Submitting patches now that we use Git
The website still references the SVN procedure (http://airavata.apache.org/community/submit-patch.html). Should we recommend that contributors just do a pull request through GitHub? Marlon
[jira] [Updated] (AIRAVATA-1055) Update integration tests defined in the integration-test module
[ https://issues.apache.org/jira/browse/AIRAVATA-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sachith Withana updated AIRAVATA-1055: -- Attachment: (was: 0001-Integration-tests-added-for-Single-Application-Testi.patch) Update integration tests defined in the integration-test module --- Key: AIRAVATA-1055 URL: https://issues.apache.org/jira/browse/AIRAVATA-1055 Project: Airavata Issue Type: Sub-task Reporter: Saminda Wijeratne Assignee: Sachith Withana Fix For: 0.12 Current integration tests include workflow executions which are not supported in the new Airavata Server Architecture. They need to be disabled for the time-being and have new integration tests created for single application execution through the AiravataThriftAPI -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (AIRAVATA-1055) Update integration tests defined in the integration-test module
[ https://issues.apache.org/jira/browse/AIRAVATA-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sachith Withana updated AIRAVATA-1055: -- Attachment: 0001-Integration-tests-for-single-app-submission-added-se.patch +Single App submission integration tests added for localhost simple echo application +SingleAppIntegrationTestBase +fixed the sure-fire plugin running integration tests +checkServerStartup for thrift Update integration tests defined in the integration-test module --- Key: AIRAVATA-1055 URL: https://issues.apache.org/jira/browse/AIRAVATA-1055 Project: Airavata Issue Type: Sub-task Reporter: Saminda Wijeratne Assignee: Sachith Withana Fix For: 0.12 Attachments: 0001-Integration-tests-for-single-app-submission-added-se.patch Current integration tests include workflow executions which are not supported in the new Airavata Server Architecture. They need to be disabled for the time-being and have new integration tests created for single application execution through the AiravataThriftAPI -- This message was sent by Atlassian JIRA (v6.2#6252)
Re: Submitting patches now that we use Git
Definitely should update that site with the relevant git commands... Its not obvious for a user who's not familiar with git to know which commands to use. Some of the commands which I found useful when working with patches are, #update current copy git pull #view changes in the code git diff #add a commit on the current changes in the local repo git commit #create patches out of local commits in the local repo - never had to use this one though git format-patch HEAD #check to see the patch can be applied without errors git apply --check patch file #apply the patch git apply patch file #how to resolve after fixing the conflicts git rm or git add #revert a single file/folder git checkout #revert the whole repo git reset --hard HEAD On Mon, Mar 31, 2014 at 3:32 PM, Marlon Pierce marpi...@iu.edu wrote: The website still references the SVN procedure (http://airavata.apache.org/community/submit-patch.html). Should we recommend that contributors just do a pull request through GitHub? Marlon
[jira] [Commented] (AIRAVATA-762) Advanced Job scripts based on job manager type
[ https://issues.apache.org/jira/browse/AIRAVATA-762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13955712#comment-13955712 ] ASF subversion and git services commented on AIRAVATA-762: -- Commit b57c333b26f85d1b00586a314a1985168cb5ffea in airavata's branch refs/heads/master from lahiru [ https://git-wip-us.apache.org/repos/asf?p=airavata.git;h=b57c333 ] adding xslt to the build system, AIRAVATA-762 Advanced Job scripts based on job manager type -- Key: AIRAVATA-762 URL: https://issues.apache.org/jira/browse/AIRAVATA-762 Project: Airavata Issue Type: Sub-task Components: GFac Affects Versions: 0.7 Reporter: Raminderjeet Singh Assignee: Lahiru Gunathilake Fix For: 0.12 Job manager like PBS/SGE/SLURM have different format of job script. Create a util method to create scripts for different format. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (AIRAVATA-762) Advanced Job scripts based on job manager type
[ https://issues.apache.org/jira/browse/AIRAVATA-762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Gunathilake resolved AIRAVATA-762. - Resolution: Fixed Added initial support for SGE. Advanced Job scripts based on job manager type -- Key: AIRAVATA-762 URL: https://issues.apache.org/jira/browse/AIRAVATA-762 Project: Airavata Issue Type: Sub-task Components: GFac Affects Versions: 0.7 Reporter: Raminderjeet Singh Assignee: Lahiru Gunathilake Fix For: 0.12 Job manager like PBS/SGE/SLURM have different format of job script. Create a util method to create scripts for different format. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (AIRAVATA-762) Advanced Job scripts based on job manager type
[ https://issues.apache.org/jira/browse/AIRAVATA-762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Gunathilake closed AIRAVATA-762. --- Advanced Job scripts based on job manager type -- Key: AIRAVATA-762 URL: https://issues.apache.org/jira/browse/AIRAVATA-762 Project: Airavata Issue Type: Sub-task Components: GFac Affects Versions: 0.7 Reporter: Raminderjeet Singh Assignee: Lahiru Gunathilake Fix For: 0.12 Job manager like PBS/SGE/SLURM have different format of job script. Create a util method to create scripts for different format. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (AIRAVATA-759) GSISSH-Grid security provider to run remote jobs
[ https://issues.apache.org/jira/browse/AIRAVATA-759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Gunathilake resolved AIRAVATA-759. - Resolution: Fixed Fixed all the child issues so resolving the parent issue. GSISSH-Grid security provider to run remote jobs Key: AIRAVATA-759 URL: https://issues.apache.org/jira/browse/AIRAVATA-759 Project: Airavata Issue Type: Epic Components: GFac Affects Versions: 0.10 Reporter: Raminderjeet Singh Assignee: Raminderjeet Singh Fix For: 0.12 Provider will help users to run/monitor batch jobs using grid security. Grid machines can have different job managers like PBS/SGE/SLURM so we need to create job scripts based on type of job manager. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (AIRAVATA-759) GSISSH-Grid security provider to run remote jobs
[ https://issues.apache.org/jira/browse/AIRAVATA-759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Gunathilake closed AIRAVATA-759. --- GSISSH-Grid security provider to run remote jobs Key: AIRAVATA-759 URL: https://issues.apache.org/jira/browse/AIRAVATA-759 Project: Airavata Issue Type: Epic Components: GFac Affects Versions: 0.10 Reporter: Raminderjeet Singh Assignee: Raminderjeet Singh Fix For: 0.12 Provider will help users to run/monitor batch jobs using grid security. Grid machines can have different job managers like PBS/SGE/SLURM so we need to create job scripts based on type of job manager. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (AIRAVATA-762) Advanced Job scripts based on job manager type
[ https://issues.apache.org/jira/browse/AIRAVATA-762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13955714#comment-13955714 ] ASF subversion and git services commented on AIRAVATA-762: -- Commit c7a9c8e97209f591b86a3f5e3da07498e5342021 in airavata's branch refs/heads/master from lahiru [ https://git-wip-us.apache.org/repos/asf?p=airavata.git;h=c7a9c8e ] changing the build to get new xslt for SGE,AIRAVATA-762 Advanced Job scripts based on job manager type -- Key: AIRAVATA-762 URL: https://issues.apache.org/jira/browse/AIRAVATA-762 Project: Airavata Issue Type: Sub-task Components: GFac Affects Versions: 0.7 Reporter: Raminderjeet Singh Assignee: Lahiru Gunathilake Fix For: 0.12 Job manager like PBS/SGE/SLURM have different format of job script. Create a util method to create scripts for different format. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (AIRAVATA-1108) Ultrascan Integration Test - Manage Launched Experiments
[ https://issues.apache.org/jira/browse/AIRAVATA-1108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13955844#comment-13955844 ] Suresh Marru commented on AIRAVATA-1108: I think we should not have project specific integration tests. From Airavata perspective, how does this cloned test differ from 1098? Ultrascan Integration Test - Manage Launched Experiments Key: AIRAVATA-1108 URL: https://issues.apache.org/jira/browse/AIRAVATA-1108 Project: Airavata Issue Type: Story Reporter: Raminderjeet Singh Priority: Trivial Creating integration tests based on real use cases This JIRA will handle testing all the thrift client API functions relating to usecase of handling the experiment lifecycle equivalent to Ultrascan usecase of handling Run Task gateway user request. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (AIRAVATA-1093) Integration Test 1 - Manage Unlaunched Experiments
[ https://issues.apache.org/jira/browse/AIRAVATA-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saminda Wijeratne updated AIRAVATA-1093: Summary: Integration Test 1 - Manage Unlaunched Experiments (was: CIPRES Integration Test 1 - Manage Unlaunched Experiments) Integration Test 1 - Manage Unlaunched Experiments -- Key: AIRAVATA-1093 URL: https://issues.apache.org/jira/browse/AIRAVATA-1093 Project: Airavata Issue Type: Story Reporter: Saminda Wijeratne Priority: Trivial Creating integration tests based on real use cases This JIRA will handle testing all the thrift client API functions relating to managing an unlaunched Experiment equivalent of an Task in CIPRES gateway. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (AIRAVATA-1094) Integration Test 1 - Create Experiment
[ https://issues.apache.org/jira/browse/AIRAVATA-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saminda Wijeratne updated AIRAVATA-1094: Description: Create and modify an Experiment object in Airavata based on what a gateway user and the gateway would provide for a new Task. (was: Create and modify an Experiment object in Airavata based on what a CIPRES user and the gateway would provide for a new Task.) Integration Test 1 - Create Experiment -- Key: AIRAVATA-1094 URL: https://issues.apache.org/jira/browse/AIRAVATA-1094 Project: Airavata Issue Type: Sub-task Reporter: Saminda Wijeratne Priority: Trivial Create and modify an Experiment object in Airavata based on what a gateway user and the gateway would provide for a new Task. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (AIRAVATA-1094) Integration Test 1 - Create Experiment
[ https://issues.apache.org/jira/browse/AIRAVATA-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saminda Wijeratne updated AIRAVATA-1094: Summary: Integration Test 1 - Create Experiment (was: CIPRES Integration Test 1 - Create Experiment) Integration Test 1 - Create Experiment -- Key: AIRAVATA-1094 URL: https://issues.apache.org/jira/browse/AIRAVATA-1094 Project: Airavata Issue Type: Sub-task Reporter: Saminda Wijeratne Priority: Trivial Create and modify an Experiment object in Airavata based on what a CIPRES user and the gateway would provide for a new Task. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (AIRAVATA-1097) Integration Test 1 - Delete Experiment
[ https://issues.apache.org/jira/browse/AIRAVATA-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saminda Wijeratne updated AIRAVATA-1097: Summary: Integration Test 1 - Delete Experiment (was: CIPRES Integration Test 1 - Delete Experiment) Integration Test 1 - Delete Experiment -- Key: AIRAVATA-1097 URL: https://issues.apache.org/jira/browse/AIRAVATA-1097 Project: Airavata Issue Type: Sub-task Reporter: Saminda Wijeratne Priority: Trivial Delete an unlaunched experiment from Airavata -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (AIRAVATA-1095) Integration Test 1 - Modify Experiment
[ https://issues.apache.org/jira/browse/AIRAVATA-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saminda Wijeratne updated AIRAVATA-1095: Description: Modify an already existing launched Experiment object (which was not launched) in Airavata based on what a gateway user and the gateway would provide for an existing Task (which was not launched). (was: Modify an already existing launched Experiment object (which was not launched) in Airavata based on what a CIPRES user and the gateway would provide for an existing Task (which was not launched). ) Integration Test 1 - Modify Experiment -- Key: AIRAVATA-1095 URL: https://issues.apache.org/jira/browse/AIRAVATA-1095 Project: Airavata Issue Type: Sub-task Reporter: Saminda Wijeratne Priority: Trivial Modify an already existing launched Experiment object (which was not launched) in Airavata based on what a gateway user and the gateway would provide for an existing Task (which was not launched). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (AIRAVATA-1096) Integration Test 1 - Clone Experiment
[ https://issues.apache.org/jira/browse/AIRAVATA-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saminda Wijeratne updated AIRAVATA-1096: Description: Clone an existing Experiment to create a new Experiment allowing different values for the attributes/properties of the Experiment object based on gateway user or gateway input. (was: Clone an existing Experiment to create a new Experiment allowing different values for the attributes/properties of the Experiment object based on CIPRES user or gateway input.) Integration Test 1 - Clone Experiment - Key: AIRAVATA-1096 URL: https://issues.apache.org/jira/browse/AIRAVATA-1096 Project: Airavata Issue Type: Sub-task Reporter: Saminda Wijeratne Priority: Trivial Clone an existing Experiment to create a new Experiment allowing different values for the attributes/properties of the Experiment object based on gateway user or gateway input. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (AIRAVATA-1095) Integration Test 1 - Modify Experiment
[ https://issues.apache.org/jira/browse/AIRAVATA-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saminda Wijeratne updated AIRAVATA-1095: Summary: Integration Test 1 - Modify Experiment (was: CIPRES Integration Test 1 - Modify Experiment) Integration Test 1 - Modify Experiment -- Key: AIRAVATA-1095 URL: https://issues.apache.org/jira/browse/AIRAVATA-1095 Project: Airavata Issue Type: Sub-task Reporter: Saminda Wijeratne Priority: Trivial Modify an already existing launched Experiment object (which was not launched) in Airavata based on what a CIPRES user and the gateway would provide for an existing Task (which was not launched). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Deleted] (AIRAVATA-1109) Ultrascan Integration Test - List Experiments
[ https://issues.apache.org/jira/browse/AIRAVATA-1109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raminderjeet Singh deleted AIRAVATA-1109: - Ultrascan Integration Test - List Experiments -- Key: AIRAVATA-1109 URL: https://issues.apache.org/jira/browse/AIRAVATA-1109 Project: Airavata Issue Type: Sub-task Reporter: Raminderjeet Singh Priority: Trivial List set of experiment which belongs to the gateway user. Should be able to list Experiment by its state (Unlaunched/Launched/Completed/etc.) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Deleted] (AIRAVATA-1110) Ultrascan Integration Test - Launch Experiment
[ https://issues.apache.org/jira/browse/AIRAVATA-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raminderjeet Singh deleted AIRAVATA-1110: - Ultrascan Integration Test - Launch Experiment --- Key: AIRAVATA-1110 URL: https://issues.apache.org/jira/browse/AIRAVATA-1110 Project: Airavata Issue Type: Sub-task Reporter: Raminderjeet Singh Priority: Trivial Launch an unlaunched experiment in Airavata -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Deleted] (AIRAVATA-1116) Ultrascan Integration Test - Download Experiment Final Results
[ https://issues.apache.org/jira/browse/AIRAVATA-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raminderjeet Singh deleted AIRAVATA-1116: - Ultrascan Integration Test - Download Experiment Final Results --- Key: AIRAVATA-1116 URL: https://issues.apache.org/jira/browse/AIRAVATA-1116 Project: Airavata Issue Type: Sub-task Reporter: Raminderjeet Singh Stream the downloaded results. This could be to the portal server or any other machine. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (AIRAVATA-1099) Integration Test 2 - List Experiments
[ https://issues.apache.org/jira/browse/AIRAVATA-1099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saminda Wijeratne updated AIRAVATA-1099: Summary: Integration Test 2 - List Experiments (was: CIPRES Integration Test 2 - List Experiments) Integration Test 2 - List Experiments - Key: AIRAVATA-1099 URL: https://issues.apache.org/jira/browse/AIRAVATA-1099 Project: Airavata Issue Type: Sub-task Reporter: Saminda Wijeratne Priority: Trivial List set of experiment which belongs to the gateway user. Should be able to list Experiment by its state (Unlaunched/Launched/Completed/etc.) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Deleted] (AIRAVATA-1111) Ultrascan Integration Test - Monitor Experiment
[ https://issues.apache.org/jira/browse/AIRAVATA-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raminderjeet Singh deleted AIRAVATA-: - Ultrascan Integration Test - Monitor Experiment Key: AIRAVATA- URL: https://issues.apache.org/jira/browse/AIRAVATA- Project: Airavata Issue Type: Sub-task Reporter: Raminderjeet Singh Priority: Trivial Monitor experiment life cycle progress and experiment metadata. -- This message was sent by Atlassian JIRA (v6.2#6252)
