[jira] [Created] (AIRAVATA-1355) Use all supported modules for an application when scheduling a deployment for an experiment
Saminda Wijeratne created AIRAVATA-1355: --- Summary: Use all supported modules for an application when scheduling a deployment for an experiment Key: AIRAVATA-1355 URL: https://issues.apache.org/jira/browse/AIRAVATA-1355 Project: Airavata Issue Type: Bug Reporter: Saminda Wijeratne Assignee: Saminda Wijeratne -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (AIRAVATA-1309) Update Orchestrator and GFac to use the Application Catalog CPI
Saminda Wijeratne created AIRAVATA-1309: --- Summary: Update Orchestrator and GFac to use the Application Catalog CPI Key: AIRAVATA-1309 URL: https://issues.apache.org/jira/browse/AIRAVATA-1309 Project: Airavata Issue Type: Sub-task Components: Application Catalog Reporter: Saminda Wijeratne Assignee: Saminda Wijeratne -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (AIRAVATA-1301) Update Airavata 0.13 to support workflows
[ https://issues.apache.org/jira/browse/AIRAVATA-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14043770#comment-14043770 ] Saminda Wijeratne edited comment on AIRAVATA-1301 at 6/25/14 5:17 PM: -- After a few offline discussions we came up with the following steps to achieve this, 1. Updating Orchcestrator CPI to add launchTask(...) and deprecate/remove launchExperiment(...) 2. Update TaskDetails thrift model object so that we can move the host selecting scheduling part that is currently in gfac to the orchestrator and save it in taskdetails. the GFac will use this information to create the JEC (job execution context) 3. Introduce a new workflow submitter (similar to a jobsubmitter for gfac) class to trigger the updated workflow interpreter 4. Update the workflow interpreter to a. use the new registry for saving and retrieving workflow and node data b. call the orchestrator when required to launch tasks related to a workflow node c. use the monitor publisher to do task status monitor to update node statuses and take workflow execution decisions 5. Update the API to allow launching workflows 6. Update the thrift API service to launch single apps and workflows note: these steps will trigger considerable registry changes and updates to scheduling in gfac changes was (Author: samindaw): After a few offline discussions we came up with the following steps to achieve this, 1. Updating Orchcestrator CPI to add launchTask(...) and deprecate/remove launchExperiment(...) 2. Update TaskDetails thrift model object so that we can move the host selecting scheduling part that is currently in gfac to the orchestrator and save it in taskdetails. the GFac will use this information to create the JEC (job execution context) 3. Introduce a new workflow submitter (similar to a jobsubmitter for gfac) class to trigger the updated workflow interpreter 4. Update the workflow interpreter to a. use the new registry for saving and retrieving workflow and node data b. call the orchestrator when required to launch tasks related to a workflow node c. use the monitor publisher to do task status monitor to update node statuses and take workflow execution decisions 5. Update the API to allow launching workflows 6. Update the thrift API service to launch single apps and workflows > Update Airavata 0.13 to support workflows > - > > Key: AIRAVATA-1301 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1301 > Project: Airavata > Issue Type: Improvement >Reporter: Saminda Wijeratne >Assignee: Saminda Wijeratne > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (AIRAVATA-1301) Update Airavata 0.13 to support workflows
[ https://issues.apache.org/jira/browse/AIRAVATA-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14043770#comment-14043770 ] Saminda Wijeratne commented on AIRAVATA-1301: - After a few offline discussions we came up with the following steps to achieve this, 1. Updating Orchcestrator CPI to add launchTask(...) and deprecate/remove launchExperiment(...) 2. Update TaskDetails thrift model object so that we can move the host selecting scheduling part that is currently in gfac to the orchestrator and save it in taskdetails. the GFac will use this information to create the JEC (job execution context) 3. Introduce a new workflow submitter (similar to a jobsubmitter for gfac) class to trigger the updated workflow interpreter 4. Update the workflow interpreter to a. use the new registry for saving and retrieving workflow and node data b. call the orchestrator when required to launch tasks related to a workflow node c. use the monitor publisher to do task status monitor to update node statuses and take workflow execution decisions 5. Update the API to allow launching workflows 6. Update the thrift API service to launch single apps and workflows > Update Airavata 0.13 to support workflows > - > > Key: AIRAVATA-1301 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1301 > Project: Airavata > Issue Type: Improvement >Reporter: Saminda Wijeratne >Assignee: Saminda Wijeratne > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (AIRAVATA-1301) Update Airavata 0.13 to support workflows
Saminda Wijeratne created AIRAVATA-1301: --- Summary: Update Airavata 0.13 to support workflows Key: AIRAVATA-1301 URL: https://issues.apache.org/jira/browse/AIRAVATA-1301 Project: Airavata Issue Type: Improvement Reporter: Saminda Wijeratne -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (AIRAVATA-1301) Update Airavata 0.13 to support workflows
[ https://issues.apache.org/jira/browse/AIRAVATA-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saminda Wijeratne reassigned AIRAVATA-1301: --- Assignee: Saminda Wijeratne > Update Airavata 0.13 to support workflows > - > > Key: AIRAVATA-1301 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1301 > Project: Airavata > Issue Type: Improvement >Reporter: Saminda Wijeratne >Assignee: Saminda Wijeratne > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (AIRAVATA-1203) Define Thrift Data Models for the Application Catalog
Saminda Wijeratne created AIRAVATA-1203: --- Summary: Define Thrift Data Models for the Application Catalog Key: AIRAVATA-1203 URL: https://issues.apache.org/jira/browse/AIRAVATA-1203 Project: Airavata Issue Type: Sub-task Reporter: Saminda Wijeratne Assignee: Saminda Wijeratne Fix For: 0.12 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (AIRAVATA-1139) Cannot get all user projects
[
https://issues.apache.org/jira/browse/AIRAVATA-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13988568#comment-13988568
]
Saminda Wijeratne commented on AIRAVATA-1139:
-
Are you still getting this error?
> Cannot get all user projects
>
>
> Key: AIRAVATA-1139
> URL: https://issues.apache.org/jira/browse/AIRAVATA-1139
> Project: Airavata
> Issue Type: Bug
> Components: Airavata Client
> Environment: PHP
>Reporter: David Reagan
> Fix For: 0.12
>
>
> getAllUserProjects("admin") throws a TTransportException
> Fatal error: Uncaught exception 'Thrift\Exception\TTransportException' with
> message 'TSocket read 0 bytes' in
> C:\wamp\www\Airavata-PHP-Client-Samples\lib\Thrift\Transport\TSocket.php on
> line 269
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (AIRAVATA-1149) Create a new user using the Airavata API
Saminda Wijeratne created AIRAVATA-1149: --- Summary: Create a new user using the Airavata API Key: AIRAVATA-1149 URL: https://issues.apache.org/jira/browse/AIRAVATA-1149 Project: Airavata Issue Type: Task Reporter: Saminda Wijeratne Currently in order to run an experiment, the owner has to be registered as a user in Airavata. Thus Airavata API should have a function to introduce new users. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Reopened] (AIRAVATA-1142) getAllExperimentsInProject throws exeption instead of empty result
[ https://issues.apache.org/jira/browse/AIRAVATA-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saminda Wijeratne reopened AIRAVATA-1142: - As for an offline discussion we decided to return proper exception instead when a project doesn't exist. Reopening this JIRA until this is fixed. > getAllExperimentsInProject throws exeption instead of empty result > -- > > Key: AIRAVATA-1142 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1142 > Project: Airavata > Issue Type: Bug > Components: Airavata Client >Affects Versions: 0.12 > Environment: PHP Java >Reporter: David Reagan > Fix For: 0.12 > > > If you ask for a project that doesn't exist, an AiravataSystemException is > thrown instead of returning an empty array. > Fatal error: Uncaught exception 'Airavata\API\Error\AiravataSystemException' > in C:\wamp\www\Airavata-PHP-Client-Samples\lib\Airavata\API\Airavata.php on > line 2280 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (AIRAVATA-1139) Cannot get all user projects
[
https://issues.apache.org/jira/browse/AIRAVATA-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saminda Wijeratne resolved AIRAVATA-1139.
-
Resolution: Fixed
> Cannot get all user projects
>
>
> Key: AIRAVATA-1139
> URL: https://issues.apache.org/jira/browse/AIRAVATA-1139
> Project: Airavata
> Issue Type: Bug
> Components: Airavata Client
> Environment: PHP
>Reporter: David Reagan
> Fix For: 0.12
>
>
> getAllUserProjects("admin") throws a TTransportException
> Fatal error: Uncaught exception 'Thrift\Exception\TTransportException' with
> message 'TSocket read 0 bytes' in
> C:\wamp\www\Airavata-PHP-Client-Samples\lib\Thrift\Transport\TSocket.php on
> line 269
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Resolved] (AIRAVATA-1141) getAllUserExperiments() ignores input
[ https://issues.apache.org/jira/browse/AIRAVATA-1141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saminda Wijeratne resolved AIRAVATA-1141. - Resolution: Fixed Fix Version/s: 0.12 Chathuri's commit fixes this issue > getAllUserExperiments() ignores input > - > > Key: AIRAVATA-1141 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1141 > Project: Airavata > Issue Type: Bug > Components: Airavata Client >Affects Versions: 0.12 > Environment: PHP >Reporter: David Reagan > Fix For: 0.12 > > > getAllUserExperiments() returns the same result regardless of the input -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (AIRAVATA-1142) getAllExperimentsInProject throws exeption instead of empty result
[ https://issues.apache.org/jira/browse/AIRAVATA-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saminda Wijeratne resolved AIRAVATA-1142. - Resolution: Fixed Fix Version/s: 0.12 > getAllExperimentsInProject throws exeption instead of empty result > -- > > Key: AIRAVATA-1142 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1142 > Project: Airavata > Issue Type: Bug > Components: Airavata Client >Affects Versions: 0.12 > Environment: PHP Java >Reporter: David Reagan > Fix For: 0.12 > > > If you ask for a project that doesn't exist, an AiravataSystemException is > thrown instead of returning an empty array. > Fatal error: Uncaught exception 'Airavata\API\Error\AiravataSystemException' > in C:\wamp\www\Airavata-PHP-Client-Samples\lib\Airavata\API\Airavata.php on > line 2280 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (AIRAVATA-1142) getAllExperimentsInProject throws exeption instead of empty result
[ https://issues.apache.org/jira/browse/AIRAVATA-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13978477#comment-13978477 ] Saminda Wijeratne commented on AIRAVATA-1142: - Small update: when an experiment is created the project associated is automatically added if it doesn't exist. Thus following the same pattern I updated the above function to return an empty experiment list if the project does not exist. > getAllExperimentsInProject throws exeption instead of empty result > -- > > Key: AIRAVATA-1142 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1142 > Project: Airavata > Issue Type: Bug > Components: Airavata Client >Affects Versions: 0.12 > Environment: PHP Java >Reporter: David Reagan > > If you ask for a project that doesn't exist, an AiravataSystemException is > thrown instead of returning an empty array. > Fatal error: Uncaught exception 'Airavata\API\Error\AiravataSystemException' > in C:\wamp\www\Airavata-PHP-Client-Samples\lib\Airavata\API\Airavata.php on > line 2280 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (AIRAVATA-433) Providing Airavata API method to cancel a running job
[ https://issues.apache.org/jira/browse/AIRAVATA-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saminda Wijeratne reassigned AIRAVATA-433: -- Assignee: Saminda Wijeratne (was: Lahiru Gunathilake) > Providing Airavata API method to cancel a running job > - > > Key: AIRAVATA-433 > URL: https://issues.apache.org/jira/browse/AIRAVATA-433 > Project: Airavata > Issue Type: Sub-task > Components: Airavata Client, GFac >Affects Versions: 0.4-INCUBATING >Reporter: Raminderjeet Singh >Assignee: Saminda Wijeratne > Fix For: 0.13 > > > Currently users need to login to remote resource to cancel a running job. > Gram have a method to cancel jobs remotely by passing job id. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (AIRAVATA-433) Providing Airavata API method to cancel a running job
[ https://issues.apache.org/jira/browse/AIRAVATA-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saminda Wijeratne updated AIRAVATA-433: --- Issue Type: Sub-task (was: New Feature) Parent: AIRAVATA-961 > Providing Airavata API method to cancel a running job > - > > Key: AIRAVATA-433 > URL: https://issues.apache.org/jira/browse/AIRAVATA-433 > Project: Airavata > Issue Type: Sub-task > Components: Airavata Client, GFac >Affects Versions: 0.4-INCUBATING >Reporter: Raminderjeet Singh >Assignee: Lahiru Gunathilake > Fix For: 0.13 > > > Currently users need to login to remote resource to cancel a running job. > Gram have a method to cancel jobs remotely by passing job id. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (AIRAVATA-1145) Update Experiment Status when Job Status Changes
[ https://issues.apache.org/jira/browse/AIRAVATA-1145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saminda Wijeratne resolved AIRAVATA-1145. - Resolution: Fixed > Update Experiment Status when Job Status Changes > > > Key: AIRAVATA-1145 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1145 > Project: Airavata > Issue Type: Task >Reporter: Saminda Wijeratne >Assignee: Saminda Wijeratne > Fix For: 0.12 > > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (AIRAVATA-1146) Seperate out the Derby Server Startup from the Airavata API Server Startup
Saminda Wijeratne created AIRAVATA-1146: --- Summary: Seperate out the Derby Server Startup from the Airavata API Server Startup Key: AIRAVATA-1146 URL: https://issues.apache.org/jira/browse/AIRAVATA-1146 Project: Airavata Issue Type: Task Reporter: Saminda Wijeratne Currently the Airavata API Server starts up the derby server before it starts itself. The derby server will be redundant in case of trying to use an existing server hosted elsewhere. Thus Derby server startup/shutdown etc. should be refactored in to a new server so that users can give the option to to start or not the derby server. Airavata API Server startup is handled in class org.apache.airavata.api.server.AiravataAPIServer -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (AIRAVATA-1144) Airavata CPP Thrift Client Distribution
[ https://issues.apache.org/jira/browse/AIRAVATA-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saminda Wijeratne resolved AIRAVATA-1144. - Resolution: Fixed > Airavata CPP Thrift Client Distribution > --- > > Key: AIRAVATA-1144 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1144 > Project: Airavata > Issue Type: Task >Reporter: Saminda Wijeratne >Assignee: Saminda Wijeratne > Fix For: 0.12 > > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (AIRAVATA-1143) Airavata PHP Thrift Client Distribution
[ https://issues.apache.org/jira/browse/AIRAVATA-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saminda Wijeratne resolved AIRAVATA-1143. - Resolution: Fixed > Airavata PHP Thrift Client Distribution > --- > > Key: AIRAVATA-1143 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1143 > Project: Airavata > Issue Type: Bug >Reporter: Saminda Wijeratne >Assignee: Saminda Wijeratne > Fix For: 0.12 > > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (AIRAVATA-1145) Update Experiment Status when Job Status Changes
Saminda Wijeratne created AIRAVATA-1145: --- Summary: Update Experiment Status when Job Status Changes Key: AIRAVATA-1145 URL: https://issues.apache.org/jira/browse/AIRAVATA-1145 Project: Airavata Issue Type: Task Reporter: Saminda Wijeratne Assignee: Saminda Wijeratne Fix For: 0.12 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (AIRAVATA-1144) Airavata CPP Thrift Client Distribution
Saminda Wijeratne created AIRAVATA-1144: --- Summary: Airavata CPP Thrift Client Distribution Key: AIRAVATA-1144 URL: https://issues.apache.org/jira/browse/AIRAVATA-1144 Project: Airavata Issue Type: Task Reporter: Saminda Wijeratne -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (AIRAVATA-1144) Airavata CPP Thrift Client Distribution
[ https://issues.apache.org/jira/browse/AIRAVATA-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saminda Wijeratne reassigned AIRAVATA-1144: --- Assignee: Saminda Wijeratne > Airavata CPP Thrift Client Distribution > --- > > Key: AIRAVATA-1144 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1144 > Project: Airavata > Issue Type: Task >Reporter: Saminda Wijeratne >Assignee: Saminda Wijeratne > Fix For: 0.12 > > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (AIRAVATA-1144) Airavata CPP Thrift Client Distribution
[ https://issues.apache.org/jira/browse/AIRAVATA-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saminda Wijeratne updated AIRAVATA-1144: Fix Version/s: 0.12 > Airavata CPP Thrift Client Distribution > --- > > Key: AIRAVATA-1144 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1144 > Project: Airavata > Issue Type: Task >Reporter: Saminda Wijeratne >Assignee: Saminda Wijeratne > Fix For: 0.12 > > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (AIRAVATA-1143) Airavata PHP Thrift Client Distribution
Saminda Wijeratne created AIRAVATA-1143: --- Summary: Airavata PHP Thrift Client Distribution Key: AIRAVATA-1143 URL: https://issues.apache.org/jira/browse/AIRAVATA-1143 Project: Airavata Issue Type: Bug Reporter: Saminda Wijeratne Assignee: Saminda Wijeratne Fix For: 0.12 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (AIRAVATA-1142) getAllExperimentsInProject throws exeption instead of empty result
[ https://issues.apache.org/jira/browse/AIRAVATA-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13970679#comment-13970679 ] Saminda Wijeratne commented on AIRAVATA-1142: - Are we planning to register projects in the gateway? If so such exceptions are valid (but should be wrapped with a meaningful exception) if the project name/id is infact unregistered. Or else in all other cases I agree that the return result should be and empty list. I'm adding "Java" as well to the Environment (technically this affects all environment) Note: Looking at the implementation in the registry however enforces projects to be registered in the "Project" table before accessing any experiment data. This piece of code actually comes from our previous registry architecture which we are reusing for underline implementations of the new registry architecture assumingly due to similarity in the required data structures for the gateway. > getAllExperimentsInProject throws exeption instead of empty result > -- > > Key: AIRAVATA-1142 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1142 > Project: Airavata > Issue Type: Bug > Components: Airavata Client >Affects Versions: 0.12 > Environment: PHP >Reporter: David Reagan > > If you ask for a project that doesn't exist, an AiravataSystemException is > thrown instead of returning an empty array. > Fatal error: Uncaught exception 'Airavata\API\Error\AiravataSystemException' > in C:\wamp\www\Airavata-PHP-Client-Samples\lib\Airavata\API\Airavata.php on > line 2280 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (AIRAVATA-1142) getAllExperimentsInProject throws exeption instead of empty result
[ https://issues.apache.org/jira/browse/AIRAVATA-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saminda Wijeratne updated AIRAVATA-1142: Environment: PHP Java (was: PHP) > getAllExperimentsInProject throws exeption instead of empty result > -- > > Key: AIRAVATA-1142 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1142 > Project: Airavata > Issue Type: Bug > Components: Airavata Client >Affects Versions: 0.12 > Environment: PHP Java >Reporter: David Reagan > > If you ask for a project that doesn't exist, an AiravataSystemException is > thrown instead of returning an empty array. > Fatal error: Uncaught exception 'Airavata\API\Error\AiravataSystemException' > in C:\wamp\www\Airavata-PHP-Client-Samples\lib\Airavata\API\Airavata.php on > line 2280 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (AIRAVATA-1140) Create client samples that'll be distributed
Saminda Wijeratne created AIRAVATA-1140: --- Summary: Create client samples that'll be distributed Key: AIRAVATA-1140 URL: https://issues.apache.org/jira/browse/AIRAVATA-1140 Project: Airavata Issue Type: Task Reporter: Saminda Wijeratne Assignee: Saminda Wijeratne Fix For: 0.12 Currently we have no valid samples to be distributed with our client distributions. We need samples that demonstrate the client capabilities. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (AIRAVATA-1124) Cleaning up unused modules in the trunk for 0.12 release
[ https://issues.apache.org/jira/browse/AIRAVATA-1124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saminda Wijeratne resolved AIRAVATA-1124. - Resolution: Fixed security, xbaya-gui, ws-messenger/messagebox, ws-messenger/messagebroker modules will not be removed. the logic of removing the modules is to remove any modules which we will not need now or in the future and remove any module which will cause confusion to a user who will download the source of this release (eg: unused distrobutions, broken samples). > Cleaning up unused modules in the trunk for 0.12 release > > > Key: AIRAVATA-1124 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1124 > Project: Airavata > Issue Type: Task >Affects Versions: 0.12 >Reporter: Saminda Wijeratne >Assignee: Saminda Wijeratne > Fix For: 0.12 > > > This JIRA task is created in accordance with the airavata-dev list mail [1] > for cleaning up maven modules out of the Apache Airavata trunk. > 1. > http://markmail.org/message/wtpufpxbjabtyntx#query:+page:1+mid:i2jlwhsqnnjd57g2+state:results -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (AIRAVATA-1121) Refactor to have Server and Client configurations in one place
[ https://issues.apache.org/jira/browse/AIRAVATA-1121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saminda Wijeratne resolved AIRAVATA-1121. - Resolution: Fixed fixed > Refactor to have Server and Client configurations in one place > -- > > Key: AIRAVATA-1121 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1121 > Project: Airavata > Issue Type: Task >Reporter: Saminda Wijeratne > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (AIRAVATA-1137) Security module obsolete
[ https://issues.apache.org/jira/browse/AIRAVATA-1137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saminda Wijeratne resolved AIRAVATA-1137. - Resolution: Fixed Removed this from the build. But it will remain in the source since it'll be updated and used in the next release. > Security module obsolete > > > Key: AIRAVATA-1137 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1137 > Project: Airavata > Issue Type: Task >Reporter: Marlon Pierce >Priority: Minor > > Only the obsolete modules/rest has dependencies on modules/security, and the > build works fine with it commented out. > Nice code though, should be put in an attic someplace so we can easily find > it and repurpose it. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (AIRAVATA-1124) Cleaning up unused modules in the trunk for 0.12 release
[ https://issues.apache.org/jira/browse/AIRAVATA-1124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13967998#comment-13967998 ] Saminda Wijeratne edited comment on AIRAVATA-1124 at 4/14/14 5:32 AM: -- Following are the list of modules that is currently present in the trunk. I've tagged the ones that I'll be removing from trunk as "[REMOVE]" and the ones that will be moved to the airavata attic[1] as "[ATTIC]" as recommended by Marlon in a JIRA [2]. |-modules |---commons |-utils |-json [REMOVE] |-workflow-execution-context |-gfac-schema |-workflow-tracking |---security |---server |---rest [REMOVE] |-client |-webapp |-mappings |-service |---configuration |-server |-client |---orchestrator |-orchestrator-core |-airavata-orchestrator-service |-orchestrator-client-sdks |---ws-messenger |-messagebroker |-commons |-messagebox |-client |-distribution [REMOVE] |-samples [REMOVE] |-message-monitor |---test-suite |---workflow-model |-workflow-model-component-node [REMOVE] |-workflow-model-core |-workflow-model-component [REMOVE] |---xbaya-gui |---registry |-airavata-registry-test [REMOVE] |-airavata-jpa-registry |-registry-api |-registry-cpi |-airavata-registry-service [REMOVE] |---credential-store |---integration-tests |---distribution |-airavata-server |-xbaya-gui [REMOVE] |-release |-airavata-client |---gfac |-gfac-core |-gfac-ec2 |-gfac-monitor |---airavata-client |---workflow-interpreter [REMOVE] |-airavata-api |---airavata-model-utils |---airavata-api-server |---airavata-api-stubs |---airavata-data-models |---airavata-client-sdks |-java-client-samples |-tools |---job-monitor |---registry-tool |---gsissh |---phoebus-integration |-samples [REMOVE] |---simple-math-service |---sample-gateway |---levenshtein-distance-service |---provenance-registry-handler |---gateway-developer-guide |---echo-service |---distribution |---airavata-client |-create-application |-workflow-run |---complex-math-service 1. https://svn.apache.org/repos/asf/airavata/attic 2. https://issues.apache.org/jira/browse/AIRAVATA-1137 was (Author: samindaw): Following are the list of modules that is currently present in the trunk. I've tagged the ones that I'll be removing from trunk as "[REMOVE]" and the ones that will be moved to the airavata attic[1] as "[ATTIC]" as recommended by Marlon in a JIRA [2]. |-modules |---commons |-utils |-json [REMOVE] |-workflow-execution-context |-gfac-schema |-workflow-tracking |---security [REMOVE][ATTIC] |---server |---rest [REMOVE] |-client |-webapp |-mappings |-service |---configuration |-server |-client |---orchestrator |-orchestrator-core |-airavata-orchestrator-service |-orchestrator-client-sdks |---ws-messenger |-messagebroker [REMOVE][ATTIC] |-commons |-messagebox [REMOVE][ATTIC] |-client |-distribution [REMOVE] |-samples [REMOVE] |-message-monitor |---test-suite |---workflow-model |-workflow-model-component-node [REMOVE] |-workflow-model-core |-workflow-model-component [REMOVE] |---xbaya-gui [REMOVE][ATTIC] |---registry |-airavata-registry-test [REMOVE] |-airavata-jpa-registry |-registry-api |-registry-cpi |-airavata-registry-service [REMOVE] |---credential-store |---integration-tests |---distribution |-airavata-server |-xbaya-gui [REMOVE] |-release |-airavata-client |---gfac |-gfac-core |-gfac-ec2 |-gfac-monitor |---airavata-client |---workflow-interpreter [REMOVE] |-airavata-api |---airavata-model-utils |---airavata-api-server |---airavata-api-stubs |---airavata-data-models |---airavata-client-sdks |-java-client-samples |-tools |---job-monitor |---registry-tool |---gsissh |---phoebus-integration |-samples [REMOVE] |---simple-math-service |---sample-gateway |---levenshtein-distance-service |---provenance-registry-handler |---gateway-developer-guide |---echo-service |---distribution |---airavata-client |-create-application |-workflow-run |---complex-math-service 1. https://svn.apache.org/repos/asf/airavata/attic 2. https://issues.apache.org/jira/browse/AIRAVATA-1137 > Cleaning up unused modules in the trunk for 0.12 release > > > Key: AIR
[jira] [Commented] (AIRAVATA-1124) Cleaning up unused modules in the trunk for 0.12 release
[ https://issues.apache.org/jira/browse/AIRAVATA-1124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13967998#comment-13967998 ] Saminda Wijeratne commented on AIRAVATA-1124: - Following are the list of modules that is currently present in the trunk. I've tagged the ones that I'll be removing from trunk as "[REMOVE]" and the ones that will be moved to the airavata attic[1] as "[ATTIC]" as recommended by Marlon in a JIRA [2]. |-modules |---commons |-utils |-json [REMOVE] |-workflow-execution-context |-gfac-schema |-workflow-tracking |---security [REMOVE][ATTIC] |---server |---rest [REMOVE] |-client |-webapp |-mappings |-service |---configuration |-server |-client |---orchestrator |-orchestrator-core |-airavata-orchestrator-service |-orchestrator-client-sdks |---ws-messenger |-messagebroker [REMOVE][ATTIC] |-commons |-messagebox [REMOVE][ATTIC] |-client |-distribution [REMOVE] |-samples [REMOVE] |-message-monitor |---test-suite |---workflow-model |-workflow-model-component-node [REMOVE] |-workflow-model-core |-workflow-model-component [REMOVE] |---xbaya-gui [REMOVE][ATTIC] |---registry |-airavata-registry-test [REMOVE] |-airavata-jpa-registry |-registry-api |-registry-cpi |-airavata-registry-service [REMOVE] |---credential-store |---integration-tests |---distribution |-airavata-server |-xbaya-gui [REMOVE] |-release |-airavata-client |---gfac |-gfac-core |-gfac-ec2 |-gfac-monitor |---airavata-client |---workflow-interpreter [REMOVE] |-airavata-api |---airavata-model-utils |---airavata-api-server |---airavata-api-stubs |---airavata-data-models |---airavata-client-sdks |-java-client-samples |-tools |---job-monitor |---registry-tool |---gsissh |---phoebus-integration |-samples [REMOVE] |---simple-math-service |---sample-gateway |---levenshtein-distance-service |---provenance-registry-handler |---gateway-developer-guide |---echo-service |---distribution |---airavata-client |-create-application |-workflow-run |---complex-math-service 1. https://svn.apache.org/repos/asf/airavata/attic 2. https://issues.apache.org/jira/browse/AIRAVATA-1137 > Cleaning up unused modules in the trunk for 0.12 release > > > Key: AIRAVATA-1124 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1124 > Project: Airavata > Issue Type: Task >Affects Versions: 0.12 >Reporter: Saminda Wijeratne >Assignee: Saminda Wijeratne > Fix For: 0.12 > > > This JIRA task is created in accordance with the airavata-dev list mail [1] > for cleaning up maven modules out of the Apache Airavata trunk. > 1. > http://markmail.org/message/wtpufpxbjabtyntx#query:+page:1+mid:i2jlwhsqnnjd57g2+state:results -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (AIRAVATA-1126) Application Catalog Design
[ https://issues.apache.org/jira/browse/AIRAVATA-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saminda Wijeratne updated AIRAVATA-1126: Attachment: application.png share space.png share space.png - My initial understanding of different components involved and the boundaries which they belong to. application.png - abstract level understanding of what an application in an application catalog > Application Catalog Design > -- > > Key: AIRAVATA-1126 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1126 > Project: Airavata > Issue Type: Sub-task >Reporter: Saminda Wijeratne >Assignee: Saminda Wijeratne > Fix For: 0.13 > > Attachments: application.png, share space.png > > > Design how the application catalog will be exposed for external users > (gateway developers), how it will be made use by Airavata component > developers and how it is managed by the application catalog component. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (AIRAVATA-1126) Application Catalog Design
[ https://issues.apache.org/jira/browse/AIRAVATA-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13962371#comment-13962371 ] Saminda Wijeratne commented on AIRAVATA-1126: - As an abstract view of what a gateway will look for managing application access, using my current experience I compiled a google doc[1]. Feel free to review and put comments on it. If you do not have edit rights please request over the doc and I'll give permission to edit. 1. https://docs.google.com/document/d/1wzJzYu1d5aVLWj6L9lB1PdzuwxmBDAZHIgq8p95RTvY/edit > Application Catalog Design > -- > > Key: AIRAVATA-1126 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1126 > Project: Airavata > Issue Type: Sub-task >Reporter: Saminda Wijeratne >Assignee: Saminda Wijeratne > Fix For: 0.13 > > > Design how the application catalog will be exposed for external users > (gateway developers), how it will be made use by Airavata component > developers and how it is managed by the application catalog component. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (AIRAVATA-1126) Application Catalog Design
Saminda Wijeratne created AIRAVATA-1126: --- Summary: Application Catalog Design Key: AIRAVATA-1126 URL: https://issues.apache.org/jira/browse/AIRAVATA-1126 Project: Airavata Issue Type: Sub-task Reporter: Saminda Wijeratne Assignee: Saminda Wijeratne Design how the application catalog will be exposed for external users (gateway developers), how it will be made use by Airavata component developers and how it is managed by the application catalog component. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (AIRAVATA-1125) Application Catalog
Saminda Wijeratne created AIRAVATA-1125: --- Summary: Application Catalog Key: AIRAVATA-1125 URL: https://issues.apache.org/jira/browse/AIRAVATA-1125 Project: Airavata Issue Type: New Feature Affects Versions: 0.11, 0.12 Reporter: Saminda Wijeratne Fix For: 0.13 Next step of the major architectural change in Apache Airavata is to introduce the Application Catalog feature. (We will be discontinuing the support for descriptors which we have used so far to support defining application access information in Airavata once we have a stable Application Catalog implementation) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (AIRAVATA-1124) Cleaning up unused modules in the trunk for 0.12 release
Saminda Wijeratne created AIRAVATA-1124: --- Summary: Cleaning up unused modules in the trunk for 0.12 release Key: AIRAVATA-1124 URL: https://issues.apache.org/jira/browse/AIRAVATA-1124 Project: Airavata Issue Type: Task Affects Versions: 0.12 Reporter: Saminda Wijeratne Assignee: Saminda Wijeratne Fix For: 0.12 This JIRA task is created in accordance with the airavata-dev list mail [1] for cleaning up maven modules out of the Apache Airavata trunk. 1. http://markmail.org/message/wtpufpxbjabtyntx#query:+page:1+mid:i2jlwhsqnnjd57g2+state:results -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (AIRAVATA-1121) Refactor to have Server and Client configurations in one place
[
https://issues.apache.org/jira/browse/AIRAVATA-1121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13961619#comment-13961619
]
Saminda Wijeratne commented on AIRAVATA-1121:
-
I refactored the trunk source (except for samples directory) to have only one
instance of airavata-server.properties and airavata-client.properties files. As
mentioned before these files (along with some additional configuration files)
now exist as maven modules.
How to use these configuration modules,
1. Want to have the configuration file in the classpath of a module.
org.apache.airavata
airavata-server-configuration
or
org.apache.airavata
airavata-client-configuration
2. Want to have configurations copied to the binary distribution (zip/tar.gz).
Use the dependency plugin to extract the configuration jar to some location and
using the assembly plugin copy the configurations to the prefered location in
the distribution.
pom.xml,
org.apache.maven.plugins
maven-dependency-plugin
2.8
unpack
compile
unpack
org.apache.airavata
airavata-client-configuration
${project.version}
jar
${project.build.directory}/conf
eg: bin-assembly.xml
...
...
${project.build.directory}/conf
conf
*.properties
...
...
3. Need either one of the configuration file for unit/integration tests.
org.apache.airavata
airavata-server-configuration
test
or
org.apache.airavata
airavata-client-configuration
test
Also I updated the ApplicationSettings/ServerSettings classes support settings
overriding through external settings files and system properties. Following is
the increasing order or priority in overriding configuration settings in
Airavata.
airavata-server.properties / airavata-client.properties
External settings files
Settings passed as command line args
Settings defined as system properties
> Refactor to have Server and Client configurations in one place
> --
>
> Key: AIRAVATA-1121
> URL: https://issues.apache.org/jira/browse/AIRAVATA-1121
> Project: Airavata
> Issue Type: Task
>Reporter: Saminda Wijeratne
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (AIRAVATA-1119) JPARegistry tests are failing
[ https://issues.apache.org/jira/browse/AIRAVATA-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13959798#comment-13959798 ] Saminda Wijeratne commented on AIRAVATA-1119: - It seems the 2 test classes which are failing are dependent upon a JPAResource class which looks for a db table of the previous experiment data structure. I will check to see if these resource classes can be salvaged to support the new structure or new resource classes are needed instead. > JPARegistry tests are failing > - > > Key: AIRAVATA-1119 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1119 > Project: Airavata > Issue Type: Bug > Components: Registry API >Affects Versions: 0.12 > Environment: mac >Reporter: Lahiru Gunathilake >Priority: Critical > Fix For: 0.13 > > > http://pastebin.com/6ije858z -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (AIRAVATA-1119) JPARegistry tests are failing
[ https://issues.apache.org/jira/browse/AIRAVATA-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saminda Wijeratne reassigned AIRAVATA-1119: --- Assignee: Saminda Wijeratne > JPARegistry tests are failing > - > > Key: AIRAVATA-1119 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1119 > Project: Airavata > Issue Type: Bug > Components: Registry API >Affects Versions: 0.12 > Environment: mac >Reporter: Lahiru Gunathilake >Assignee: Saminda Wijeratne >Priority: Critical > Fix For: 0.13 > > > http://pastebin.com/6ije858z -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (AIRAVATA-1121) Refactor to have Server and Client configurations in one place
Saminda Wijeratne created AIRAVATA-1121: --- Summary: Refactor to have Server and Client configurations in one place Key: AIRAVATA-1121 URL: https://issues.apache.org/jira/browse/AIRAVATA-1121 Project: Airavata Issue Type: Task Reporter: Saminda Wijeratne -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (AIRAVATA-973) Improving XBays.java '-workflow' option to accept URL as well
[ https://issues.apache.org/jira/browse/AIRAVATA-973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saminda Wijeratne updated AIRAVATA-973: --- Fix Version/s: (was: 0.10) 0.13 > Improving XBays.java '-workflow' option to accept URL as well > -- > > Key: AIRAVATA-973 > URL: https://issues.apache.org/jira/browse/AIRAVATA-973 > Project: Airavata > Issue Type: Improvement > Components: XBaya >Affects Versions: 0.10 >Reporter: Heejoon Chae > Labels: Contributor, features, improvement > Fix For: 0.13 > > Original Estimate: 168h > Remaining Estimate: 168h > > Currently -workflow option in XBaya.java only accept registered workflow ID > in registry. > Accepting URL based workflow using -workflow option allows that the workflow > can be created on the fly including user specific default values in it. > This functionality allow creating user specific workflows on the fly. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (AIRAVATA-973) Improving XBays.java '-workflow' option to accept URL as well
[ https://issues.apache.org/jira/browse/AIRAVATA-973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13956974#comment-13956974 ] Saminda Wijeratne commented on AIRAVATA-973: I will fix this along with the updates to the workflow interpreter for 0.13 > Improving XBays.java '-workflow' option to accept URL as well > -- > > Key: AIRAVATA-973 > URL: https://issues.apache.org/jira/browse/AIRAVATA-973 > Project: Airavata > Issue Type: Improvement > Components: XBaya >Affects Versions: 0.10 >Reporter: Heejoon Chae > Labels: Contributor, features, improvement > Fix For: 0.13 > > Original Estimate: 168h > Remaining Estimate: 168h > > Currently -workflow option in XBaya.java only accept registered workflow ID > in registry. > Accepting URL based workflow using -workflow option allows that the workflow > can be created on the fly including user specific default values in it. > This functionality allow creating user specific workflows on the fly. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (AIRAVATA-490) Deployment Description Delete Issue
[ https://issues.apache.org/jira/browse/AIRAVATA-490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saminda Wijeratne resolved AIRAVATA-490. Resolution: Invalid We no longer use JCRRegistry > Deployment Description Delete Issue > --- > > Key: AIRAVATA-490 > URL: https://issues.apache.org/jira/browse/AIRAVATA-490 > Project: Airavata > Issue Type: Bug > Components: Registry API >Reporter: Bhathiya Jayasekara >Assignee: Bhathiya Jayasekara > Attachments: deleteapp.patch > > > When a Deployment Description is deleted, all Deployment descriptions of that > particular Service and Host are deleted. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (AIRAVATA-461) Allow users skip the workflow Nodes which already ran and invoke the rest of the Nodes
[ https://issues.apache.org/jira/browse/AIRAVATA-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13956962#comment-13956962 ] Saminda Wijeratne commented on AIRAVATA-461: Not sure whether it fixed yet or not... But we'll be able to fix this when we update the workflow interpreter for 0.13. > Allow users skip the workflow Nodes which already ran and invoke the rest of > the Nodes > -- > > Key: AIRAVATA-461 > URL: https://issues.apache.org/jira/browse/AIRAVATA-461 > Project: Airavata > Issue Type: Improvement > Components: Workflow Interpreter, XBaya >Affects Versions: 0.4-INCUBATING > Environment: $subject. So if you have a long running node which > already ran and if you are not changing the inputs for that node you can run > the workflow with same experiment ID and XBaya will not run the workflow > Nodes which already ran and will simply use the outputs gerated. > XBaya will load the outputs from Registry and use them. This will be useful > in-case XBaya or backend server crashed during a workflow run. > Lahiru >Reporter: Lahiru Gunathilake >Assignee: Saminda Wijeratne > Fix For: 0.13 > > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (AIRAVATA-461) Allow users skip the workflow Nodes which already ran and invoke the rest of the Nodes
[ https://issues.apache.org/jira/browse/AIRAVATA-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saminda Wijeratne updated AIRAVATA-461: --- Fix Version/s: 0.13 > Allow users skip the workflow Nodes which already ran and invoke the rest of > the Nodes > -- > > Key: AIRAVATA-461 > URL: https://issues.apache.org/jira/browse/AIRAVATA-461 > Project: Airavata > Issue Type: Improvement > Components: Workflow Interpreter, XBaya >Affects Versions: 0.4-INCUBATING > Environment: $subject. So if you have a long running node which > already ran and if you are not changing the inputs for that node you can run > the workflow with same experiment ID and XBaya will not run the workflow > Nodes which already ran and will simply use the outputs gerated. > XBaya will load the outputs from Registry and use them. This will be useful > in-case XBaya or backend server crashed during a workflow run. > Lahiru >Reporter: Lahiru Gunathilake >Assignee: Saminda Wijeratne > Fix For: 0.13 > > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (AIRAVATA-822) Delete experiment records.
[ https://issues.apache.org/jira/browse/AIRAVATA-822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saminda Wijeratne updated AIRAVATA-822: --- Issue Type: Wish (was: New Feature) > Delete experiment records. > -- > > Key: AIRAVATA-822 > URL: https://issues.apache.org/jira/browse/AIRAVATA-822 > Project: Airavata > Issue Type: Wish >Reporter: Shinyoung Ahn >Assignee: Saminda Wijeratne > Fix For: WISHLIST > > > User who execute some workflow via XBaya. > As experiment records increase, user may be difficult to find out his/her > interesting records > becasue too may records are there.. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (AIRAVATA-822) Delete experiment records.
[ https://issues.apache.org/jira/browse/AIRAVATA-822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saminda Wijeratne updated AIRAVATA-822: --- Fix Version/s: WISHLIST > Delete experiment records. > -- > > Key: AIRAVATA-822 > URL: https://issues.apache.org/jira/browse/AIRAVATA-822 > Project: Airavata > Issue Type: Wish >Reporter: Shinyoung Ahn >Assignee: Saminda Wijeratne > Fix For: WISHLIST > > > User who execute some workflow via XBaya. > As experiment records increase, user may be difficult to find out his/her > interesting records > becasue too may records are there.. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (AIRAVATA-669) Separate current Airavata binary distributions to seperate Client & Server binary distributions
[ https://issues.apache.org/jira/browse/AIRAVATA-669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saminda Wijeratne resolved AIRAVATA-669. Resolution: Fixed Resolving this since it was fixed long time ago. > Separate current Airavata binary distributions to seperate Client & Server > binary distributions > --- > > Key: AIRAVATA-669 > URL: https://issues.apache.org/jira/browse/AIRAVATA-669 > Project: Airavata > Issue Type: Task >Reporter: Saminda Wijeratne > > Current binary distribution include both server & client components together. > In order to avoid confusion & unnecessary overhead of > retrieving/understanding/configuring for different stakeholders we can have > the following separate binary distributions created at build-time, > Airavata server binary distribution - everything related to hosting an > Airavata Server > XBaya binary distribution - everything needed for XBaya to run > independently > Airavata client binary distribution - all the libraries required for a 3rd > party client to use the Airavata API -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13956076#comment-13956076 ] Saminda Wijeratne commented on AIRAVATA-1055: - Thanks for the patch Sachith. Tested and committed to the trunk. > 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)
[jira] [Updated] (AIRAVATA-1105) Integration Test 2 - Notifications when Results available for Download
[ https://issues.apache.org/jira/browse/AIRAVATA-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saminda Wijeratne updated AIRAVATA-1105: Summary: Integration Test 2 - Notifications when Results available for Download (was: CIPRES Integration Test 2 - Notifications when Results available for Download) > Integration Test 2 - Notifications when Results available for Download > -- > > Key: AIRAVATA-1105 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1105 > Project: Airavata > Issue Type: Sub-task >Reporter: Saminda Wijeratne >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-1104) Integration Test 2 - Notification when Experiment Completes/Fails
[ https://issues.apache.org/jira/browse/AIRAVATA-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saminda Wijeratne updated AIRAVATA-1104: Summary: Integration Test 2 - Notification when Experiment Completes/Fails (was: CIPRES Integration Test 2 - Notification when Experiment Completes/Fails) > 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] [Updated] (AIRAVATA-1107) Integration Test 2 - View Experiment Errors
[ https://issues.apache.org/jira/browse/AIRAVATA-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saminda Wijeratne updated AIRAVATA-1107: Summary: Integration Test 2 - View Experiment Errors (was: CIPRES Integration Test 2 - View Experiment Errors) > 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-1106) 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: Integration Test 2 - Download Experiment Final Results (was: CIPRES Integration Test 2 - Download Experiment Final Results) > 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] [Updated] (AIRAVATA-1100) Integration Test 2 - Launch Experiment
[ https://issues.apache.org/jira/browse/AIRAVATA-1100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saminda Wijeratne updated AIRAVATA-1100: Summary: Integration Test 2 - Launch Experiment (was: CIPRES Integration Test 2 - Launch Experiment) > 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] [Updated] (AIRAVATA-1098) 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: Summary: Integration Test 2 - Manage Launched Experiments (was: CIPRES Integration Test 2 - Manage Launched Experiments) > 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-1102) 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: Summary: Integration Test 2 - List Experiment Intermediate Results (was: CIPRES Integration Test 2 - List Experiment Intermediate Results) > 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] [Updated] (AIRAVATA-1102) 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) 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, 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) > 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) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (AIRAVATA-1103) Integration Test 2 - Download Experiment Intermediate Results
[ https://issues.apache.org/jira/browse/AIRAVATA-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saminda Wijeratne updated AIRAVATA-1103: Summary: Integration Test 2 - Download Experiment Intermediate Results (was: CIPRES Integration Test 2 - Download Experiment Intermediate Results) > 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] [Updated] (AIRAVATA-1101) Integration Test 2 - Monitor Experiment
[ https://issues.apache.org/jira/browse/AIRAVATA-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saminda Wijeratne updated AIRAVATA-1101: Summary: Integration Test 2 - Monitor Experiment (was: CIPRES Integration Test 2 - Monitor Experiment) > 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] [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] [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] [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: Summary: Integration Test 1 - Clone Experiment (was: CIPRES Integration Test 1 - Clone Experiment) > 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 CIPRES > user or gateway input. -- 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-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-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: 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". was: 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. > 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". -- 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-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] [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: Environment: (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. ) > 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 > -- 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] [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] [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-1105) CIPRES Integration Test 2 - Notifications when Results available for Download
Saminda Wijeratne created AIRAVATA-1105: --- Summary: CIPRES Integration Test 2 - Notifications when Results available for Download Key: AIRAVATA-1105 URL: https://issues.apache.org/jira/browse/AIRAVATA-1105 Project: Airavata Issue Type: Sub-task Reporter: Saminda Wijeratne 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] [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] [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-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] [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-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] [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] [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: Description: List set of experiment which belongs to the gateway user. Should be able to list Experiment by its state (Unlaunched/Launched/Completed/etc.) (was: List set of experiment which hasn't being launched yet which belongs to the gateway user.) > 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 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-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] [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] [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-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: 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-1096) CIPRES Integration Test 1 - Clone Experiment
Saminda Wijeratne created AIRAVATA-1096: --- Summary: CIPRES 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 CIPRES user or gateway input. -- 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 - Create/Update and Save Task
[ 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 - Create/Update and Save Task (was: CIPRES Integration Test - Create/Update and Save Task) > CIPRES Integration Test 1 - 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] [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-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] [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] [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)
[jira] [Resolved] (AIRAVATA-1051) Airavata-Client distribution doesn't work with the old API anymore
[ https://issues.apache.org/jira/browse/AIRAVATA-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saminda Wijeratne resolved AIRAVATA-1051. - Resolution: Fixed The fix is mainly to allow supporting descriptor functions. > Airavata-Client distribution doesn't work with the old API anymore > -- > > Key: AIRAVATA-1051 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1051 > Project: Airavata > Issue Type: Bug >Reporter: Saminda Wijeratne > Fix For: 0.12 > > > This distribution is obsolete for the new architecture. However since the new > API doesn't provide functions to add applications to the system we need to > reuse the old API. Since REST services are no longer hosted the API has to > connect with the registry using the JPA implementation and currently the > client distribution throws errors when trying to use the API. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (AIRAVATA-524) The monitor panel need to be minimizable
[ https://issues.apache.org/jira/browse/AIRAVATA-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saminda Wijeratne resolved AIRAVATA-524. Resolution: Fixed This is related to Paramberoo project. > The monitor panel need to be minimizable > > > Key: AIRAVATA-524 > URL: https://issues.apache.org/jira/browse/AIRAVATA-524 > Project: Airavata > Issue Type: Wish >Reporter: Sudhakar Pamidighantam > > The monitor panel can only be closed currently. It will be useful to be able > to minimize and resize it so the rest of desktop is not cluttered. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (AIRAVATA-408) Learning Airavata from a Developers Perspective
[ https://issues.apache.org/jira/browse/AIRAVATA-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saminda Wijeratne updated AIRAVATA-408: --- Component/s: WS-Messenger Website/Documentation GFac Airavata Orchestrator Airavata Job Monitor Airavata Client Airavata API > Learning Airavata from a Developers Perspective > --- > > Key: AIRAVATA-408 > URL: https://issues.apache.org/jira/browse/AIRAVATA-408 > Project: Airavata > Issue Type: Task > Components: Airavata API, Airavata Client, Airavata Job Monitor, > Airavata Orchestrator, GFac, Website/Documentation, Workflow Interpreter, > WS-Messenger >Reporter: Saminda Wijeratne > > Airavata is not a large project, but still there are quite alot of components > in it for a developer to get familiar with before diving in on its API. This > task will address learning the essentials of APIs present in Airavata & some > of the programming aspects related to working with Airavata source code. -- This message was sent by Atlassian JIRA (v6.2#6252)
