[jira] [Updated] (AIRAVATA-1448) Schedule throttle experiments

[ https://issues.apache.org/jira/browse/AIRAVATA-1448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma updated AIRAVATA-1448: Fix Version/s: (was: 0.15 ) 0.16 Schedule throttle experiments

[jira] [Updated] (AIRAVATA-1447) Job restriction per computer resource

[ https://issues.apache.org/jira/browse/AIRAVATA-1447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma updated AIRAVATA-1447: Fix Version/s: (was: 0.15 ) 0.16 Job restriction per computer resource

[jira] [Updated] (AIRAVATA-1426) Handle Job Restriction in Orchestrator Level

[ https://issues.apache.org/jira/browse/AIRAVATA-1426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma updated AIRAVATA-1426: Fix Version/s: (was: 0.15 ) 0.16 Handle Job Restriction in Orchestrator Level

[jira] [Resolved] (AIRAVATA-1314) CANCELED an experiment in state CREATED. Got the message 'Experiment Canceled!' but still it has the status as CREATED.

[ https://issues.apache.org/jira/browse/AIRAVATA-1314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma resolved AIRAVATA-1314. - Resolution: Fixed Cancel is implemented in 0.15 CANCELED an experiment in state CREATED. Got the

[jira] [Resolved] (AIRAVATA-1475) Error creating BESProvider instance from BetterGfacImpl

[ https://issues.apache.org/jira/browse/AIRAVATA-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma resolved AIRAVATA-1475. - Resolution: Fixed Error creating BESProvider instance from BetterGfacImpl

[jira] [Resolved] (AIRAVATA-1476) Integrate Unicore-BES provider with master Airavata

[ https://issues.apache.org/jira/browse/AIRAVATA-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma resolved AIRAVATA-1476. - Resolution: Fixed Integrate Unicore-BES provider with master Airavata

[jira] [Closed] (AIRAVATA-1458) RabbitMQ: java: not found on Lonestar job sometime

[ https://issues.apache.org/jira/browse/AIRAVATA-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma closed AIRAVATA-1458. --- Resolution: Won't Fix We will not be using rabbitMQ monitoring. Currently using email based monitoring

[jira] [Commented] (AIRAVATA-1722) Ability to cancel number of experiments from a pre selected list

[ https://issues.apache.org/jira/browse/AIRAVATA-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14591931#comment-14591931 ] Eroma commented on AIRAVATA-1722: - Bulk cancelation makes more sense and useful for a

[jira] [Updated] (AIRAVATA-1706) Have a Refresh button similar to Experiment Summary page in Project summary page as well.

[ https://issues.apache.org/jira/browse/AIRAVATA-1706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma updated AIRAVATA-1706: Assignee: Supun Chathuranga Nakandala Have a Refresh button similar to Experiment Summary page in

[jira] [Closed] (AIRAVATA-1354) Job monitor for Stampede unknow status

[ https://issues.apache.org/jira/browse/AIRAVATA-1354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma closed AIRAVATA-1354. --- Resolution: Cannot Reproduce Fix Version/s: 0.15 Tested experiments in

[jira] [Closed] (AIRAVATA-1146) Seperate out the Derby Server Startup from the Airavata API Server Startup

[ https://issues.apache.org/jira/browse/AIRAVATA-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma closed AIRAVATA-1146. --- Resolution: Not A Problem Seperate out the Derby Server Startup from the Airavata API Server Startup

[jira] [Updated] (AIRAVATA-1730) Expose input and output variable set for an application as variables

[ https://issues.apache.org/jira/browse/AIRAVATA-1730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma updated AIRAVATA-1730: Fix Version/s: 0.16 Expose input and output variable set for an application as variables

[jira] [Updated] (AIRAVATA-1518) In Compute Resource added data movement protocol 'GridFTP' and when Security protocol is updated and saved new records get created

[ https://issues.apache.org/jira/browse/AIRAVATA-1518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma updated AIRAVATA-1518: Assignee: Supun Chathuranga Nakandala (was: Chathuri Wimalasena) In Compute Resource added data

[jira] [Closed] (AIRAVATA-961) Update API to support Experiment Cancel/Stop, Pause, Resume

[ https://issues.apache.org/jira/browse/AIRAVATA-961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma closed AIRAVATA-961. -- Resolution: Incomplete Currently Airavata supports (Cancel/Stop). This is tested in current 0.15. Airavata

[jira] [Updated] (AIRAVATA-1715) When experiments are launched from PGA, exp status in the Registry is not getting changed to LAUNCHED by the Orchestrator

[ https://issues.apache.org/jira/browse/AIRAVATA-1715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma updated AIRAVATA-1715: Assignee: Chathuri Wimalasena When experiments are launched from PGA, exp status in the Registry is not

[jira] [Closed] (AIRAVATA-1314) CANCELED an experiment in state CREATED. Got the message 'Experiment Canceled!' but still it has the status as CREATED.

[ https://issues.apache.org/jira/browse/AIRAVATA-1314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma closed AIRAVATA-1314. --- Cancel tested and verified in http://dev.test-drive.airavata.org/portal/ultrascan-testing/public/

[jira] [Resolved] (AIRAVATA-1094) Integration Test 1 - Create Experiment

[ https://issues.apache.org/jira/browse/AIRAVATA-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma resolved AIRAVATA-1094. - Resolution: Fixed Testing is transfered to test framework. Currently Create Experiment is been tested

[jira] [Resolved] (AIRAVATA-1687) Add gatewayExecutionId to Experiment model and WorkingDir to job details

[ https://issues.apache.org/jira/browse/AIRAVATA-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma resolved AIRAVATA-1687. - Resolution: Fixed Add gatewayExecutionId to Experiment model and WorkingDir to job details

[jira] [Closed] (AIRAVATA-1362) Terminate /cancel Experiment

[ https://issues.apache.org/jira/browse/AIRAVATA-1362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma closed AIRAVATA-1362. --- Resolution: Fixed Fix Version/s: (was: 1.0) 0.15 Terminate /cancel

[jira] [Closed] (AIRAVATA-914) Failed to authenticate when connecting to an existing database

[ https://issues.apache.org/jira/browse/AIRAVATA-914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma closed AIRAVATA-914. -- Resolution: Not A Problem User store will be handled by a third party tool.Only user name will be listed in

[jira] [Created] (AIRAVATA-1732) When an Experiment is created and launched while GFAC server is down it does not get LAUNCHED

Eroma created AIRAVATA-1732: --- Summary: When an Experiment is created and launched while GFAC server is down it does not get LAUNCHED Key: AIRAVATA-1732 URL: https://issues.apache.org/jira/browse/AIRAVATA-1732

[jira] [Updated] (AIRAVATA-1715) When experiments are launched from PGA, exp status in the Registry is not getting changed to LAUNCHED by the Orchestrator

[ https://issues.apache.org/jira/browse/AIRAVATA-1715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma updated AIRAVATA-1715: Issue Type: Sub-task (was: Bug) Parent: AIRAVATA-1732 When experiments are launched from PGA,