[jira] [Commented] (AIRAVATA-1632) Evaluate Apache Thrift 0.9.2 multi-plexing for Airavata Services
[ https://issues.apache.org/jira/browse/AIRAVATA-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14366632#comment-14366632 ] ASF subversion and git services commented on AIRAVATA-1632: --- Commit e33bf99b040eb59add06d73b25c3e5a042dbd1da in airavata-sandbox's branch refs/heads/master from [~smarru] [ https://git-wip-us.apache.org/repos/asf?p=airavata-sandbox.git;h=e33bf99 ] adding java multiplexing client for AIRAVATA-1632 > Evaluate Apache Thrift 0.9.2 multi-plexing for Airavata Services > > > Key: AIRAVATA-1632 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1632 > Project: Airavata > Issue Type: Task >Reporter: Suresh Marru > Fix For: WISHLIST > > > Evaluate updating Airavata API to use thrift 0.9.2. Among numerous bug fixes, > multiplexing is fully supported and is of interest to Airavata. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AIRAVATA-1635) [GSoC] Integrate Airavata Java Client SDK with GridChem Client
[ https://issues.apache.org/jira/browse/AIRAVATA-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14365789#comment-14365789 ] Suresh Marru commented on AIRAVATA-1635: Well the best API for the middleware service will be the WSDL itself. If you cannot find the wsdl in the code, I will fetch it from a production instance. Yes you will require to have a local instance of Airavata for all this development. > [GSoC] Integrate Airavata Java Client SDK with GridChem Client > --- > > Key: AIRAVATA-1635 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1635 > Project: Airavata > Issue Type: Epic >Reporter: Suresh Marru > Labels: gsoc, gsoc2015, mentor > > GridChem is a Science Gateway enables users to run computational experiments > on multiple supercomputing resources. Currently GridChem, a java swing based > webstart client [1] uses a Axis2 based Middleware Service [2] which brokers > users actions into computational jobs. > This project needs to understand the Client [1] and port it to use Apache > Airavata java client SDK. The project has following components: > * Integrate GridChem client with Airavata User Store (implemented by WSO2 > Identity Server) > * Integrate with Airavata API for application executions. > * Integrate with Atlassian JIRA + Confluence for user error reporting and > status notifications. > [1] - https://github.com/SciGaP/sha2-GridChem-client > [2] - https://github.com/SciGaP/sha2-gms -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AIRAVATA-1636) [GSoC] Benchmark framework to facilitate Airavata Scheduling
[ https://issues.apache.org/jira/browse/AIRAVATA-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14365793#comment-14365793 ] Suresh Marru commented on AIRAVATA-1636: Concretely the expected outcome of the GSoC project will include: * Plugin a bench marking framework to Airavata. * Run some benchmarks of sample applications of airavata. But it will be better if previous execution run times can be taken into account. > [GSoC] Benchmark framework to facilitate Airavata Scheduling > > > Key: AIRAVATA-1636 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1636 > Project: Airavata > Issue Type: New Feature >Reporter: Suresh Marru > Labels: gsoc, gsoc2015, mentor > > Airavata assists science gateways to execute on multiple computational > resources. To efficiently schedule applications on resources, Airavata needs > to understand application performance. Applications are typically complex in > terms of the models and algorithms they support and internally implemented > optimization of resources available. The hardware provides additional > variables in this optimization in terms of memory and computing units that > can be allocated and time restrictions in the form of queue limits. > Scheduling adds to this complexity by implementing policies toward enabling a > particular Science domain and/or maximizing the usage of the resources > itself. > Airavata can feed data from historical executions and a framework can be > built to systematically feed to new experiments (based on existing or totally > newly devised models) executed. The run and timing data then can be codified > such that the information can be presented to the user if an intelligent > choice can be made by the user or can be used programmatically by Airavata in > cases where the user does not or cannot provide such a choice. > The end goal of this benchmark exercise will be to provide fastest execution > time possible accounting for constraints available in the gateway to optimize > its own allocations for all the users in the communities the gateway > supports. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AIRAVATA-1635) [GSoC] Integrate Airavata Java Client SDK with GridChem Client
[ https://issues.apache.org/jira/browse/AIRAVATA-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14365777#comment-14365777 ] Dimuthu Upeksha commented on AIRAVATA-1635: --- 1. Is there any documentation that describes about the API functions of Middleware Service [2] and Airavata SDK? 2. Do I have to setup a local SCiGap (Airavata) instance or is there a existing setup? > [GSoC] Integrate Airavata Java Client SDK with GridChem Client > --- > > Key: AIRAVATA-1635 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1635 > Project: Airavata > Issue Type: Epic >Reporter: Suresh Marru > Labels: gsoc, gsoc2015, mentor > > GridChem is a Science Gateway enables users to run computational experiments > on multiple supercomputing resources. Currently GridChem, a java swing based > webstart client [1] uses a Axis2 based Middleware Service [2] which brokers > users actions into computational jobs. > This project needs to understand the Client [1] and port it to use Apache > Airavata java client SDK. The project has following components: > * Integrate GridChem client with Airavata User Store (implemented by WSO2 > Identity Server) > * Integrate with Airavata API for application executions. > * Integrate with Atlassian JIRA + Confluence for user error reporting and > status notifications. > [1] - https://github.com/SciGaP/sha2-GridChem-client > [2] - https://github.com/SciGaP/sha2-gms -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AIRAVATA-1636) [GSoC] Benchmark framework to facilitate Airavata Scheduling
Suresh Marru created AIRAVATA-1636: -- Summary: [GSoC] Benchmark framework to facilitate Airavata Scheduling Key: AIRAVATA-1636 URL: https://issues.apache.org/jira/browse/AIRAVATA-1636 Project: Airavata Issue Type: New Feature Reporter: Suresh Marru Airavata assists science gateways to execute on multiple computational resources. To efficiently schedule applications on resources, Airavata needs to understand application performance. Applications are typically complex in terms of the models and algorithms they support and internally implemented optimization of resources available. The hardware provides additional variables in this optimization in terms of memory and computing units that can be allocated and time restrictions in the form of queue limits. Scheduling adds to this complexity by implementing policies toward enabling a particular Science domain and/or maximizing the usage of the resources itself. Airavata can feed data from historical executions and a framework can be built to systematically feed to new experiments (based on existing or totally newly devised models) executed. The run and timing data then can be codified such that the information can be presented to the user if an intelligent choice can be made by the user or can be used programmatically by Airavata in cases where the user does not or cannot provide such a choice. The end goal of this benchmark exercise will be to provide fastest execution time possible accounting for constraints available in the gateway to optimize its own allocations for all the users in the communities the gateway supports. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AIRAVATA-1635) [GSoC] Integrate Airavata Java Client SDK with GridChem Client
[ https://issues.apache.org/jira/browse/AIRAVATA-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Marru updated AIRAVATA-1635: --- Description: GridChem is a Science Gateway enables users to run computational experiments on multiple supercomputing resources. Currently GridChem, a java swing based webstart client [1] uses a Axis2 based Middleware Service [2] which brokers users actions into computational jobs. This project needs to understand the Client [1] and port it to use Apache Airavata java client SDK. The project has following components: * Integrate GridChem client with Airavata User Store (implemented by WSO2 Identity Server) * Integrate with Airavata API for application executions. * Integrate with Atlassian JIRA + Confluence for user error reporting and status notifications. [1] - https://github.com/SciGaP/sha2-GridChem-client [2] - https://github.com/SciGaP/sha2-gms was: GridChem is a Science Gateway enables users to run computational experiments on multiple supercomputing resources. Currently GridChem, a java swing based webstart client [1] uses a Axis2 based Middleware Service [2] which brokers users actions into computational jobs. This project needs to understand the Client [1] and port it to use Apache Airavata java client SDK. The project has following components: * Integrate GridChem client with Airavata User Store (implemented by WSO2 Identity Server) * Integrate with Airavata API for application executions. * Integrate with Atlassian JIRA + Confluence for user error reporting and status notifications. > [GSoC] Integrate Airavata Java Client SDK with GridChem Client > --- > > Key: AIRAVATA-1635 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1635 > Project: Airavata > Issue Type: Epic >Reporter: Suresh Marru > Labels: gsoc, gsoc2015, mentor > > GridChem is a Science Gateway enables users to run computational experiments > on multiple supercomputing resources. Currently GridChem, a java swing based > webstart client [1] uses a Axis2 based Middleware Service [2] which brokers > users actions into computational jobs. > This project needs to understand the Client [1] and port it to use Apache > Airavata java client SDK. The project has following components: > * Integrate GridChem client with Airavata User Store (implemented by WSO2 > Identity Server) > * Integrate with Airavata API for application executions. > * Integrate with Atlassian JIRA + Confluence for user error reporting and > status notifications. > [1] - https://github.com/SciGaP/sha2-GridChem-client > [2] - https://github.com/SciGaP/sha2-gms -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AIRAVATA-1635) [GSoC] Integrate Airavata Java Client SDK with GridChem Client
Suresh Marru created AIRAVATA-1635: -- Summary: [GSoC] Integrate Airavata Java Client SDK with GridChem Client Key: AIRAVATA-1635 URL: https://issues.apache.org/jira/browse/AIRAVATA-1635 Project: Airavata Issue Type: Epic Reporter: Suresh Marru GridChem is a Science Gateway enables users to run computational experiments on multiple supercomputing resources. Currently GridChem, a java swing based webstart client [1] uses a Axis2 based Middleware Service [2] which brokers users actions into computational jobs. This project needs to understand the Client [1] and port it to use Apache Airavata java client SDK. The project has following components: * Integrate GridChem client with Airavata User Store (implemented by WSO2 Identity Server) * Integrate with Airavata API for application executions. * Integrate with Atlassian JIRA + Confluence for user error reporting and status notifications. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AIRAVATA-1631) To handle outputs in other folders than working directory
[ https://issues.apache.org/jira/browse/AIRAVATA-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14365464#comment-14365464 ] ASF subversion and git services commented on AIRAVATA-1631: --- Commit 7d57c09865be7da0dff3ec506e5b6bd00cbf9268 in airavata's branch refs/heads/master from [~raminder] [ https://git-wip-us.apache.org/repos/asf?p=airavata.git;h=7d57c09 ] Changed according to AIRAVATA-1634 in clone fix. AIRAVATA-1631 > To handle outputs in other folders than working directory > - > > Key: AIRAVATA-1631 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1631 > Project: Airavata > Issue Type: Improvement > Components: GFac >Affects Versions: 0.15 >Reporter: Raminderjeet Singh >Assignee: Raminderjeet Singh > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AIRAVATA-1634) Experiment cloning should not have output details from previous run
[ https://issues.apache.org/jira/browse/AIRAVATA-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14365463#comment-14365463 ] ASF subversion and git services commented on AIRAVATA-1634: --- Commit 7d57c09865be7da0dff3ec506e5b6bd00cbf9268 in airavata's branch refs/heads/master from [~raminder] [ https://git-wip-us.apache.org/repos/asf?p=airavata.git;h=7d57c09 ] Changed according to AIRAVATA-1634 in clone fix. AIRAVATA-1631 > Experiment cloning should not have output details from previous run > --- > > Key: AIRAVATA-1634 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1634 > Project: Airavata > Issue Type: Improvement > Components: Airavata API >Affects Versions: 0.15 >Reporter: Raminderjeet Singh >Assignee: Chathuri Wimalasena > > If we are cloning a finished or failed experiment, then it should not copy > the output details. To handle this we have some code in GFAC BetterGfacImpl > which can create problems if output location is set. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1634) Experiment cloning should not have output details from previous run
[ https://issues.apache.org/jira/browse/AIRAVATA-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chathuri Wimalasena resolved AIRAVATA-1634. --- Resolution: Fixed > Experiment cloning should not have output details from previous run > --- > > Key: AIRAVATA-1634 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1634 > Project: Airavata > Issue Type: Improvement > Components: Airavata API >Affects Versions: 0.15 >Reporter: Raminderjeet Singh >Assignee: Chathuri Wimalasena > > If we are cloning a finished or failed experiment, then it should not copy > the output details. To handle this we have some code in GFAC BetterGfacImpl > which can create problems if output location is set. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AIRAVATA-1634) Experiment cloning should not have output details from previous run
[ https://issues.apache.org/jira/browse/AIRAVATA-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14365318#comment-14365318 ] ASF subversion and git services commented on AIRAVATA-1634: --- Commit f708304446dae8aa02244a9baa05cba13242a166 in airavata's branch refs/heads/master from [~chathuri] [ https://git-wip-us.apache.org/repos/asf?p=airavata.git;h=f708304 ] fixing AIRAVATA-1634 > Experiment cloning should not have output details from previous run > --- > > Key: AIRAVATA-1634 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1634 > Project: Airavata > Issue Type: Improvement > Components: Airavata API >Affects Versions: 0.15 >Reporter: Raminderjeet Singh >Assignee: Chathuri Wimalasena > > If we are cloning a finished or failed experiment, then it should not copy > the output details. To handle this we have some code in GFAC BetterGfacImpl > which can create problems if output location is set. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AIRAVATA-1634) Experiment cloning should not have output details from previous run
[ https://issues.apache.org/jira/browse/AIRAVATA-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chathuri Wimalasena reassigned AIRAVATA-1634: - Assignee: Chathuri Wimalasena > Experiment cloning should not have output details from previous run > --- > > Key: AIRAVATA-1634 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1634 > Project: Airavata > Issue Type: Improvement > Components: Airavata API >Affects Versions: 0.15 >Reporter: Raminderjeet Singh >Assignee: Chathuri Wimalasena > > If we are cloning a finished or failed experiment, then it should not copy > the output details. To handle this we have some code in GFAC BetterGfacImpl > which can create problems if output location is set. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AIRAVATA-1634) Experiment cloning should not have output details from previous run
Raminderjeet Singh created AIRAVATA-1634: Summary: Experiment cloning should not have output details from previous run Key: AIRAVATA-1634 URL: https://issues.apache.org/jira/browse/AIRAVATA-1634 Project: Airavata Issue Type: Improvement Components: Airavata API Affects Versions: 0.15 Reporter: Raminderjeet Singh If we are cloning a finished or failed experiment, then it should not copy the output details. To handle this we have some code in GFAC BetterGfacImpl which can create problems if output location is set. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AIRAVATA-1633) Add empty checks if a job property is not set
[ https://issues.apache.org/jira/browse/AIRAVATA-1633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14365217#comment-14365217 ] ASF subversion and git services commented on AIRAVATA-1633: --- Commit d09957ba1b8c4b19c59349defccc9382a483619c in airavata's branch refs/heads/master from [~raminder] [ https://git-wip-us.apache.org/repos/asf?p=airavata.git;h=d09957b ] Fixed AIRAVATA-1633. > Add empty checks if a job property is not set > - > > Key: AIRAVATA-1633 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1633 > Project: Airavata > Issue Type: Improvement > Components: GFac >Affects Versions: 0.15 >Reporter: Raminderjeet Singh >Assignee: Raminderjeet Singh > > If a queue name or other PBS parameter come empty, we should not generate > the tag. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AIRAVATA-1633) Add empty checks if a job property is not set
Raminderjeet Singh created AIRAVATA-1633: Summary: Add empty checks if a job property is not set Key: AIRAVATA-1633 URL: https://issues.apache.org/jira/browse/AIRAVATA-1633 Project: Airavata Issue Type: Improvement Components: GFac Affects Versions: 0.15 Reporter: Raminderjeet Singh Assignee: Raminderjeet Singh If a queue name or other PBS parameter come empty, we should not generate the tag. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
