date:20161111


[ 
https://issues.apache.org/jira/browse/AIRAVATA-2153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15658483#comment-15658483
 ] 

Eroma commented on AIRAVATA-2153:
-

Still the same saved comments are not available when viewed again

> Added comment to Gateway request is not available when the record is viewed 
> again
> -
>
> Key: AIRAVATA-2153
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2153
> Project: Airavata
>  Issue Type: Bug
>  Components: PGA PHP Web Gateway
> Environment: https://dev.scigap.org
>Reporter: Eroma
>Assignee: Nipurn Doshi
>
> Added comment to Gateway request is not available when the record is viewed 
> again.
> SciGaP admin viewed a gateway request and then added a comment and clicked 
> update gateway.
> 1. When SciGaP admin viewed the comment again it is not displayed in comment 
> section.
> 2. In DB table 'GATEWAY' the added comment is saved in 'DECLINED_REASON'.
> 3. Only added a comment and already the status in GATEWAY table is APPROVED.
> 4. For the gateway requested PI the status is showed as APPROVED. Added 
> comments are displayed there as well.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (AIRAVATA-2155) 'Deactivate Gateway' button should exists only for gateway requests which are approved.

2016-11-11 Thread Eroma (JIRA)


 [ 
https://issues.apache.org/jira/browse/AIRAVATA-2155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eroma closed AIRAVATA-2155.
---

tested and verified in
https://dev.scigap.org/

Now upon creating the tenant only 'Deactivate Gateway' appears.

> 'Deactivate Gateway' button should exists only for gateway requests which are 
> approved.
> ---
>
> Key: AIRAVATA-2155
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2155
> Project: Airavata
>  Issue Type: Bug
>  Components: PGA PHP Web Gateway
>Reporter: Eroma
>Assignee: Nipurn Doshi
>
> 'Deactivate Gateway' button should exists only for gateway requests which are 
> approved.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (AIRAVATA-2025) When clicked 'Approved' for a gateway request error exception thrown

2016-11-11 Thread Eroma (JIRA)


 [ 
https://issues.apache.org/jira/browse/AIRAVATA-2025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eroma closed AIRAVATA-2025.
---

tested and verified in
https://dev.scigap.org/

when a gateway request is submitted SciGaP admin can use 'Create Tenant' to 
create the gateway tenant in IS.
No error thrown. Domain is automatically added using the  airavata.

> When clicked 'Approved' for a gateway request error exception thrown
> 
>
> Key: AIRAVATA-2025
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2025
> Project: Airavata
>  Issue Type: Bug
>  Components: PGA PHP Web Gateway
>Affects Versions: 0.17-SNAPSHOT
>Reporter: Eroma
>Assignee: Nipurn Doshi
> Attachments: Screen Shot 2016-08-08 at 12.23.48 AM.png
>
>
> When clicked 'Approved' error exception thrown. This should be handled. If 
> the domain needs an extension we need to enforce at request creation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (AIRAVATA-2030) Cannot login to WSO2 IS using newly created gateways admin username and password

2016-11-11 Thread Eroma (JIRA)


 [ 
https://issues.apache.org/jira/browse/AIRAVATA-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eroma closed AIRAVATA-2030.
---

tested and verified in
https://dev.scigap.org/

Now the tenant get created successfully and can login to IS using the correct 
tenant username and password. No domain repeating as well.

> Cannot login to WSO2 IS using newly created gateways admin username and 
> password
> 
>
> Key: AIRAVATA-2030
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2030
> Project: Airavata
>  Issue Type: Bug
>  Components: PGA PHP Web Gateway
>Affects Versions: 0.17-SNAPSHOT
>Reporter: Eroma
>Assignee: Supun Chathuranga Nakandala
> Attachments: Screen Shot 2016-08-08 at 2.48.36 PM.png
>
>
> Cannot login to WSO2 IS using newly created gateways admin username and 
> password
> Admin username: NewGtwy2
> domain: chemistry.airavata
> When tried to login to IS gives the message
> Login failed! Please recheck the username and password and try again.
> Logged in as scigap admin and checked the admin username
> as per IS username has the domain as part of it.
> So the domain repeats.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AIRAVATA-2224) Contact email given for gateway requests page need to change

2016-11-11 Thread Eroma (JIRA)

Eroma created AIRAVATA-2224:
---

 Summary: Contact email given for gateway requests page need to 
change
 Key: AIRAVATA-2224
 URL: https://issues.apache.org/jira/browse/AIRAVATA-2224
 Project: Airavata
  Issue Type: Bug
  Components: PGA PHP Web Gateway
 Environment: https://dev.scigap.org/admin/dashboard
Reporter: Eroma
Assignee: Nipurn Doshi


Please change the existing email to h...@scigap.org. Currently existing 
cont...@scigap.org which is not the right one.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AIRAVATA-2163) optimize credential store data models

2016-11-11 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/AIRAVATA-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15658328#comment-15658328
 ] 

ASF GitHub Bot commented on AIRAVATA-2163:
--

Github user anujbhan closed the pull request at:

https://github.com/apache/airavata/pull/74


> optimize credential store data models
> -
>
> Key: AIRAVATA-2163
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2163
> Project: Airavata
>  Issue Type: Improvement
>  Components: Airavata API
> Environment: Development
>Reporter: Anuj Bhandar
>Assignee: Anuj Bhandar
>  Labels: GATask
> Fix For: 17
>
>
> This improvement is based on the following Pull request : 
> https://github.com/apache/airavata/pull/54.
> **Improvements agreed upon :** 
> Followings are few suggestions to improve your pull request.
> * We can do this in a better way by adding generic API method(to 
> AiravataAPIServer) like "getAllCredentialSummary" instead of adding API 
> method for each credential types eg: "getAllGatewaySSHPubKeysSummary" which 
> will return all the credential summary for that particular gatewayId. You may 
> be able to remove few redundant methods from Airavata API server.
> * Let's introduced one credential summary struct to all credential types, 
> how we differentiate is we have credential type enum field( SSH, PASSWD, CERT 
> etc ) in the credential summary thrift struct.
>  * Move credential data model thrift file to data model directory and 
> merge credential summary thrift file with it.
>  * Credential stubs still have date fields in generated thrift files, not 
> because your changes, but we need to fix it so remove it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] airavata issue #74: AIRAVATA-2163: Optimising the cred store data model

2016-11-11 Thread anujbhan

Github user anujbhan commented on the issue:

https://github.com/apache/airavata/pull/74
  
https://github.com/apache/airavata/pull/76, refer this pull request with 
resolved conflicts


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (AIRAVATA-2163) optimize credential store data models

2016-11-11 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/AIRAVATA-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15658327#comment-15658327
 ] 

ASF GitHub Bot commented on AIRAVATA-2163:
--

Github user anujbhan commented on the issue:

https://github.com/apache/airavata/pull/74
  
https://github.com/apache/airavata/pull/76, refer this pull request with 
resolved conflicts


> optimize credential store data models
> -
>
> Key: AIRAVATA-2163
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2163
> Project: Airavata
>  Issue Type: Improvement
>  Components: Airavata API
> Environment: Development
>Reporter: Anuj Bhandar
>Assignee: Anuj Bhandar
>  Labels: GATask
> Fix For: 17
>
>
> This improvement is based on the following Pull request : 
> https://github.com/apache/airavata/pull/54.
> **Improvements agreed upon :** 
> Followings are few suggestions to improve your pull request.
> * We can do this in a better way by adding generic API method(to 
> AiravataAPIServer) like "getAllCredentialSummary" instead of adding API 
> method for each credential types eg: "getAllGatewaySSHPubKeysSummary" which 
> will return all the credential summary for that particular gatewayId. You may 
> be able to remove few redundant methods from Airavata API server.
> * Let's introduced one credential summary struct to all credential types, 
> how we differentiate is we have credential type enum field( SSH, PASSWD, CERT 
> etc ) in the credential summary thrift struct.
>  * Move credential data model thrift file to data model directory and 
> merge credential summary thrift file with it.
>  * Credential stubs still have date fields in generated thrift files, not 
> because your changes, but we need to fix it so remove it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] airavata pull request #74: AIRAVATA-2163: Optimising the cred store data mod...

2016-11-11 Thread anujbhan

Github user anujbhan closed the pull request at:

https://github.com/apache/airavata/pull/74


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] airavata pull request #76: Optimise cred store data models

2016-11-11 Thread anujbhan

GitHub user anujbhan opened a pull request:

https://github.com/apache/airavata/pull/76

Optimise cred store data models

This pull request resolves the merge conflicts in 
https://github.com/apache/airavata/pull/74 and also adds few incremental 
changes to credential-storestub pom file to remove date fields in auto-gen files

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/anujbhan/airavata optimise-cred-pr-rc

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/airavata/pull/76.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #76


commit ef2966ff8f2c7fb4ebb768ac4b72aadb193590a9
Author: Anuj Bhandar 
Date:   2016-11-04T17:26:32Z

AIRAVATA-2163: Optimising the cred store data model

commit 8bdd26fc724a61d07b2a0cfe7123ccbd303a1f27
Author: Anuj Bhandar 
Date:   2016-11-04T19:59:51Z

correcting exception handling in Airavata API




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Closed] (AIRAVATA-1654) Document all possible job state mismatches in Airavata.

2016-11-11 Thread Eroma (JIRA)


 [ 
https://issues.apache.org/jira/browse/AIRAVATA-1654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eroma closed AIRAVATA-1654.
---

> Document all possible job state mismatches in Airavata. 
> 
>
> Key: AIRAVATA-1654
> URL: https://issues.apache.org/jira/browse/AIRAVATA-1654
> Project: Airavata
>  Issue Type: Sub-task
>Reporter: Eroma
>Assignee: Shameera Rathnayaka
>
> Looking at existing job states and messages in Airaveata & evaluating what 
> are the options we have for job monitoring.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (AIRAVATA-1568) Integrate XBAYA with Airavata Workflow Engine/ Workflow Interpreter

2016-11-11 Thread Eroma (JIRA)


 [ 
https://issues.apache.org/jira/browse/AIRAVATA-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eroma closed AIRAVATA-1568.
---

> Integrate XBAYA with Airavata Workflow Engine/ Workflow Interpreter
> ---
>
> Key: AIRAVATA-1568
> URL: https://issues.apache.org/jira/browse/AIRAVATA-1568
> Project: Airavata
>  Issue Type: Task
>  Components: Workflow Interpreter
>Reporter: Eroma
>Assignee: Shameera Rathnayaka
> Fix For: 0.15
>
>
> Implementation on new Workflow Engine. Integrating Workflow engine with XBAYA



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (AIRAVATA-1540) XBaya GUI froze when an experiment is launched. Killed the XBaya process but didn't work

2016-11-11 Thread Eroma (JIRA)


 [ 
https://issues.apache.org/jira/browse/AIRAVATA-1540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eroma closed AIRAVATA-1540.
---

XBAYA not integrated and update with Airavata 0.16. Hence this is not a valid 
feature/functional scenario any longer.

> XBaya GUI froze when an experiment is launched. Killed the XBaya process but 
> didn't work
> 
>
> Key: AIRAVATA-1540
> URL: https://issues.apache.org/jira/browse/AIRAVATA-1540
> Project: Airavata
>  Issue Type: Bug
>  Components: XBaya
> Environment: Ran on localhost
>Reporter: Eroma
>Assignee: Shameera Rathnayaka
> Fix For: 0.15
>
> Attachments: Screen Shot 2014-12-02 at 2.07.25 PM.png
>
>
> In XBAYA GUI entered all information and clicked on Run to execute the launch 
> experiment.
> Experiment didn't get launched or completed (no messages on monitoring window 
> in XBAYA GUI)
> XBAYA GUI sort of frozen and killed XBAYA process and ran it again.
> In GUI when tried to load the registered applications got the pop up window 
> attached. GUI is frozen



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (AIRAVATA-2190) User A shared a single experiment with User B, read access. Project is also shared now with User B.

2016-11-11 Thread Eroma (JIRA)


 [ 
https://issues.apache.org/jira/browse/AIRAVATA-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eroma closed AIRAVATA-2190.
---

tested and verified in
https://dev.seagrid.org

> User A shared a single experiment with User B, read access. Project is also 
> shared now with User B.
> ---
>
> Key: AIRAVATA-2190
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2190
> Project: Airavata
>  Issue Type: Bug
>  Components: PGA PHP Web Gateway
> Environment: https://dev.seagrid.org
>Reporter: Eroma
>Assignee: Marcus Christie
> Fix For: 0.17-SNAPSHOT
>
>
> Steps
> 1. User A shared a single experiment with user B. With read access
> 2. User B now has access to User A's project which experiment belongs
> 3. User B can create new experiments under the Project.
> 4. User B can cancel the shared experiment irrespective of having only read 
> access
> 5. user B can clone the shared experiment and create a new experiment under 
> the same project and remove sharing of the project owner. 
> 6. Original user A cannot see the cloned experiment under his own project
> User B should not be able to create any experiments under the project the 
> shared experiment belongs. 
> No should be able to cancel the shared experiment, only has read access.
> If cloned should create it under own project; not with user A's project



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (AIRAVATA-2196) Both users with 'Read' access and 'Write' access should NOT have the same set of privileges in PGA

2016-11-11 Thread Eroma (JIRA)


 [ 
https://issues.apache.org/jira/browse/AIRAVATA-2196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eroma closed AIRAVATA-2196.
---

tested and verified in 
https://dev.seagrid.org/

When experiments shared with READ access
Can clone and create a new experiment under own project.
Can download input and outputs

When experiments shared with Write access
Can cancel
Can launch
Can download input and outputs
Can clone and create a new one under own project if the project is not shared 
with write access

Project Write access
Can change name and description

Project with Read access 
Only view

With any access cannot do any changes to the shared user list unless its the 
owner.




> Both users with 'Read' access and 'Write' access should NOT have the same set 
> of privileges in PGA
> --
>
> Key: AIRAVATA-2196
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2196
> Project: Airavata
>  Issue Type: Bug
>  Components: PGA PHP Web Gateway
>Reporter: Eroma
>Assignee: Marcus Christie
> Fix For: 0.17-SNAPSHOT
>
>
> Currently when sharing experiments and projects 'read' access and 'write' 
> access provides same set of privileges for users.
> Please review the requirements in 
> https://docs.google.com/document/d/1PVWFNDmbugpwUbcla9LiNx_3SuYGl-_4WjiJ7rGkfl8/edit
>  and modify accordingly.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AIRAVATA-2195) Shared user will end up with an experiment which he has no permission to view

2016-11-11 Thread Marcus Christie (JIRA)


[ 
https://issues.apache.org/jira/browse/AIRAVATA-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15658128#comment-15658128
 ] 

Marcus Christie commented on AIRAVATA-2195:
---

This is basically done. I just need to test with the changes Supun added in 
AIRAVATA-2185 once they get deployed.

> Shared user will end up with an experiment which he has no permission to view
> -
>
> Key: AIRAVATA-2195
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2195
> Project: Airavata
>  Issue Type: Bug
>  Components: PGA PHP Web Gateway
> Environment: https://dev.seagrid.org
>Reporter: Eroma
>Assignee: Marcus Christie
> Fix For: 0.17-SNAPSHOT
>
> Attachments: Screen Shot 2016-10-25 at 3.04.35 PM.png, 
> project_owner.png
>
>
> Steps;
> 1. User A creates a a project and shares it with user B and user C
> 2. user A creates an experiment which is shared with both users B and C
> 3. User C clones and creates a new experiment and removes User A from the 
> experiment. Only the experiment is shared with usr C
> 4. User A removes the sharing from both users at project level.
> 5. Both users cannot view the project now.
> 6. Both users can see the cloned experiment in Experiment Browse but cannot 
> view the experiment details. Throws exception attached
> First if using owners project to create experiments should not be able to 
> remove the owner from the experiment or the project
> Secondly if permission is denied should handle with correct error messages. 
> h5. TODO
> * Add the notion of an indirect or cascading owner to the sharing dialog and 
> display them like the [^project_owner.png] screenshot attached
> * also show the indirect owner in the display of shared with users



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (AIRAVATA-2080) When tried to view the project summary gives error exception in dev seagrid portal

2016-11-11 Thread Eroma (JIRA)


 [ 
https://issues.apache.org/jira/browse/AIRAVATA-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eroma closed AIRAVATA-2080.
---

tested and verified in 
https://dev.seagrid.org/

Project summary can be viewed successfully. Even with shared experiment with 
other users.

> When tried to view the project summary gives error exception in dev seagrid 
> portal
> --
>
> Key: AIRAVATA-2080
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2080
> Project: Airavata
>  Issue Type: Bug
>  Components: PGA PHP Web Gateway
>Affects Versions: 0.17-SNAPSHOT
>Reporter: Eroma
>Assignee: Supun Chathuranga Nakandala
> Attachments: Screen Shot 2016-09-02 at 2.26.29 PM.png, Screen Shot 
> 2016-10-05 at 3.02.50 PM.png
>
>
> error exception 
> Error while retrieving the job statuses. More info : Internal error 
> processing getJobStatuses (View: 
> /var/www/portals/dev-seagrid/app/views/project/summary.blade.php)
> when tried to view project summary. This project was created today and it has 
> experiment which has no job status in it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (AIRAVATA-2021) User shared only a single experiment; project also got shared with the new user

2016-11-11 Thread Eroma (JIRA)


 [ 
https://issues.apache.org/jira/browse/AIRAVATA-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eroma closed AIRAVATA-2021.
---

tested and verified in
https://dev.seagrid.org/

When user A shared a single experiment with User B, only the experiment got 
shared. Not the project belonging to user A.

> User shared only a single experiment; project also got shared with the new 
> user
> ---
>
> Key: AIRAVATA-2021
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2021
> Project: Airavata
>  Issue Type: Bug
>  Components: PGA PHP Web Gateway
>Affects Versions: 0.17-SNAPSHOT
> Environment: https://dev.seagrid.org
>Reporter: Eroma
>Assignee: Supun Chathuranga Nakandala
>
> Steps;
> 1. User A (gateway-user role) shared a single experiment with user B (admin 
> role)
> 2. User B logs in
> 3. In Project Browse it shows as Usr A shared the project as well
> 4. Experiment also displayed in Experiment browse.
> 5. When only a experiment is shared only the Experiment browse should 
> display. Should NOT share the whole project.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (AIRAVATA-2120) Application deployments are merged together when tried to create a new deployment in same resource using same app module

2016-11-11 Thread Eroma (JIRA)


 [ 
https://issues.apache.org/jira/browse/AIRAVATA-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eroma closed AIRAVATA-2120.
---

> Application deployments are merged together when tried to create a new 
> deployment in same resource using same app module
> 
>
> Key: AIRAVATA-2120
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2120
> Project: Airavata
>  Issue Type: Bug
>  Components: PGA PHP Web Gateway
> Environment: https://dev.seagrid.org
>Reporter: Eroma
>Assignee: Supun Chathuranga Nakandala
>
> Single compute resource holding two separate deployments of the same 
> application module (2 separate application interfaces) results merge of the 
> old and the new deployment.
> Updates the existing merging both pre job commands, etc. 
> Abaqus has two separate application interfaces using same module. When tried 
> to deploy the new deployment in Comet, PGA allowed me to create a new 
> deployment but when revisited there is only one merged deployment in Comet 
> instead of two separate ones.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Jenkins build is back to stable : airavata-dev #1300

2016-11-11 Thread Apache Jenkins Server

See

Jenkins build is back to stable : airavata-dev » Airavata Registry Core #1300

2016-11-11 Thread Apache Jenkins Server

See

[jira] [Updated] (AIRAVATA-2193) When projects of other users are available for experiment creation cannot figure out to whom it belongs

2016-11-11 Thread Marcus Christie (JIRA)


 [ 
https://issues.apache.org/jira/browse/AIRAVATA-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Marcus Christie updated AIRAVATA-2193:
--
Assignee: Eroma  (was: Marcus Christie)

> When projects of other users are available for experiment creation cannot 
> figure out to whom it belongs
> ---
>
> Key: AIRAVATA-2193
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2193
> Project: Airavata
>  Issue Type: Bug
>  Components: PGA PHP Web Gateway
> Environment: https://dev.seagrid.org
>Reporter: Eroma
>Assignee: Eroma
> Fix For: 0.17-SNAPSHOT
>
> Attachments: screenshot-1.png
>
>
> Currently in Experiment creation we only show the project name. When projects 
> are shared (with write access), the shared user can use the project and make 
> new experiments. If both users has projects with same name (E.g: Default 
> Project) user will not be able to identify the correct project.
> This gets worse if several has shared their Default Project with each other. 
> We need to feature of displaying the owner of a project at experiment 
> creation. When selecting the project.
> h3. TODO
> * (/) update project selection at experiment creation
> * (/) update project selection when cloning an experiment



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AIRAVATA-2193) When projects of other users are available for experiment creation cannot figure out to whom it belongs

2016-11-11 Thread Marcus Christie (JIRA)


[ 
https://issues.apache.org/jira/browse/AIRAVATA-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15657909#comment-15657909
 ] 

Marcus Christie commented on AIRAVATA-2193:
---

This is on dev.seagrid.org and should be fixed now. Can you please resolve this 
issue?

> When projects of other users are available for experiment creation cannot 
> figure out to whom it belongs
> ---
>
> Key: AIRAVATA-2193
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2193
> Project: Airavata
>  Issue Type: Bug
>  Components: PGA PHP Web Gateway
> Environment: https://dev.seagrid.org
>Reporter: Eroma
>Assignee: Eroma
> Fix For: 0.17-SNAPSHOT
>
> Attachments: screenshot-1.png
>
>
> Currently in Experiment creation we only show the project name. When projects 
> are shared (with write access), the shared user can use the project and make 
> new experiments. If both users has projects with same name (E.g: Default 
> Project) user will not be able to identify the correct project.
> This gets worse if several has shared their Default Project with each other. 
> We need to feature of displaying the owner of a project at experiment 
> creation. When selecting the project.
> h3. TODO
> * (/) update project selection at experiment creation
> * (/) update project selection when cloning an experiment



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AIRAVATA-2193) When projects of other users are available for experiment creation cannot figure out to whom it belongs

2016-11-11 Thread Marcus Christie (JIRA)


 [ 
https://issues.apache.org/jira/browse/AIRAVATA-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Marcus Christie updated AIRAVATA-2193:
--
Description: 
Currently in Experiment creation we only show the project name. When projects 
are shared (with write access), the shared user can use the project and make 
new experiments. If both users has projects with same name (E.g: Default 
Project) user will not be able to identify the correct project.

This gets worse if several has shared their Default Project with each other. We 
need to feature of displaying the owner of a project at experiment creation. 
When selecting the project.


h3. TODO
* (/) update project selection at experiment creation
* (/) update project selection when cloning an experiment

  was:
Currently in Experiment creation we only show the project name. When projects 
are shared (with write access), the shared user can use the project and make 
new experiments. If both users has projects with same name (E.g: Default 
Project) user will not be able to identify the correct project.

This gets worse if several has shared their Default Project with each other. We 
need to feature of displaying the owner of a project at experiment creation. 
When selecting the project.


h3. TODO
* update project selection at experiment creation
* update project selection when cloning an experiment


> When projects of other users are available for experiment creation cannot 
> figure out to whom it belongs
> ---
>
> Key: AIRAVATA-2193
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2193
> Project: Airavata
>  Issue Type: Bug
>  Components: PGA PHP Web Gateway
> Environment: https://dev.seagrid.org
>Reporter: Eroma
>Assignee: Marcus Christie
> Fix For: 0.17-SNAPSHOT
>
> Attachments: screenshot-1.png
>
>
> Currently in Experiment creation we only show the project name. When projects 
> are shared (with write access), the shared user can use the project and make 
> new experiments. If both users has projects with same name (E.g: Default 
> Project) user will not be able to identify the correct project.
> This gets worse if several has shared their Default Project with each other. 
> We need to feature of displaying the owner of a project at experiment 
> creation. When selecting the project.
> h3. TODO
> * (/) update project selection at experiment creation
> * (/) update project selection when cloning an experiment



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (AIRAVATA-2212) Experiment Auto Refresh may try to reload the page while reloading the page

2016-11-11 Thread Marcus Christie (JIRA)


 [ 
https://issues.apache.org/jira/browse/AIRAVATA-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Marcus Christie resolved AIRAVATA-2212.
---
Resolution: Fixed

> Experiment Auto Refresh may try to reload the page while reloading the page
> ---
>
> Key: AIRAVATA-2212
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2212
> Project: Airavata
>  Issue Type: Bug
>Reporter: Marcus Christie
>Assignee: Marcus Christie
> Fix For: 0.17-SNAPSHOT
>
>
> The Experiment Auto Refresh feature has a bug that occurs when it takes more 
> than about 3 seconds to load the experiment summary. Experiment Auto Refresh 
> runs an Ajax request every 3 seconds to check to see if the experiment status 
> has changed. If the experiment status has changed it tries to reload the 
> page. However, it keeps checking every 3 seconds and it is possible for the 
> summary page to
> * check to see if the experiment status has changed
> * start reloading the page
> * check a second time to see if the experiment status has changed
> * start reloading the page a second time
> * etc.
> For [~eroma_a] the summary page basically got stuck in this loop and never 
> refreshed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (AIRAVATA-2212) Experiment Auto Refresh may try to reload the page while reloading the page

2016-11-11 Thread Marcus Christie (JIRA)


 [ 
https://issues.apache.org/jira/browse/AIRAVATA-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Marcus Christie closed AIRAVATA-2212.
-

> Experiment Auto Refresh may try to reload the page while reloading the page
> ---
>
> Key: AIRAVATA-2212
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2212
> Project: Airavata
>  Issue Type: Bug
>Reporter: Marcus Christie
>Assignee: Marcus Christie
> Fix For: 0.17-SNAPSHOT
>
>
> The Experiment Auto Refresh feature has a bug that occurs when it takes more 
> than about 3 seconds to load the experiment summary. Experiment Auto Refresh 
> runs an Ajax request every 3 seconds to check to see if the experiment status 
> has changed. If the experiment status has changed it tries to reload the 
> page. However, it keeps checking every 3 seconds and it is possible for the 
> summary page to
> * check to see if the experiment status has changed
> * start reloading the page
> * check a second time to see if the experiment status has changed
> * start reloading the page a second time
> * etc.
> For [~eroma_a] the summary page basically got stuck in this loop and never 
> refreshed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Reopened] (AIRAVATA-2212) Experiment Auto Refresh may try to reload the page while reloading the page

2016-11-11 Thread Marcus Christie (JIRA)


 [ 
https://issues.apache.org/jira/browse/AIRAVATA-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Marcus Christie reopened AIRAVATA-2212:
---

> Experiment Auto Refresh may try to reload the page while reloading the page
> ---
>
> Key: AIRAVATA-2212
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2212
> Project: Airavata
>  Issue Type: Bug
>Reporter: Marcus Christie
>Assignee: Marcus Christie
> Fix For: 0.17-SNAPSHOT
>
>
> The Experiment Auto Refresh feature has a bug that occurs when it takes more 
> than about 3 seconds to load the experiment summary. Experiment Auto Refresh 
> runs an Ajax request every 3 seconds to check to see if the experiment status 
> has changed. If the experiment status has changed it tries to reload the 
> page. However, it keeps checking every 3 seconds and it is possible for the 
> summary page to
> * check to see if the experiment status has changed
> * start reloading the page
> * check a second time to see if the experiment status has changed
> * start reloading the page a second time
> * etc.
> For [~eroma_a] the summary page basically got stuck in this loop and never 
> refreshed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AIRAVATA-2212) Experiment Auto Refresh may try to reload the page while reloading the page

2016-11-11 Thread Marcus Christie (JIRA)


 [ 
https://issues.apache.org/jira/browse/AIRAVATA-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Marcus Christie updated AIRAVATA-2212:
--
Fix Version/s: 0.17-SNAPSHOT

> Experiment Auto Refresh may try to reload the page while reloading the page
> ---
>
> Key: AIRAVATA-2212
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2212
> Project: Airavata
>  Issue Type: Bug
>Reporter: Marcus Christie
>Assignee: Marcus Christie
> Fix For: 0.17-SNAPSHOT
>
>
> The Experiment Auto Refresh feature has a bug that occurs when it takes more 
> than about 3 seconds to load the experiment summary. Experiment Auto Refresh 
> runs an Ajax request every 3 seconds to check to see if the experiment status 
> has changed. If the experiment status has changed it tries to reload the 
> page. However, it keeps checking every 3 seconds and it is possible for the 
> summary page to
> * check to see if the experiment status has changed
> * start reloading the page
> * check a second time to see if the experiment status has changed
> * start reloading the page a second time
> * etc.
> For [~eroma_a] the summary page basically got stuck in this loop and never 
> refreshed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (AIRAVATA-2212) Experiment Auto Refresh may try to reload the page while reloading the page

2016-11-11 Thread Marcus Christie (JIRA)


 [ 
https://issues.apache.org/jira/browse/AIRAVATA-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Marcus Christie resolved AIRAVATA-2212.
---
Resolution: Fixed

> Experiment Auto Refresh may try to reload the page while reloading the page
> ---
>
> Key: AIRAVATA-2212
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2212
> Project: Airavata
>  Issue Type: Bug
>Reporter: Marcus Christie
>Assignee: Marcus Christie
>
> The Experiment Auto Refresh feature has a bug that occurs when it takes more 
> than about 3 seconds to load the experiment summary. Experiment Auto Refresh 
> runs an Ajax request every 3 seconds to check to see if the experiment status 
> has changed. If the experiment status has changed it tries to reload the 
> page. However, it keeps checking every 3 seconds and it is possible for the 
> summary page to
> * check to see if the experiment status has changed
> * start reloading the page
> * check a second time to see if the experiment status has changed
> * start reloading the page a second time
> * etc.
> For [~eroma_a] the summary page basically got stuck in this loop and never 
> refreshed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (AIRAVATA-2212) Experiment Auto Refresh may try to reload the page while reloading the page

2016-11-11 Thread Marcus Christie (JIRA)


 [ 
https://issues.apache.org/jira/browse/AIRAVATA-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Marcus Christie closed AIRAVATA-2212.
-

> Experiment Auto Refresh may try to reload the page while reloading the page
> ---
>
> Key: AIRAVATA-2212
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2212
> Project: Airavata
>  Issue Type: Bug
>Reporter: Marcus Christie
>Assignee: Marcus Christie
>
> The Experiment Auto Refresh feature has a bug that occurs when it takes more 
> than about 3 seconds to load the experiment summary. Experiment Auto Refresh 
> runs an Ajax request every 3 seconds to check to see if the experiment status 
> has changed. If the experiment status has changed it tries to reload the 
> page. However, it keeps checking every 3 seconds and it is possible for the 
> summary page to
> * check to see if the experiment status has changed
> * start reloading the page
> * check a second time to see if the experiment status has changed
> * start reloading the page a second time
> * etc.
> For [~eroma_a] the summary page basically got stuck in this loop and never 
> refreshed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (AIRAVATA-2080) When tried to view the project summary gives error exception in dev seagrid portal

2016-11-11 Thread Supun Chathuranga Nakandala (JIRA)


 [ 
https://issues.apache.org/jira/browse/AIRAVATA-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Supun Chathuranga Nakandala resolved AIRAVATA-2080.
---
Resolution: Fixed

> When tried to view the project summary gives error exception in dev seagrid 
> portal
> --
>
> Key: AIRAVATA-2080
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2080
> Project: Airavata
>  Issue Type: Bug
>  Components: PGA PHP Web Gateway
>Affects Versions: 0.17-SNAPSHOT
>Reporter: Eroma
>Assignee: Supun Chathuranga Nakandala
> Attachments: Screen Shot 2016-09-02 at 2.26.29 PM.png, Screen Shot 
> 2016-10-05 at 3.02.50 PM.png
>
>
> error exception 
> Error while retrieving the job statuses. More info : Internal error 
> processing getJobStatuses (View: 
> /var/www/portals/dev-seagrid/app/views/project/summary.blade.php)
> when tried to view project summary. This project was created today and it has 
> experiment which has no job status in it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AIRAVATA-2015) When a gateway user shares a project or an experiment have a notification sent

2016-11-11 Thread Supun Chathuranga Nakandala (JIRA)


[ 
https://issues.apache.org/jira/browse/AIRAVATA-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15657848#comment-15657848
 ] 

Supun Chathuranga Nakandala commented on AIRAVATA-2015:
---

[~eroma_a] Can't we handle at the PGA ?

> When a gateway user shares a project or an experiment have a notification sent
> --
>
> Key: AIRAVATA-2015
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2015
> Project: Airavata
>  Issue Type: Bug
>  Components: PGA PHP Web Gateway
>Affects Versions: 0.17-SNAPSHOT
>Reporter: Eroma
>Assignee: Supun Chathuranga Nakandala
>Priority: Minor
>
> When a project or experiment shared, unshared please notify the other person. 
> It would be ideal if we also could notify the owner when any changes take 
> place in project and experiment by shared users as well.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (AIRAVATA-1927) In SEAGrid desktop client NanoCAD window 'Import Structure' screen is not opening

2016-11-11 Thread Eroma (JIRA)


 [ 
https://issues.apache.org/jira/browse/AIRAVATA-1927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eroma closed AIRAVATA-1927.
---

tested and verified in
production SEAGrid desktop client.

Now the import structure opens when clicked on Structure.


> In SEAGrid desktop client NanoCAD window 'Import Structure' screen is not 
> opening
> -
>
> Key: AIRAVATA-1927
> URL: https://issues.apache.org/jira/browse/AIRAVATA-1927
> Project: Airavata
>  Issue Type: Bug
>Affects Versions: 0.16
> Environment: https://dev.seagrid.org
>Reporter: Eroma
>Assignee: Supun Chathuranga Nakandala
> Fix For: 0.16
>
>
> In NanoCAD window when clicked button 'structure' the 'Import Structure' 
> pop-up window does not open.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Jenkins build is still unstable: airavata-dev » Airavata Registry Core #1299

2016-11-11 Thread Apache Jenkins Server

See

Jenkins build is still unstable: airavata-dev #1299

2016-11-11 Thread Apache Jenkins Server

See

[jira] [Updated] (AIRAVATA-2064) In ultrascan production PGA cannot view outputs. Getting the attached error

2016-11-11 Thread Supun Chathuranga Nakandala (JIRA)


 [ 
https://issues.apache.org/jira/browse/AIRAVATA-2064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Supun Chathuranga Nakandala updated AIRAVATA-2064:
--
Assignee: Eroma  (was: Supun Chathuranga Nakandala)

> In ultrascan production PGA cannot view outputs. Getting the attached error
> ---
>
> Key: AIRAVATA-2064
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2064
> Project: Airavata
>  Issue Type: Bug
>  Components: PGA PHP Web Gateway
>Affects Versions: 0.16
>Reporter: Eroma
>Assignee: Eroma
> Attachments: Screen Shot 2016-08-24 at 1.12.26 PM.png
>
>
> In production ultrascan PGA (https://ultrascan.scigap.org) getting error 'The 
> file 
> "/var/www/portals/gateway-user-data/ultrascan/Ero2016/Aug_24_2016/SLM2_US_Stampede_08_24_13_09_401472058589/Ultrascan.stderr"
>  does not exist' when tried to view the outputs.
> The actual data folder does not contain the output file and it could be the 
> reason for the exception. But it should be handled gracefully. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (AIRAVATA-2120) Application deployments are merged together when tried to create a new deployment in same resource using same app module

2016-11-11 Thread Supun Chathuranga Nakandala (JIRA)


 [ 
https://issues.apache.org/jira/browse/AIRAVATA-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Supun Chathuranga Nakandala resolved AIRAVATA-2120.
---
Resolution: Won't Fix

> Application deployments are merged together when tried to create a new 
> deployment in same resource using same app module
> 
>
> Key: AIRAVATA-2120
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2120
> Project: Airavata
>  Issue Type: Bug
>  Components: PGA PHP Web Gateway
> Environment: https://dev.seagrid.org
>Reporter: Eroma
>Assignee: Supun Chathuranga Nakandala
>
> Single compute resource holding two separate deployments of the same 
> application module (2 separate application interfaces) results merge of the 
> old and the new deployment.
> Updates the existing merging both pre job commands, etc. 
> Abaqus has two separate application interfaces using same module. When tried 
> to deploy the new deployment in Comet, PGA allowed me to create a new 
> deployment but when revisited there is only one merged deployment in Comet 
> instead of two separate ones.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Jenkins build is still unstable: airavata-dev » Airavata Registry Core #1298

2016-11-11 Thread Apache Jenkins Server

See

Jenkins build is still unstable: airavata-dev #1298

2016-11-11 Thread Apache Jenkins Server

See

[jira] [Resolved] (AIRAVATA-2175) Prevent changing project owner

2016-11-11 Thread Supun Chathuranga Nakandala (JIRA)


 [ 
https://issues.apache.org/jira/browse/AIRAVATA-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Supun Chathuranga Nakandala resolved AIRAVATA-2175.
---
Resolution: Fixed

> Prevent changing project owner
> --
>
> Key: AIRAVATA-2175
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2175
> Project: Airavata
>  Issue Type: Bug
>  Components: Airavata API
>Reporter: Marcus Christie
>Assignee: Supun Chathuranga Nakandala
>
> Currently Airavata.updateProject allows updating the owner of the project.  
> This was causing the owner of a shared project to change to whoever last 
> edited it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AIRAVATA-2175) Prevent changing project owner

2016-11-11 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/AIRAVATA-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15657609#comment-15657609
 ] 

ASF subversion and git services commented on AIRAVATA-2175:
---

Commit c456337f23c6833779d454789ee698e0e87b2b24 in airavata's branch 
refs/heads/develop from scnakandala
[ https://git-wip-us.apache.org/repos/asf?p=airavata.git;h=c456337 ]

fixing AIRAVATA-2175 : Prevent changing project owner


> Prevent changing project owner
> --
>
> Key: AIRAVATA-2175
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2175
> Project: Airavata
>  Issue Type: Bug
>  Components: Airavata API
>Reporter: Marcus Christie
>Assignee: Supun Chathuranga Nakandala
>
> Currently Airavata.updateProject allows updating the owner of the project.  
> This was causing the owner of a shared project to change to whoever last 
> edited it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AIRAVATA-2212) Experiment Auto Refresh may try to reload the page while reloading the page

2016-11-11 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/AIRAVATA-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15657590#comment-15657590
 ] 

ASF subversion and git services commented on AIRAVATA-2212:
---

Commit 3910260e58b3e1c5c554bada3dd33ded9e7fd403 in airavata-php-gateway's 
branch refs/heads/develop from [~marcuschristie]
[ https://git-wip-us.apache.org/repos/asf?p=airavata-php-gateway.git;h=3910260 ]

AIRAVATA-2212 Using setInterval so status check is turned back on

The way it was implemented with setTimeout the status checking
(autoRefresh) wouldn't start again once it was toggled back on. I
switched to setInterval since it is easier to just check the autoRefresh
flag every 3 seconds.


> Experiment Auto Refresh may try to reload the page while reloading the page
> ---
>
> Key: AIRAVATA-2212
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2212
> Project: Airavata
>  Issue Type: Bug
>Reporter: Marcus Christie
>Assignee: Marcus Christie
>
> The Experiment Auto Refresh feature has a bug that occurs when it takes more 
> than about 3 seconds to load the experiment summary. Experiment Auto Refresh 
> runs an Ajax request every 3 seconds to check to see if the experiment status 
> has changed. If the experiment status has changed it tries to reload the 
> page. However, it keeps checking every 3 seconds and it is possible for the 
> summary page to
> * check to see if the experiment status has changed
> * start reloading the page
> * check a second time to see if the experiment status has changed
> * start reloading the page a second time
> * etc.
> For [~eroma_a] the summary page basically got stuck in this loop and never 
> refreshed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AIRAVATA-2193) When projects of other users are available for experiment creation cannot figure out to whom it belongs

2016-11-11 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/AIRAVATA-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15657594#comment-15657594
 ] 

ASF GitHub Bot commented on AIRAVATA-2193:
--

Github user asfgit closed the pull request at:

https://github.com/apache/airavata-php-gateway/pull/37


> When projects of other users are available for experiment creation cannot 
> figure out to whom it belongs
> ---
>
> Key: AIRAVATA-2193
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2193
> Project: Airavata
>  Issue Type: Bug
>  Components: PGA PHP Web Gateway
> Environment: https://dev.seagrid.org
>Reporter: Eroma
>Assignee: Marcus Christie
> Fix For: 0.17-SNAPSHOT
>
> Attachments: screenshot-1.png
>
>
> Currently in Experiment creation we only show the project name. When projects 
> are shared (with write access), the shared user can use the project and make 
> new experiments. If both users has projects with same name (E.g: Default 
> Project) user will not be able to identify the correct project.
> This gets worse if several has shared their Default Project with each other. 
> We need to feature of displaying the owner of a project at experiment 
> creation. When selecting the project.
> h3. TODO
> * update project selection at experiment creation
> * update project selection when cloning an experiment



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AIRAVATA-2212) Experiment Auto Refresh may try to reload the page while reloading the page

2016-11-11 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/AIRAVATA-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15657592#comment-15657592
 ] 

ASF subversion and git services commented on AIRAVATA-2212:
---

Commit de3ac07ad5bfc56044a28b1f3ce6fb80cdc3c144 in airavata-php-gateway's 
branch refs/heads/develop from scnakandala
[ https://git-wip-us.apache.org/repos/asf?p=airavata-php-gateway.git;h=de3ac07 ]

Merge branch 'AIRAVATA-2212-autorefresh-prevents-page-from-loading' of 
https://github.com/machristie/airavata-php-gateway into develop


> Experiment Auto Refresh may try to reload the page while reloading the page
> ---
>
> Key: AIRAVATA-2212
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2212
> Project: Airavata
>  Issue Type: Bug
>Reporter: Marcus Christie
>Assignee: Marcus Christie
>
> The Experiment Auto Refresh feature has a bug that occurs when it takes more 
> than about 3 seconds to load the experiment summary. Experiment Auto Refresh 
> runs an Ajax request every 3 seconds to check to see if the experiment status 
> has changed. If the experiment status has changed it tries to reload the 
> page. However, it keeps checking every 3 seconds and it is possible for the 
> summary page to
> * check to see if the experiment status has changed
> * start reloading the page
> * check a second time to see if the experiment status has changed
> * start reloading the page a second time
> * etc.
> For [~eroma_a] the summary page basically got stuck in this loop and never 
> refreshed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AIRAVATA-2193) When projects of other users are available for experiment creation cannot figure out to whom it belongs

2016-11-11 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/AIRAVATA-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15657591#comment-15657591
 ] 

ASF subversion and git services commented on AIRAVATA-2193:
---

Commit 9faea85c25360f3df18eb967fcc2f83c764d781d in airavata-php-gateway's 
branch refs/heads/develop from [~marcuschristie]
[ https://git-wip-us.apache.org/repos/asf?p=airavata-php-gateway.git;h=9faea85 ]

AIRAVATA-2193 Distinguish projects owned by other users


> When projects of other users are available for experiment creation cannot 
> figure out to whom it belongs
> ---
>
> Key: AIRAVATA-2193
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2193
> Project: Airavata
>  Issue Type: Bug
>  Components: PGA PHP Web Gateway
> Environment: https://dev.seagrid.org
>Reporter: Eroma
>Assignee: Marcus Christie
> Fix For: 0.17-SNAPSHOT
>
> Attachments: screenshot-1.png
>
>
> Currently in Experiment creation we only show the project name. When projects 
> are shared (with write access), the shared user can use the project and make 
> new experiments. If both users has projects with same name (E.g: Default 
> Project) user will not be able to identify the correct project.
> This gets worse if several has shared their Default Project with each other. 
> We need to feature of displaying the owner of a project at experiment 
> creation. When selecting the project.
> h3. TODO
> * update project selection at experiment creation
> * update project selection when cloning an experiment



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AIRAVATA-2212) Experiment Auto Refresh may try to reload the page while reloading the page

2016-11-11 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/AIRAVATA-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15657593#comment-15657593
 ] 

ASF GitHub Bot commented on AIRAVATA-2212:
--

Github user asfgit closed the pull request at:

https://github.com/apache/airavata-php-gateway/pull/36


> Experiment Auto Refresh may try to reload the page while reloading the page
> ---
>
> Key: AIRAVATA-2212
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2212
> Project: Airavata
>  Issue Type: Bug
>Reporter: Marcus Christie
>Assignee: Marcus Christie
>
> The Experiment Auto Refresh feature has a bug that occurs when it takes more 
> than about 3 seconds to load the experiment summary. Experiment Auto Refresh 
> runs an Ajax request every 3 seconds to check to see if the experiment status 
> has changed. If the experiment status has changed it tries to reload the 
> page. However, it keeps checking every 3 seconds and it is possible for the 
> summary page to
> * check to see if the experiment status has changed
> * start reloading the page
> * check a second time to see if the experiment status has changed
> * start reloading the page a second time
> * etc.
> For [~eroma_a] the summary page basically got stuck in this loop and never 
> refreshed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AIRAVATA-2163) optimize credential store data models

2016-11-11 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/AIRAVATA-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15657587#comment-15657587
 ] 

ASF GitHub Bot commented on AIRAVATA-2163:
--

Github user scnakandala commented on the issue:

https://github.com/apache/airavata/pull/74
  
@anujbhan Is this an active pull request ? If so can you fix the conflicts 


> optimize credential store data models
> -
>
> Key: AIRAVATA-2163
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2163
> Project: Airavata
>  Issue Type: Improvement
>  Components: Airavata API
> Environment: Development
>Reporter: Anuj Bhandar
>Assignee: Anuj Bhandar
>  Labels: GATask
> Fix For: 17
>
>
> This improvement is based on the following Pull request : 
> https://github.com/apache/airavata/pull/54.
> **Improvements agreed upon :** 
> Followings are few suggestions to improve your pull request.
> * We can do this in a better way by adding generic API method(to 
> AiravataAPIServer) like "getAllCredentialSummary" instead of adding API 
> method for each credential types eg: "getAllGatewaySSHPubKeysSummary" which 
> will return all the credential summary for that particular gatewayId. You may 
> be able to remove few redundant methods from Airavata API server.
> * Let's introduced one credential summary struct to all credential types, 
> how we differentiate is we have credential type enum field( SSH, PASSWD, CERT 
> etc ) in the credential summary thrift struct.
>  * Move credential data model thrift file to data model directory and 
> merge credential summary thrift file with it.
>  * Credential stubs still have date fields in generated thrift files, not 
> because your changes, but we need to fix it so remove it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (AIRAVATA-1960) Ability to mark inputs as 'Optional'. These are not mandatory to be available at create experiment.

2016-11-11 Thread Eroma (JIRA)


 [ 
https://issues.apache.org/jira/browse/AIRAVATA-1960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eroma closed AIRAVATA-1960.
---

tested and verified in 
https://dev.seagrid.org/

We can enable optional inputs at application interface level.
Once enabled user can upload no files, single file or multiple files.
Thes are just uploaded files. User cannot give any arguments, etc...No cn give 
string or numeric optional inputs as well

> Ability to mark inputs as 'Optional'. These are not mandatory to be available 
> at create experiment.
> ---
>
> Key: AIRAVATA-1960
> URL: https://issues.apache.org/jira/browse/AIRAVATA-1960
> Project: Airavata
>  Issue Type: New Feature
>  Components: PGA PHP Web Gateway
>Affects Versions: 0.16
>Reporter: Eroma
>Assignee: Shameera Rathnayaka
> Fix For: 0.16
>
>
> Currently when defined all the inputs are mandatory. There are some 
> applications that will take input files only if they are provided by the user.
> These could be user adding multiples of the same input or different inputs 
> but not mandatory for application execution.
> If marked as optional; they will not be mandatory at experiment create, clone 
> and edit



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] airavata issue #74: AIRAVATA-2163: Optimising the cred store data model

2016-11-11 Thread scnakandala

Github user scnakandala commented on the issue:

https://github.com/apache/airavata/pull/74
  
@anujbhan Is this an active pull request ? If so can you fix the conflicts 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (AIRAVATA-2206) When the SEAGrid rich client times out have the login page to appear for logins

2016-11-11 Thread Supun Chathuranga Nakandala (JIRA)


[ 
https://issues.apache.org/jira/browse/AIRAVATA-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15657582#comment-15657582
 ] 

Supun Chathuranga Nakandala commented on AIRAVATA-2206:
---

[~eroma_a] when this happen does it pops up an exception dialog

> When the SEAGrid rich client times out have the login page to appear for 
> logins
> ---
>
> Key: AIRAVATA-2206
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2206
> Project: Airavata
>  Issue Type: Bug
> Environment: seagrid.org
>Reporter: Eroma
>Assignee: Supun Chathuranga Nakandala
>
> When SEAGrid rich client times out currently the same page will remain where 
> users cannot do anything but to close and open again.
> Instead have the login page prompted at time out.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (AIRAVATA-2185) Add OWNER ResourcePermissionType to sharing API

2016-11-11 Thread Supun Chathuranga Nakandala (JIRA)


 [ 
https://issues.apache.org/jira/browse/AIRAVATA-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Supun Chathuranga Nakandala resolved AIRAVATA-2185.
---
Resolution: Fixed

> Add OWNER ResourcePermissionType to sharing API
> ---
>
> Key: AIRAVATA-2185
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2185
> Project: Airavata
>  Issue Type: New Feature
>  Components: Airavata API
>Reporter: Marcus Christie
>Assignee: Supun Chathuranga Nakandala
>
> I [discussed this earlier with 
> Supun|https://issues.apache.org/jira/browse/AIRAVATA-2170?focusedCommentId=15588665=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15588665]
> {quote}
> I talked with Supun and he is going to add the OWNER ResourcePermissionType 
> to the sharing API. Then I'll be able to call getAllAccessibleUsers with the 
> OWNER permission type.
> {quote}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AIRAVATA-2185) Add OWNER ResourcePermissionType to sharing API

2016-11-11 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/AIRAVATA-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15657578#comment-15657578
 ] 

ASF subversion and git services commented on AIRAVATA-2185:
---

Commit 177a2484dfffaf5f46d92d4bdc6755fcc1ce07d0 in airavata's branch 
refs/heads/develop from scnakandala
[ https://git-wip-us.apache.org/repos/asf?p=airavata.git;h=177a248 ]

fixing AIRAVATA-2185 : Add OWNER ResourcePermissionType to sharing API


> Add OWNER ResourcePermissionType to sharing API
> ---
>
> Key: AIRAVATA-2185
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2185
> Project: Airavata
>  Issue Type: New Feature
>  Components: Airavata API
>Reporter: Marcus Christie
>Assignee: Supun Chathuranga Nakandala
>
> I [discussed this earlier with 
> Supun|https://issues.apache.org/jira/browse/AIRAVATA-2170?focusedCommentId=15588665=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15588665]
> {quote}
> I talked with Supun and he is going to add the OWNER ResourcePermissionType 
> to the sharing API. Then I'll be able to call getAllAccessibleUsers with the 
> OWNER permission type.
> {quote}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AIRAVATA-2223) Support for data sharing disabled

2016-11-11 Thread Marcus Christie (JIRA)


 [ 
https://issues.apache.org/jira/browse/AIRAVATA-2223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Marcus Christie updated AIRAVATA-2223:
--
Fix Version/s: 0.17-SNAPSHOT

> Support for data sharing disabled
> -
>
> Key: AIRAVATA-2223
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2223
> Project: Airavata
>  Issue Type: Bug
>  Components: PGA PHP Web Gateway
>Reporter: Marcus Christie
>Assignee: Marcus Christie
> Fix For: 0.17-SNAPSHOT
>
>
> Test and fix issues related to data sharing being disabled.
> Known issues
> * Project listing is empty when creating a new experiment even when user has 
> several projects



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (AIRAVATA-1997) Gateway ID saved as project name. Default Project not existing for new users.

2016-11-11 Thread Eroma (JIRA)


 [ 
https://issues.apache.org/jira/browse/AIRAVATA-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eroma closed AIRAVATA-1997.
---

tested and verified in
https://dev.seagrid.org/

> Gateway ID saved as project name. Default Project not existing for new users.
> -
>
> Key: AIRAVATA-1997
> URL: https://issues.apache.org/jira/browse/AIRAVATA-1997
> Project: Airavata
>  Issue Type: Bug
>  Components: PGA PHP Web Gateway
>Reporter: Eroma
>Assignee: Supun Chathuranga Nakandala
> Fix For: 0.17-SNAPSHOT
>
>
> When a new use with gateway-user role logs in
> 1. Default Project does not exists
> 2. When a new project is created project name is not the name given by user 
> but the gateway ID



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (AIRAVATA-2196) Both users with 'Read' access and 'Write' access should NOT have the same set of privileges in PGA

2016-11-11 Thread Eroma (JIRA)


 [ 
https://issues.apache.org/jira/browse/AIRAVATA-2196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eroma resolved AIRAVATA-2196.
-
Resolution: Fixed

> Both users with 'Read' access and 'Write' access should NOT have the same set 
> of privileges in PGA
> --
>
> Key: AIRAVATA-2196
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2196
> Project: Airavata
>  Issue Type: Bug
>  Components: PGA PHP Web Gateway
>Reporter: Eroma
>Assignee: Marcus Christie
> Fix For: 0.17-SNAPSHOT
>
>
> Currently when sharing experiments and projects 'read' access and 'write' 
> access provides same set of privileges for users.
> Please review the requirements in 
> https://docs.google.com/document/d/1PVWFNDmbugpwUbcla9LiNx_3SuYGl-_4WjiJ7rGkfl8/edit
>  and modify accordingly.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (AIRAVATA-2190) User A shared a single experiment with User B, read access. Project is also shared now with User B.

2016-11-11 Thread Eroma (JIRA)


 [ 
https://issues.apache.org/jira/browse/AIRAVATA-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eroma resolved AIRAVATA-2190.
-
Resolution: Fixed

> User A shared a single experiment with User B, read access. Project is also 
> shared now with User B.
> ---
>
> Key: AIRAVATA-2190
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2190
> Project: Airavata
>  Issue Type: Bug
>  Components: PGA PHP Web Gateway
> Environment: https://dev.seagrid.org
>Reporter: Eroma
>Assignee: Marcus Christie
> Fix For: 0.17-SNAPSHOT
>
>
> Steps
> 1. User A shared a single experiment with user B. With read access
> 2. User B now has access to User A's project which experiment belongs
> 3. User B can create new experiments under the Project.
> 4. User B can cancel the shared experiment irrespective of having only read 
> access
> 5. user B can clone the shared experiment and create a new experiment under 
> the same project and remove sharing of the project owner. 
> 6. Original user A cannot see the cloned experiment under his own project
> User B should not be able to create any experiments under the project the 
> shared experiment belongs. 
> No should be able to cancel the shared experiment, only has read access.
> If cloned should create it under own project; not with user A's project



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AIRAVATA-2195) Shared user will end up with an experiment which he has no permission to view

2016-11-11 Thread Marcus Christie (JIRA)


[ 
https://issues.apache.org/jira/browse/AIRAVATA-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15657562#comment-15657562
 ] 

Marcus Christie commented on AIRAVATA-2195:
---

I don't think I can implement this until AIRAVATA-2185 is implemented. The 
situation is this:
* User A is the owner of project P1
* User A gives User B write access to project P1
* User B creates experiment E1 in P1
* User A revokes from User B write access to project P1
* User B can still see E1 but can't see P1
* There's now no way for PGA to figure out, with User B's login, who is the 
owner of P1.


> Shared user will end up with an experiment which he has no permission to view
> -
>
> Key: AIRAVATA-2195
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2195
> Project: Airavata
>  Issue Type: Bug
>  Components: PGA PHP Web Gateway
> Environment: https://dev.seagrid.org
>Reporter: Eroma
>Assignee: Marcus Christie
> Fix For: 0.17-SNAPSHOT
>
> Attachments: Screen Shot 2016-10-25 at 3.04.35 PM.png, 
> project_owner.png
>
>
> Steps;
> 1. User A creates a a project and shares it with user B and user C
> 2. user A creates an experiment which is shared with both users B and C
> 3. User C clones and creates a new experiment and removes User A from the 
> experiment. Only the experiment is shared with usr C
> 4. User A removes the sharing from both users at project level.
> 5. Both users cannot view the project now.
> 6. Both users can see the cloned experiment in Experiment Browse but cannot 
> view the experiment details. Throws exception attached
> First if using owners project to create experiments should not be able to 
> remove the owner from the experiment or the project
> Secondly if permission is denied should handle with correct error messages. 
> h5. TODO
> * Add the notion of an indirect or cascading owner to the sharing dialog and 
> display them like the [^project_owner.png] screenshot attached
> * also show the indirect owner in the display of shared with users



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AIRAVATA-2223) Support for data sharing disabled

2016-11-11 Thread Suresh Marru (JIRA)


[ 
https://issues.apache.org/jira/browse/AIRAVATA-2223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15657543#comment-15657543
 ] 

Suresh Marru commented on AIRAVATA-2223:


Since this is a " experimental feature" and needs more to mature +1 for 
disabling it by default in 0.17 release. 

> Support for data sharing disabled
> -
>
> Key: AIRAVATA-2223
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2223
> Project: Airavata
>  Issue Type: Bug
>  Components: PGA PHP Web Gateway
>Reporter: Marcus Christie
>Assignee: Marcus Christie
>
> Test and fix issues related to data sharing being disabled.
> Known issues
> * Project listing is empty when creating a new experiment even when user has 
> several projects



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (AIRAVATA-2202) Experiment data not available in https://data.seagrid.org/

2016-11-11 Thread Eroma (JIRA)


 [ 
https://issues.apache.org/jira/browse/AIRAVATA-2202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eroma closed AIRAVATA-2202.
---

tested and verified in  production seagrid and https://data.seagrid.org
Now soon after the job and experiment is COMPLETED it will be available in data 
catalog.

BUT this is only working for Gaussian.


> Experiment data not available in https://data.seagrid.org/
> --
>
> Key: AIRAVATA-2202
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2202
> Project: Airavata
>  Issue Type: Bug
>  Components: PGA PHP Web Gateway
> Environment: seagrid.org
>Reporter: Eroma
>Assignee: Supun Chathuranga Nakandala
>
> 1. Created and launched an experiment.
> 2. Once the job got completed and files are transferred to PGA side logged in 
> to https://data.seagrid.org/
> 3. When searched for the experiment using the name nothing is retrieved. 
> Seems like only some pervious data is existing in https://data.seagrid.org/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AIRAVATA-2223) Support for data sharing disabled

2016-11-11 Thread Marcus Christie (JIRA)


[ 
https://issues.apache.org/jira/browse/AIRAVATA-2223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15657520#comment-15657520
 ] 

Marcus Christie commented on AIRAVATA-2223:
---

[~eroma_a], [~smarru],

Just want to confirm that we want to support data sharing disabled in the next 
release.  I think there are probably a few bugs that will need to be fixed 
because some code that assumes data sharing has crept into PGA.

> Support for data sharing disabled
> -
>
> Key: AIRAVATA-2223
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2223
> Project: Airavata
>  Issue Type: Bug
>  Components: PGA PHP Web Gateway
>Reporter: Marcus Christie
>Assignee: Marcus Christie
>
> Test and fix issues related to data sharing being disabled.
> Known issues
> * Project listing is empty when creating a new experiment even when user has 
> several projects



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (AIRAVATA-2081) Error exception thrown when clicked on clone for an experiment

2016-11-11 Thread Eroma (JIRA)


 [ 
https://issues.apache.org/jira/browse/AIRAVATA-2081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eroma closed AIRAVATA-2081.
---

tested and verified in 
https://dev.seagrid.org

> Error exception thrown when clicked on clone for an experiment
> --
>
> Key: AIRAVATA-2081
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2081
> Project: Airavata
>  Issue Type: Bug
>  Components: PGA PHP Web Gateway
>Affects Versions: 0.17-SNAPSHOT
> Environment: dev.seagrid.org
>Reporter: Eroma
>Assignee: Supun Chathuranga Nakandala
> Attachments: Screen Shot 2016-09-02 at 2.34.51 PM.png, Screen Shot 
> 2016-10-05 at 3.13.58 PM.png
>
>
> when clicked on clone gets the error 
> Undefined index: scheduling
> but the new cloned experiment is actually created in the backend.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AIRAVATA-2223) Support for data sharing disabled

2016-11-11 Thread Marcus Christie (JIRA)

Marcus Christie created AIRAVATA-2223:
-

 Summary: Support for data sharing disabled
 Key: AIRAVATA-2223
 URL: https://issues.apache.org/jira/browse/AIRAVATA-2223
 Project: Airavata
  Issue Type: Bug
  Components: PGA PHP Web Gateway
Reporter: Marcus Christie
Assignee: Marcus Christie


Test and fix issues related to data sharing being disabled.

Known issues
* Project listing is empty when creating a new experiment even when user has 
several projects



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Jenkins build is still unstable: airavata-dev » Airavata Registry Core #1297

2016-11-11 Thread Apache Jenkins Server

See

Jenkins build is still unstable: airavata-dev #1297

2016-11-11 Thread Apache Jenkins Server

See

[jira] [Closed] (AIRAVATA-2213) Experiment Summary is not getting refreshed!

2016-11-11 Thread Eroma (JIRA)


 [ 
https://issues.apache.org/jira/browse/AIRAVATA-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eroma closed AIRAVATA-2213.
---

tested and verified in
https://dev.seagrid.org/


Now the Experiment summary gets experiment and job statuses updated either when 
manually refreshed or auto refreshed.

> Experiment Summary is not getting refreshed!
> 
>
> Key: AIRAVATA-2213
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2213
> Project: Airavata
>  Issue Type: Bug
>  Components: PGA PHP Web Gateway
> Environment: https://dev.seagrid.org/
>Reporter: Eroma
>Assignee: Marcus Christie
>
> When clicked on manual refresh always shows the experiment status as CREATED. 
> No job status or experiment statuses are displayed as they change. But 
> actually the experiment is executed and job is launched. although those are 
> not refreshed and displayed in Experiment Summary.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (AIRAVATA-2213) Experiment Summary is not getting refreshed!

2016-11-11 Thread Eroma (JIRA)


 [ 
https://issues.apache.org/jira/browse/AIRAVATA-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eroma resolved AIRAVATA-2213.
-
Resolution: Fixed

> Experiment Summary is not getting refreshed!
> 
>
> Key: AIRAVATA-2213
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2213
> Project: Airavata
>  Issue Type: Bug
>  Components: PGA PHP Web Gateway
> Environment: https://dev.seagrid.org/
>Reporter: Eroma
>Assignee: Marcus Christie
>
> When clicked on manual refresh always shows the experiment status as CREATED. 
> No job status or experiment statuses are displayed as they change. But 
> actually the experiment is executed and job is launched. although those are 
> not refreshed and displayed in Experiment Summary.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Jenkins build is still unstable: airavata-dev » Airavata Registry Core #1296

2016-11-11 Thread Apache Jenkins Server

See

Jenkins build is still unstable: airavata-dev #1296

2016-11-11 Thread Apache Jenkins Server

See

[jira] [Commented] (AIRAVATA-2193) When projects of other users are available for experiment creation cannot figure out to whom it belongs

2016-11-11 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/AIRAVATA-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15657369#comment-15657369
 ] 

ASF GitHub Bot commented on AIRAVATA-2193:
--

Github user machristie commented on the issue:

https://github.com/apache/airavata-php-gateway/pull/37
  
@scnakandala can you review when you get a chance? Thanks.


> When projects of other users are available for experiment creation cannot 
> figure out to whom it belongs
> ---
>
> Key: AIRAVATA-2193
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2193
> Project: Airavata
>  Issue Type: Bug
>  Components: PGA PHP Web Gateway
> Environment: https://dev.seagrid.org
>Reporter: Eroma
>Assignee: Marcus Christie
> Fix For: 0.17-SNAPSHOT
>
> Attachments: screenshot-1.png
>
>
> Currently in Experiment creation we only show the project name. When projects 
> are shared (with write access), the shared user can use the project and make 
> new experiments. If both users has projects with same name (E.g: Default 
> Project) user will not be able to identify the correct project.
> This gets worse if several has shared their Default Project with each other. 
> We need to feature of displaying the owner of a project at experiment 
> creation. When selecting the project.
> h3. TODO
> * update project selection at experiment creation
> * update project selection when cloning an experiment



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AIRAVATA-2193) When projects of other users are available for experiment creation cannot figure out to whom it belongs

2016-11-11 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/AIRAVATA-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15657366#comment-15657366
 ] 

ASF GitHub Bot commented on AIRAVATA-2193:
--

GitHub user machristie opened a pull request:

https://github.com/apache/airavata-php-gateway/pull/37

AIRAVATA-2193 Distinguish projects owned by other users



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/machristie/airavata-php-gateway 
AIRAVATA-2193-projects-of-other-users-exp-creation

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/airavata-php-gateway/pull/37.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #37


commit 9faea85c25360f3df18eb967fcc2f83c764d781d
Author: Marcus Christie 
Date:   2016-11-11T15:41:29Z

AIRAVATA-2193 Distinguish projects owned by other users




> When projects of other users are available for experiment creation cannot 
> figure out to whom it belongs
> ---
>
> Key: AIRAVATA-2193
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2193
> Project: Airavata
>  Issue Type: Bug
>  Components: PGA PHP Web Gateway
> Environment: https://dev.seagrid.org
>Reporter: Eroma
>Assignee: Marcus Christie
> Fix For: 0.17-SNAPSHOT
>
> Attachments: screenshot-1.png
>
>
> Currently in Experiment creation we only show the project name. When projects 
> are shared (with write access), the shared user can use the project and make 
> new experiments. If both users has projects with same name (E.g: Default 
> Project) user will not be able to identify the correct project.
> This gets worse if several has shared their Default Project with each other. 
> We need to feature of displaying the owner of a project at experiment 
> creation. When selecting the project.
> h3. TODO
> * update project selection at experiment creation
> * update project selection when cloning an experiment



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] airavata-php-gateway issue #37: AIRAVATA-2193 Distinguish projects owned by ...

2016-11-11 Thread machristie

Github user machristie commented on the issue:

https://github.com/apache/airavata-php-gateway/pull/37
  
@scnakandala can you review when you get a chance? Thanks.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] airavata-php-gateway pull request #37: AIRAVATA-2193 Distinguish projects ow...

2016-11-11 Thread machristie

GitHub user machristie opened a pull request:

https://github.com/apache/airavata-php-gateway/pull/37

AIRAVATA-2193 Distinguish projects owned by other users



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/machristie/airavata-php-gateway 
AIRAVATA-2193-projects-of-other-users-exp-creation

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/airavata-php-gateway/pull/37.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #37


commit 9faea85c25360f3df18eb967fcc2f83c764d781d
Author: Marcus Christie 
Date:   2016-11-11T15:41:29Z

AIRAVATA-2193 Distinguish projects owned by other users




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Assigned] (AIRAVATA-2207) Gateway admins cannot view experiments launched by gateway users in Experiment Statistics

2016-11-11 Thread Marcus Christie (JIRA)


 [ 
https://issues.apache.org/jira/browse/AIRAVATA-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Marcus Christie reassigned AIRAVATA-2207:
-

Assignee: Eroma  (was: Marcus Christie)

> Gateway admins cannot view experiments launched by gateway users in 
> Experiment Statistics
> -
>
> Key: AIRAVATA-2207
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2207
> Project: Airavata
>  Issue Type: Bug
>  Components: PGA PHP Web Gateway
> Environment: https://dev.seagrid.org
>Reporter: Eroma
>Assignee: Eroma
> Fix For: 0.17-SNAPSHOT
>
> Attachments: Screen Shot 2016-11-03 at 11.15.40 AM.png
>
>
> In Admin dashboard -> Experiment Statistics page gateway admin should be able 
> to view any experiment. Currently when tried to view other users experiment 
> summary throws error 'Exception: User does not have permission to access this 
> resource'
> Admin can only view his own experiments in experiment statistics



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AIRAVATA-2207) Gateway admins cannot view experiments launched by gateway users in Experiment Statistics

2016-11-11 Thread Marcus Christie (JIRA)


[ 
https://issues.apache.org/jira/browse/AIRAVATA-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15657266#comment-15657266
 ] 

Marcus Christie commented on AIRAVATA-2207:
---

I've deployed this fix to dev.seagrid.org and tested.

I'm going to assign it to Eroma to resolve and close.

> Gateway admins cannot view experiments launched by gateway users in 
> Experiment Statistics
> -
>
> Key: AIRAVATA-2207
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2207
> Project: Airavata
>  Issue Type: Bug
>  Components: PGA PHP Web Gateway
> Environment: https://dev.seagrid.org
>Reporter: Eroma
>Assignee: Marcus Christie
> Fix For: 0.17-SNAPSHOT
>
> Attachments: Screen Shot 2016-11-03 at 11.15.40 AM.png
>
>
> In Admin dashboard -> Experiment Statistics page gateway admin should be able 
> to view any experiment. Currently when tried to view other users experiment 
> summary throws error 'Exception: User does not have permission to access this 
> resource'
> Admin can only view his own experiments in experiment statistics



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Jenkins build is still unstable: airavata-dev » Airavata Registry Core #1295

2016-11-11 Thread Apache Jenkins Server

See

Jenkins build is still unstable: airavata-dev #1295

2016-11-11 Thread Apache Jenkins Server

See

[jira] [Closed] (AIRAVATA-2188) Created user account in gateway portal has no roles displayed or no roles can be assigned!

2016-11-11 Thread Eroma (JIRA)


 [ 
https://issues.apache.org/jira/browse/AIRAVATA-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eroma closed AIRAVATA-2188.
---

tested and verified in 
https://dev.seagrid.org

Roles are getting assigned correctly.

> Created user account in gateway portal has no roles displayed or no roles can 
> be assigned!
> --
>
> Key: AIRAVATA-2188
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2188
> Project: Airavata
>  Issue Type: Bug
>  Components: PGA PHP Web Gateway
> Environment: https://dev.seagrid.org
>Reporter: Eroma
>Assignee: Marcus Christie
> Attachments: Screen Shot 2016-10-25 at 10.48.57 AM.png
>
>
> Created a new account 'DataShare15'
> Account confirmation done
> When tried to assign a user role for the account none of the roles are 
> displayed no the user has any roles assigned.
> Only happened once and rest of the account creation worked fine. 
> Check the attachment



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (AIRAVATA-2188) Created user account in gateway portal has no roles displayed or no roles can be assigned!

2016-11-11 Thread Eroma (JIRA)


 [ 
https://issues.apache.org/jira/browse/AIRAVATA-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eroma resolved AIRAVATA-2188.
-
Resolution: Fixed

> Created user account in gateway portal has no roles displayed or no roles can 
> be assigned!
> --
>
> Key: AIRAVATA-2188
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2188
> Project: Airavata
>  Issue Type: Bug
>  Components: PGA PHP Web Gateway
> Environment: https://dev.seagrid.org
>Reporter: Eroma
>Assignee: Marcus Christie
> Attachments: Screen Shot 2016-10-25 at 10.48.57 AM.png
>
>
> Created a new account 'DataShare15'
> Account confirmation done
> When tried to assign a user role for the account none of the roles are 
> displayed no the user has any roles assigned.
> Only happened once and rest of the account creation worked fine. 
> Check the attachment



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Jenkins build is still unstable: airavata-dev » Airavata Registry Core #1294

2016-11-11 Thread Apache Jenkins Server

See

[jira] [Commented] (AIRAVATA-2212) Experiment Auto Refresh may try to reload the page while reloading the page

2016-11-11 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/AIRAVATA-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15657093#comment-15657093
 ] 

ASF GitHub Bot commented on AIRAVATA-2212:
--

Github user machristie commented on the issue:

https://github.com/apache/airavata-php-gateway/pull/36
  
@scnakandala I found a bug in my solution. This PR fixes it.  Can you 
please review when you get a chance?


> Experiment Auto Refresh may try to reload the page while reloading the page
> ---
>
> Key: AIRAVATA-2212
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2212
> Project: Airavata
>  Issue Type: Bug
>Reporter: Marcus Christie
>Assignee: Marcus Christie
>
> The Experiment Auto Refresh feature has a bug that occurs when it takes more 
> than about 3 seconds to load the experiment summary. Experiment Auto Refresh 
> runs an Ajax request every 3 seconds to check to see if the experiment status 
> has changed. If the experiment status has changed it tries to reload the 
> page. However, it keeps checking every 3 seconds and it is possible for the 
> summary page to
> * check to see if the experiment status has changed
> * start reloading the page
> * check a second time to see if the experiment status has changed
> * start reloading the page a second time
> * etc.
> For [~eroma_a] the summary page basically got stuck in this loop and never 
> refreshed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] airavata-php-gateway issue #36: AIRAVATA-2212 Using setInterval so status ch...

2016-11-11 Thread machristie

Github user machristie commented on the issue:

https://github.com/apache/airavata-php-gateway/pull/36
  
@scnakandala I found a bug in my solution. This PR fixes it.  Can you 
please review when you get a chance?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (AIRAVATA-2212) Experiment Auto Refresh may try to reload the page while reloading the page

2016-11-11 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/AIRAVATA-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15657086#comment-15657086
 ] 

ASF GitHub Bot commented on AIRAVATA-2212:
--

GitHub user machristie opened a pull request:

https://github.com/apache/airavata-php-gateway/pull/36

AIRAVATA-2212 Using setInterval so status check is turned back on

The way it was implemented with setTimeout the status checking
(autoRefresh) wouldn't start again once it was toggled back on. I
switched to setInterval since it is easier to just check the autoRefresh
flag every 3 seconds.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/machristie/airavata-php-gateway 
AIRAVATA-2212-autorefresh-prevents-page-from-loading

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/airavata-php-gateway/pull/36.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #36


commit 3910260e58b3e1c5c554bada3dd33ded9e7fd403
Author: Marcus Christie 
Date:   2016-11-11T13:26:17Z

AIRAVATA-2212 Using setInterval so status check is turned back on

The way it was implemented with setTimeout the status checking
(autoRefresh) wouldn't start again once it was toggled back on. I
switched to setInterval since it is easier to just check the autoRefresh
flag every 3 seconds.




> Experiment Auto Refresh may try to reload the page while reloading the page
> ---
>
> Key: AIRAVATA-2212
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2212
> Project: Airavata
>  Issue Type: Bug
>Reporter: Marcus Christie
>Assignee: Marcus Christie
>
> The Experiment Auto Refresh feature has a bug that occurs when it takes more 
> than about 3 seconds to load the experiment summary. Experiment Auto Refresh 
> runs an Ajax request every 3 seconds to check to see if the experiment status 
> has changed. If the experiment status has changed it tries to reload the 
> page. However, it keeps checking every 3 seconds and it is possible for the 
> summary page to
> * check to see if the experiment status has changed
> * start reloading the page
> * check a second time to see if the experiment status has changed
> * start reloading the page a second time
> * etc.
> For [~eroma_a] the summary page basically got stuck in this loop and never 
> refreshed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] airavata-php-gateway pull request #36: AIRAVATA-2212 Using setInterval so st...

2016-11-11 Thread machristie

GitHub user machristie opened a pull request:

https://github.com/apache/airavata-php-gateway/pull/36

AIRAVATA-2212 Using setInterval so status check is turned back on

The way it was implemented with setTimeout the status checking
(autoRefresh) wouldn't start again once it was toggled back on. I
switched to setInterval since it is easier to just check the autoRefresh
flag every 3 seconds.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/machristie/airavata-php-gateway 
AIRAVATA-2212-autorefresh-prevents-page-from-loading

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/airavata-php-gateway/pull/36.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #36


commit 3910260e58b3e1c5c554bada3dd33ded9e7fd403
Author: Marcus Christie 
Date:   2016-11-11T13:26:17Z

AIRAVATA-2212 Using setInterval so status check is turned back on

The way it was implemented with setTimeout the status checking
(autoRefresh) wouldn't start again once it was toggled back on. I
switched to setInterval since it is easier to just check the autoRefresh
flag every 3 seconds.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

1 2 >

1 - 100 of 114 matches

Mail list logo