date:20161104

See 

--
[...truncated 2554 lines...]
[INFO] Downloaded: 
http://maven.wso2.org/nexus/content/groups/wso2-public/org/apache/neethi/wso2/neethi/2.0.4.wso2v4/neethi-2.0.4.wso2v4.jar
 (28 KB at 30.7 KB/sec)
[INFO] Downloading: 
http://maven.wso2.org/nexus/content/groups/wso2-public/org/apache/ws/commons/axiom/wso2/axiom/1.2.11.wso2v4/axiom-1.2.11.wso2v4.jar
[INFO] Downloaded: 
http://maven.wso2.org/nexus/content/groups/wso2-public/org/apache/ws/commons/schema/wso2/XmlSchema/1.4.7.wso2v2/XmlSchema-1.4.7.wso2v2.jar
 (139 KB at 102.9 KB/sec)
[INFO] Downloading: 
http://maven.wso2.org/nexus/content/groups/wso2-public/org/apache/axis2/wso2/axis2/1.6.1.wso2v4/axis2-1.6.1.wso2v4.jar
[INFO] Downloaded: 
http://maven.wso2.org/nexus/content/groups/wso2-public/org/apache/ws/commons/schema/XmlSchema/1.4.7-wso2v2/XmlSchema-1.4.7-wso2v2.jar
 (146 KB at 107.8 KB/sec)
[INFO] Downloading: 
http://maven.wso2.org/nexus/content/groups/wso2-public/org/wso2/carbon/org.wso2.carbon.utils/4.2.0/org.wso2.carbon.utils-4.2.0.jar
[INFO] Downloaded: 
http://maven.wso2.org/nexus/content/groups/wso2-public/wsdl4j/wso2/wsdl4j/1.6.2.wso2v4/wsdl4j-1.6.2.wso2v4.jar
 (189 KB at 124.8 KB/sec)
[INFO] Downloading: 
http://maven.wso2.org/nexus/content/groups/wso2-public/org/wso2/carbon/org.wso2.carbon.user.api/4.2.0/org.wso2.carbon.user.api-4.2.0.jar
[INFO] Downloaded: 
http://maven.wso2.org/nexus/content/groups/wso2-public/org/wso2/carbon/org.wso2.carbon.user.api/4.2.0/org.wso2.carbon.user.api-4.2.0.jar
 (19 KB at 5.6 KB/sec)
[INFO] Downloading: 
http://maven.wso2.org/nexus/content/groups/wso2-public/org/wso2/carbon/org.wso2.carbon.logging/4.2.0/org.wso2.carbon.logging-4.2.0.jar
[INFO] Downloaded: 
http://maven.wso2.org/nexus/content/groups/wso2-public/org/wso2/carbon/org.wso2.carbon.utils/4.2.0/org.wso2.carbon.utils-4.2.0.jar
 (233 KB at 59.5 KB/sec)
[INFO] Downloading: 
http://maven.wso2.org/nexus/content/groups/wso2-public/org/eclipse/equinox/org.apache.log4j/1.2.13.v200706111418/org.apache.log4j-1.2.13.v200706111418.jar
[INFO] Downloaded: 
http://maven.wso2.org/nexus/content/groups/wso2-public/org/apache/ws/commons/axiom/wso2/axiom/1.2.11.wso2v4/axiom-1.2.11.wso2v4.jar
 (1592 KB at 313.7 KB/sec)
[INFO] Downloading: 
http://maven.wso2.org/nexus/content/groups/wso2-public/org/wso2/carbon/org.wso2.carbon.bootstrap/4.2.0/org.wso2.carbon.bootstrap-4.2.0.jar
[INFO] Downloaded: 
http://maven.wso2.org/nexus/content/groups/wso2-public/org/wso2/carbon/org.wso2.carbon.bootstrap/4.2.0/org.wso2.carbon.bootstrap-4.2.0.jar
 (13 KB at 2.3 KB/sec)
[INFO] Downloading: 
http://maven.wso2.org/nexus/content/groups/wso2-public/wrapper/wrapper/3.2.3/wrapper-3.2.3.jar
[INFO] Downloaded: 
http://maven.wso2.org/nexus/content/groups/wso2-public/org/wso2/carbon/org.wso2.carbon.logging/4.2.0/org.wso2.carbon.logging-4.2.0.jar
 (410 KB at 70.0 KB/sec)
[INFO] Downloading: 
http://maven.wso2.org/nexus/content/groups/wso2-public/org/wso2/carbon/org.wso2.carbon.queuing/4.2.0/org.wso2.carbon.queuing-4.2.0.jar
[INFO] Downloaded: 
http://maven.wso2.org/nexus/content/groups/wso2-public/org/apache/axis2/wso2/axis2/1.6.1.wso2v4/axis2-1.6.1.wso2v4.jar
 (8421 KB at 1387.9 KB/sec)
[INFO] Downloading: 
http://maven.wso2.org/nexus/content/groups/wso2-public/org/wso2/carbon/org.wso2.carbon.base/4.2.0/org.wso2.carbon.base-4.2.0.jar
[INFO] Downloaded: 
http://maven.wso2.org/nexus/content/groups/wso2-public/org/wso2/carbon/org.wso2.carbon.queuing/4.2.0/org.wso2.carbon.queuing-4.2.0.jar
 (6 KB at 0.8 KB/sec)
[INFO] Downloading: 
http://maven.wso2.org/nexus/content/groups/wso2-public/org/wso2/securevault/org.wso2.securevault/1.0.0-wso2v2/org.wso2.securevault-1.0.0-wso2v2.jar
[INFO] Downloaded: 
http://maven.wso2.org/nexus/content/groups/wso2-public/wrapper/wrapper/3.2.3/wrapper-3.2.3.jar
 (82 KB at 12.3 KB/sec)
[INFO] Downloading: 
http://maven.wso2.org/nexus/content/groups/wso2-public/org/wso2/carbon/org.wso2.carbon.securevault/4.2.0/org.wso2.carbon.securevault-4.2.0.jar
[INFO] Downloaded: 
http://maven.wso2.org/nexus/content/groups/wso2-public/org/wso2/carbon/org.wso2.carbon.base/4.2.0/org.wso2.carbon.base-4.2.0.jar
 (27 KB at 3.9 KB/sec)
[INFO] Downloading: 
http://maven.wso2.org/nexus/content/groups/wso2-public/org/eclipse/osgi/org.eclipse.osgi/3.8.1.v20120830-144521/org.eclipse.osgi-3.8.1.v20120830-144521.jar
[INFO] Downloaded: 
http://maven.wso2.org/nexus/content/groups/wso2-public/org/eclipse/equinox/org.apache.log4j/1.2.13.v200706111418/org.apache.log4j-1.2.13.v200706111418.jar
 (360 KB at 50.9 KB/sec)
[INFO] Downloading: 
http://maven.wso2.org/nexus/content/groups/wso2-public/org/igniterealtime/smack/wso2/smack/3.0.4.wso2v1/smack-3.0.4.wso2v1.jar
[INFO] Downloaded: 
http://maven.wso2.org/nexus/content/groups/wso2-public/org/wso2/carbon/org.wso2.carbon.identity.oauth.stub/4.2.3/org.wso2.carbon.identity.oauth.stub-4.2.3.jar
 (553 KB at 75.7 KB/sec)
[INFO] Downloading:

Build failed in Jenkins: airavata-dev » Airavata API Server #1140

2016-11-04 Thread Apache Jenkins Server

See 


--
[...truncated 440 lines...]
[INFO] Downloading: 
http://repo1.maven.org/maven2/org/wso2/carbon/org.wso2.carbon.securevault/4.2.0/org.wso2.carbon.securevault-4.2.0.jar
[INFO] Downloaded: 
http://repo1.maven.org/maven2/org/apache/ws/commons/axiom/axiom-impl/1.2.11/axiom-impl-1.2.11.jar
 (120 KB at 2490.5 KB/sec)
[INFO] Downloading: 
http://repo1.maven.org/maven2/org/eclipse/osgi/org.eclipse.osgi/3.8.1.v20120830-144521/org.eclipse.osgi-3.8.1.v20120830-144521.jar
[INFO] Downloading: 
http://repo1.maven.org/maven2/org/igniterealtime/smack/wso2/smack/3.0.4.wso2v1/smack-3.0.4.wso2v1.jar
[INFO] Downloaded: 
http://repo1.maven.org/maven2/org/apache/httpcomponents/httpclient/4.4/httpclient-4.4.jar
 (703 KB at 13773.4 KB/sec)
[INFO] Downloading: 
http://repo1.maven.org/maven2/org/igniterealtime/smack/wso2/smackx/3.0.4.wso2v1/smackx-3.0.4.wso2v1.jar
[INFO] Downloaded: 
http://repo1.maven.org/maven2/commons-io/commons-io/2.0/commons-io-2.0.jar (156 
KB at 2990.4 KB/sec)
[INFO] Downloading: 
http://repo1.maven.org/maven2/jaxen/jaxen/1.1.1/jaxen-1.1.1.jar
[INFO] Downloading: http://repo1.maven.org/maven2/jdom/jdom/1.0/jdom-1.0.jar
[INFO] Downloading: 
http://repo1.maven.org/maven2/xml-apis/xml-apis/1.3.02/xml-apis-1.3.02.jar
[INFO] Downloading: 
http://repo1.maven.org/maven2/xerces/xercesImpl/2.6.2/xercesImpl-2.6.2.jar
[INFO] Downloaded: 
http://repo1.maven.org/maven2/jaxen/jaxen/1.1.1/jaxen-1.1.1.jar (222 KB at 
3077.7 KB/sec)
[INFO] Downloading: http://repo1.maven.org/maven2/xom/xom/1.0/xom-1.0.jar
[INFO] Downloaded: 
http://repo1.maven.org/maven2/org/codehaus/woodstox/wstx-asl/3.2.9/wstx-asl-3.2.9.jar
 (512 KB at 6825.8 KB/sec)
[INFO] Downloading: 
http://repo1.maven.org/maven2/xerces/xmlParserAPIs/2.6.2/xmlParserAPIs-2.6.2.jar
[INFO] Downloaded: http://repo1.maven.org/maven2/jdom/jdom/1.0/jdom-1.0.jar 
(150 KB at 2078.6 KB/sec)
[INFO] Downloading: 
http://repo1.maven.org/maven2/xalan/xalan/2.6.0/xalan-2.6.0.jar
[INFO] Downloaded: 
http://repo1.maven.org/maven2/xml-apis/xml-apis/1.3.02/xml-apis-1.3.02.jar (190 
KB at 2495.4 KB/sec)
[INFO] Downloading: 
http://repo1.maven.org/maven2/com/ibm/icu/icu4j/2.6.1/icu4j-2.6.1.jar
[INFO] Downloaded: http://repo1.maven.org/maven2/xom/xom/1.0/xom-1.0.jar (107 
KB at 1329.0 KB/sec)
[INFO] Downloading: 
http://repo1.maven.org/maven2/commons-fileupload/wso2/commons-fileupload/1.2.0.wso2v1/commons-fileupload-1.2.0.wso2v1.jar
[INFO] Downloaded: 
http://repo1.maven.org/maven2/xerces/xmlParserAPIs/2.6.2/xmlParserAPIs-2.6.2.jar
 (122 KB at 1416.3 KB/sec)
[INFO] Downloading: 
http://repo1.maven.org/maven2/commons-fileupload/commons-fileupload/1.2/commons-fileupload-1.2.jar
[INFO] Downloading: 
http://repo1.maven.org/maven2/org/apache/ant/wso2/ant/1.7.0.wso2v1/ant-1.7.0.wso2v1.jar
[INFO] Downloaded: 
http://repo1.maven.org/maven2/xerces/xercesImpl/2.6.2/xercesImpl-2.6.2.jar (987 
KB at 10728.1 KB/sec)
[INFO] Downloading: 
http://repo1.maven.org/maven2/org/apache/ant/ant/1.7.0/ant-1.7.0.jar
[INFO] Downloading: 
http://repo1.maven.org/maven2/org/apache/ant/ant-launcher/1.7.0/ant-launcher-1.7.0.jar
[INFO] Downloaded: 
http://repo1.maven.org/maven2/commons-fileupload/commons-fileupload/1.2/commons-fileupload-1.2.jar
 (52 KB at 545.7 KB/sec)
[INFO] Downloading: 
http://repo1.maven.org/maven2/org/eclipse/equinox/javax.servlet/3.0.0.v201112011016/javax.servlet-3.0.0.v201112011016.jar
[INFO] Downloaded: 
http://repo1.maven.org/maven2/org/apache/ant/ant-launcher/1.7.0/ant-launcher-1.7.0.jar
 (12 KB at 109.1 KB/sec)
[INFO] Downloading: 
http://repo1.maven.org/maven2/commons-httpclient/wso2/commons-httpclient/3.1.0.wso2v2/commons-httpclient-3.1.0.wso2v2.jar
[INFO] Downloading: 
http://repo1.maven.org/maven2/org/apache/commons/ssl/not-yet-commons-ssl/0.3.9/not-yet-commons-ssl-0.3.9.jar
[INFO] Downloading: 
http://repo1.maven.org/maven2/org/wso2/carbon/org.wso2.carbon.registry.api/4.2.0/org.wso2.carbon.registry.api-4.2.0.jar
[INFO] Downloading: 
http://repo1.maven.org/maven2/org/wso2/carbon/org.wso2.carbon.identity.entitlement.stub/4.2.1/org.wso2.carbon.identity.entitlement.stub-4.2.1.jar
[INFO] Downloading: 
http://repo1.maven.org/maven2/org/wso2/carbon/org.wso2.carbon.identity.entitlement.common/4.2.1/org.wso2.carbon.identity.entitlement.common-4.2.1.jar
[INFO] Downloading: 
http://repo1.maven.org/maven2/org/wso2/balana/org.wso2.balana.utils/1.0.0-wso2v6/org.wso2.balana.utils-1.0.0-wso2v6.jar
[INFO] Downloading: 
http://repo1.maven.org/maven2/org/wso2/carbon/org.wso2.carbon.registry.core/4.2.0/org.wso2.carbon.registry.core-4.2.0.jar
[INFO] Downloading: 
http://repo1.maven.org/maven2/commons-io/wso2/commons-io/2.0.0.wso2v2/commons-io-2.0.0.wso2v2.jar
[INFO] Downloaded: 
http://repo1.maven.org/maven2/org/apache/ant/ant/1.7.0/ant-1.7.0.jar (1260 KB 
at 10076.6 KB/sec)
[INFO] Downloading:

[jira] [Commented] (AIRAVATA-2200) Allow user to select their own compute resource account when creating experiment

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


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

ASF GitHub Bot commented on AIRAVATA-2200:
--

Github user asfgit closed the pull request at:

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


> Allow user to select their own compute resource account when creating 
> experiment
> 
>
> Key: AIRAVATA-2200
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2200
> Project: Airavata
>  Issue Type: Bug
>Reporter: Marcus Christie
>Assignee: Marcus Christie
>
> If the user has configured their own compute resource account (see EINT-2152) 
> then they should be able to select that and run an experiment under their own 
> account.
> h3. Testing to do once backend is updated
> * Scenario: User A creates an experiment to run under their own compute 
> resource account. User A shares experiment with User B, read only. User B 
> clones the experiment but User B doesn't have their own compute resource 
> account on that compute resource. User B's cloned experiment should not have 
> useUserCRPref checkbox checked



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

[jira] [Commented] (AIRAVATA-2200) Allow user to select their own compute resource account when creating experiment

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


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

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

Commit 00094b4c82d3c1eb2fa7b509784c1008e3f6f7ed 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=00094b4 ]

AIRAVATA-2200 User can opt to use their own compute resource account


> Allow user to select their own compute resource account when creating 
> experiment
> 
>
> Key: AIRAVATA-2200
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2200
> Project: Airavata
>  Issue Type: Bug
>Reporter: Marcus Christie
>Assignee: Marcus Christie
>
> If the user has configured their own compute resource account (see EINT-2152) 
> then they should be able to select that and run an experiment under their own 
> account.
> h3. Testing to do once backend is updated
> * Scenario: User A creates an experiment to run under their own compute 
> resource account. User A shares experiment with User B, read only. User B 
> clones the experiment but User B doesn't have their own compute resource 
> account on that compute resource. User B's cloned experiment should not have 
> useUserCRPref checkbox checked



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

[jira] [Commented] (AIRAVATA-2200) Allow user to select their own compute resource account when creating experiment

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


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

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

Commit 5f6e8e445819b6c9198b59ae34e3b5d71d1c22dd 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=5f6e8e4 ]

AIRAVATA-2200 Check useUserCRPref when cloning

Uncheck useUserCRPref if cloned by user who doesn't have user compute
resource preference for that compute resource.


> Allow user to select their own compute resource account when creating 
> experiment
> 
>
> Key: AIRAVATA-2200
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2200
> Project: Airavata
>  Issue Type: Bug
>Reporter: Marcus Christie
>Assignee: Marcus Christie
>
> If the user has configured their own compute resource account (see EINT-2152) 
> then they should be able to select that and run an experiment under their own 
> account.
> h3. Testing to do once backend is updated
> * Scenario: User A creates an experiment to run under their own compute 
> resource account. User A shares experiment with User B, read only. User B 
> clones the experiment but User B doesn't have their own compute resource 
> account on that compute resource. User B's cloned experiment should not have 
> useUserCRPref checkbox checked



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

[jira] [Commented] (AIRAVATA-2200) Allow user to select their own compute resource account when creating experiment

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


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

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

Commit 291f3b50f9d4f419b4b1f62af670be17eeeb9a45 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=291f3b5 ]

AIRAVATA-2200 User's personal compute account added to summary page


> Allow user to select their own compute resource account when creating 
> experiment
> 
>
> Key: AIRAVATA-2200
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2200
> Project: Airavata
>  Issue Type: Bug
>Reporter: Marcus Christie
>Assignee: Marcus Christie
>
> If the user has configured their own compute resource account (see EINT-2152) 
> then they should be able to select that and run an experiment under their own 
> account.
> h3. Testing to do once backend is updated
> * Scenario: User A creates an experiment to run under their own compute 
> resource account. User A shares experiment with User B, read only. User B 
> clones the experiment but User B doesn't have their own compute resource 
> account on that compute resource. User B's cloned experiment should not have 
> useUserCRPref checkbox checked



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

[GitHub] airavata-php-gateway pull request #32: AIRAVATA-2200 allow user compute reso...

2016-11-04 Thread asfgit

Github user asfgit closed the pull request at:

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


---
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-2200) Allow user to select their own compute resource account when creating experiment

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


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

ASF GitHub Bot commented on AIRAVATA-2200:
--

Github user machristie commented on the issue:

https://github.com/apache/airavata-php-gateway/pull/32
  
Okay, I've added the changes for cloning, so this is ready for review.


> Allow user to select their own compute resource account when creating 
> experiment
> 
>
> Key: AIRAVATA-2200
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2200
> Project: Airavata
>  Issue Type: Bug
>Reporter: Marcus Christie
>Assignee: Marcus Christie
>
> If the user has configured their own compute resource account (see EINT-2152) 
> then they should be able to select that and run an experiment under their own 
> account.
> h3. Testing to do once backend is updated
> * Scenario: User A creates an experiment to run under their own compute 
> resource account. User A shares experiment with User B, read only. User B 
> clones the experiment but User B doesn't have their own compute resource 
> account on that compute resource. User B's cloned experiment should not have 
> useUserCRPref checkbox checked



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

[GitHub] airavata-php-gateway issue #32: AIRAVATA-2200 allow user compute resource se...

2016-11-04 Thread machristie

Github user machristie commented on the issue:

https://github.com/apache/airavata-php-gateway/pull/32
  
Okay, I've added the changes for cloning, so this is ready for review.


---
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-2190) User A shared a single experiment with User B, read access. Project is also shared now with User B.

2016-11-04 Thread Marcus Christie (JIRA)


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

Marcus Christie commented on AIRAVATA-2190:
---

The code changes are done and have been merged. Still need to redeploy the API 
server and PGA and do some testing.

> 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] [Updated] (AIRAVATA-2200) Allow user to select their own compute resource account when creating experiment

2016-11-04 Thread Marcus Christie (JIRA)


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

Marcus Christie updated AIRAVATA-2200:
--
Description: 
If the user has configured their own compute resource account (see EINT-2152) 
then they should be able to select that and run an experiment under their own 
account.

h3. Testing to do once backend is updated
* Scenario: User A creates an experiment to run under their own compute 
resource account. User A shares experiment with User B, read only. User B 
clones the experiment but User B doesn't have their own compute resource 
account on that compute resource. User B's cloned experiment should not have 
useUserCRPref checkbox checked

  was:If the user has configured their own compute resource account (see 
EINT-2152) then they should be able to select that and run an experiment under 
their own account.


> Allow user to select their own compute resource account when creating 
> experiment
> 
>
> Key: AIRAVATA-2200
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2200
> Project: Airavata
>  Issue Type: Bug
>Reporter: Marcus Christie
>Assignee: Marcus Christie
>
> If the user has configured their own compute resource account (see EINT-2152) 
> then they should be able to select that and run an experiment under their own 
> account.
> h3. Testing to do once backend is updated
> * Scenario: User A creates an experiment to run under their own compute 
> resource account. User A shares experiment with User B, read only. User B 
> clones the experiment but User B doesn't have their own compute resource 
> account on that compute resource. User B's cloned experiment should not have 
> useUserCRPref checkbox checked



--
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-04 Thread anujbhan

Github user anujbhan commented on the issue:

https://github.com/apache/airavata/pull/74
  
@shamrath,
Method signatures for fetching the Credential Summary data have been 
changed as a part of optimization, These changes should reflect in the 
PHP-Gateway implementation. I have informed Marcus about the same.


---
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-2200) Allow user to select their own compute resource account when creating experiment

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


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

ASF GitHub Bot commented on AIRAVATA-2200:
--

Github user machristie commented on the issue:

https://github.com/apache/airavata-php-gateway/pull/32
  
This pull request isn't quite ready. I need to test with and maybe make 
some updates for experiment cloning.


> Allow user to select their own compute resource account when creating 
> experiment
> 
>
> Key: AIRAVATA-2200
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2200
> Project: Airavata
>  Issue Type: Bug
>Reporter: Marcus Christie
>Assignee: Marcus Christie
>
> If the user has configured their own compute resource account (see EINT-2152) 
> then they should be able to select that and run an experiment under their own 
> account.



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

[GitHub] airavata-php-gateway issue #32: AIRAVATA-2200 allow user compute resource se...

2016-11-04 Thread machristie

Github user machristie commented on the issue:

https://github.com/apache/airavata-php-gateway/pull/32
  
This pull request isn't quite ready. I need to test with and maybe make 
some updates for experiment cloning.


---
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-2200) Allow user to select their own compute resource account when creating experiment

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


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

ASF GitHub Bot commented on AIRAVATA-2200:
--

GitHub user machristie opened a pull request:

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

AIRAVATA-2200 allow user compute resource selection



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

$ git pull https://github.com/machristie/airavata-php-gateway 
AIRAVATA-2200-allow-user-compute-resource-selection

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

https://github.com/apache/airavata-php-gateway/pull/32.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 #32


commit 00094b4c82d3c1eb2fa7b509784c1008e3f6f7ed
Author: Marcus Christie 
Date:   2016-11-04T20:00:50Z

AIRAVATA-2200 User can opt to use their own compute resource account

commit 291f3b50f9d4f419b4b1f62af670be17eeeb9a45
Author: Marcus Christie 
Date:   2016-11-04T20:12:22Z

AIRAVATA-2200 User's personal compute account added to summary page




> Allow user to select their own compute resource account when creating 
> experiment
> 
>
> Key: AIRAVATA-2200
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2200
> Project: Airavata
>  Issue Type: Bug
>Reporter: Marcus Christie
>Assignee: Marcus Christie
>
> If the user has configured their own compute resource account (see EINT-2152) 
> then they should be able to select that and run an experiment under their own 
> account.



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

[GitHub] airavata-php-gateway pull request #32: AIRAVATA-2200 allow user compute reso...

2016-11-04 Thread machristie

GitHub user machristie opened a pull request:

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

AIRAVATA-2200 allow user compute resource selection



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

$ git pull https://github.com/machristie/airavata-php-gateway 
AIRAVATA-2200-allow-user-compute-resource-selection

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

https://github.com/apache/airavata-php-gateway/pull/32.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 #32


commit 00094b4c82d3c1eb2fa7b509784c1008e3f6f7ed
Author: Marcus Christie 
Date:   2016-11-04T20:00:50Z

AIRAVATA-2200 User can opt to use their own compute resource account

commit 291f3b50f9d4f419b4b1f62af670be17eeeb9a45
Author: Marcus Christie 
Date:   2016-11-04T20:12:22Z

AIRAVATA-2200 User's personal compute account added to summary page




---
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] [Created] (AIRAVATA-2209) Send all details that users provides during account creation in the email even if they are blank.

2016-11-04 Thread Sudhakar Pamidighantam (JIRA)

Sudhakar Pamidighantam created AIRAVATA-2209:


 Summary: Send all details that users provides during account 
creation in the email even if they are blank.
 Key: AIRAVATA-2209
 URL: https://issues.apache.org/jira/browse/AIRAVATA-2209
 Project: Airavata
  Issue Type: Sub-task
Reporter: Sudhakar Pamidighantam






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

[jira] [Created] (AIRAVATA-2208) Admin should be able contact users through PGA

2016-11-04 Thread Sudhakar Pamidighantam (JIRA)

Sudhakar Pamidighantam created AIRAVATA-2208:


 Summary: Admin should be able contact users through PGA 
 Key: AIRAVATA-2208
 URL: https://issues.apache.org/jira/browse/AIRAVATA-2208
 Project: Airavata
  Issue Type: Sub-task
Reporter: Sudhakar Pamidighantam
Priority: Minor


Admin should be able to contact users from Dashboard  and the data recorded  
eventually into user profile.



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

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

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


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

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

Commit 35a9e8e50ecc427e88bf121d5ec42615bea18448 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=35a9e8e ]

AIRAVATA-2190 Check data-sharing-enabled flag


> 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-2190) User A shared a single experiment with User B, read access. Project is also shared now with User B.

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


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

ASF GitHub Bot commented on AIRAVATA-2190:
--

Github user asfgit closed the pull request at:

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


> 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-2190) User A shared a single experiment with User B, read access. Project is also shared now with User B.

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


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

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

Commit 0d58af524d86fefb9566008aab7ab0e39bc571bd 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=0d58af5 ]

AIRAVATA-2190 Updating Thrift stubs


> 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-2190) User A shared a single experiment with User B, read access. Project is also shared now with User B.

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


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

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

Commit 071a027a134037ef63192e1e3dd99172fa306518 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=071a027 ]

AIRAVATA-2190 Must have write perm to edit/cancel


> 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-2190) User A shared a single experiment with User B, read access. Project is also shared now with User B.

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


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

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

Commit f76343df20524fcf8e8595f519555c0de33f4df4 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=f76343d ]

AIRAVATA-2190 Select project when cloning experiment


> 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-2190) User A shared a single experiment with User B, read access. Project is also shared now with User B.

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


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

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

Commit 0455ebd7f3d0a2214e901b9f29b915046b65b620 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=0455ebd ]

AIRAVATA-2190 Project no longer automatically shared

When experiment is shared with a user, project is no longer
automatically also shared, which was a workaround on the PGA side for a
data sharing issue that no longer exists with the current implementation.


> 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-2190) User A shared a single experiment with User B, read access. Project is also shared now with User B.

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


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

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

Commit 81f3b130ee77462bfd898fadfc638aaeeddb2ef7 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=81f3b13 ]

AIRAVATA-2190 Only show writeable projects when creating experiment

Also removed older project sharing code that is no longer applicable.


> 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-2190) User A shared a single experiment with User B, read access. Project is also shared now with User B.

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


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

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

Commit 61e36dd04d6fb28231103cc4ba5345b2fb1773ad 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=61e36dd ]

AIRAVATA-2190 Handling errors when cloning


> 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)

[GitHub] airavata-php-gateway pull request #31: AIRAVATA-2190 Experiment sharing fixe...

2016-11-04 Thread asfgit

Github user asfgit closed the pull request at:

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


---
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-04 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on AIRAVATA-2163:
--

GitHub user anujbhan opened a pull request:

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

AIRAVATA-2163: Optimising the cred store data model

This pull request resolves, 
https://issues.apache.org/jira/browse/AIRAVATA-2163

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

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

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

https://github.com/apache/airavata/pull/74.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 #74


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

AIRAVATA-2163: Optimising the cred store data model




> 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
>
> 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-04 Thread anujbhan

GitHub user anujbhan opened a pull request:

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

AIRAVATA-2163: Optimising the cred store data model

This pull request resolves, 
https://issues.apache.org/jira/browse/AIRAVATA-2163

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

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

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

https://github.com/apache/airavata/pull/74.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 #74


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

AIRAVATA-2163: Optimising the cred store data model




---
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 #31: AIRAVATA-2190 Experiment sharing fixe...

2016-11-04 Thread machristie

GitHub user machristie opened a pull request:

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

AIRAVATA-2190 Experiment sharing fixes



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

$ git pull https://github.com/machristie/airavata-php-gateway 
AIRAVATA-2190-single-experiment-shared-project-shared

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

https://github.com/apache/airavata-php-gateway/pull/31.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 #31


commit 0455ebd7f3d0a2214e901b9f29b915046b65b620
Author: Marcus Christie 
Date:   2016-11-02T19:58:32Z

AIRAVATA-2190 Project no longer automatically shared

When experiment is shared with a user, project is no longer
automatically also shared, which was a workaround on the PGA side for a
data sharing issue that no longer exists with the current implementation.

commit 071a027a134037ef63192e1e3dd99172fa306518
Author: Marcus Christie 
Date:   2016-11-02T20:34:47Z

AIRAVATA-2190 Must have write perm to edit/cancel

commit 0d58af524d86fefb9566008aab7ab0e39bc571bd
Author: Marcus Christie 
Date:   2016-11-04T16:11:37Z

AIRAVATA-2190 Updating Thrift stubs

commit f76343df20524fcf8e8595f519555c0de33f4df4
Author: Marcus Christie 
Date:   2016-11-04T16:12:47Z

AIRAVATA-2190 Select project when cloning experiment

commit 61e36dd04d6fb28231103cc4ba5345b2fb1773ad
Author: Marcus Christie 
Date:   2016-11-04T16:39:30Z

AIRAVATA-2190 Handling errors when cloning

commit 81f3b130ee77462bfd898fadfc638aaeeddb2ef7
Author: Marcus Christie 
Date:   2016-11-04T16:49:50Z

AIRAVATA-2190 Only show writeable projects when creating experiment

Also removed older project sharing code that is no longer applicable.

commit 35a9e8e50ecc427e88bf121d5ec42615bea18448
Author: Marcus Christie 
Date:   2016-11-04T17:04:27Z

AIRAVATA-2190 Check data-sharing-enabled flag




---
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-2190) User A shared a single experiment with User B, read access. Project is also shared now with User B.

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


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

ASF GitHub Bot commented on AIRAVATA-2190:
--

GitHub user machristie opened a pull request:

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

AIRAVATA-2190 Experiment sharing fixes



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

$ git pull https://github.com/machristie/airavata-php-gateway 
AIRAVATA-2190-single-experiment-shared-project-shared

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

https://github.com/apache/airavata-php-gateway/pull/31.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 #31


commit 0455ebd7f3d0a2214e901b9f29b915046b65b620
Author: Marcus Christie 
Date:   2016-11-02T19:58:32Z

AIRAVATA-2190 Project no longer automatically shared

When experiment is shared with a user, project is no longer
automatically also shared, which was a workaround on the PGA side for a
data sharing issue that no longer exists with the current implementation.

commit 071a027a134037ef63192e1e3dd99172fa306518
Author: Marcus Christie 
Date:   2016-11-02T20:34:47Z

AIRAVATA-2190 Must have write perm to edit/cancel

commit 0d58af524d86fefb9566008aab7ab0e39bc571bd
Author: Marcus Christie 
Date:   2016-11-04T16:11:37Z

AIRAVATA-2190 Updating Thrift stubs

commit f76343df20524fcf8e8595f519555c0de33f4df4
Author: Marcus Christie 
Date:   2016-11-04T16:12:47Z

AIRAVATA-2190 Select project when cloning experiment

commit 61e36dd04d6fb28231103cc4ba5345b2fb1773ad
Author: Marcus Christie 
Date:   2016-11-04T16:39:30Z

AIRAVATA-2190 Handling errors when cloning

commit 81f3b130ee77462bfd898fadfc638aaeeddb2ef7
Author: Marcus Christie 
Date:   2016-11-04T16:49:50Z

AIRAVATA-2190 Only show writeable projects when creating experiment

Also removed older project sharing code that is no longer applicable.

commit 35a9e8e50ecc427e88bf121d5ec42615bea18448
Author: Marcus Christie 
Date:   2016-11-04T17:04:27Z

AIRAVATA-2190 Check data-sharing-enabled flag




> 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)

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

2016-11-04 Thread Apache Jenkins Server

See

[GitHub] airavata pull request #73: Thrift CPI service Script for User Profile

2016-11-04 Thread abhijitkaranjkar89

GitHub user abhijitkaranjkar89 opened a pull request:

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

Thrift CPI service Script for User Profile



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

$ git pull https://github.com/abhijitkaranjkar89/airavata 
registry-refactoring

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

https://github.com/apache/airavata/pull/73.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 #73


commit 659da19e334dd03e632b59c390647bcb291b93ea
Author: Abhiit Karanjkar 
Date:   2016-11-04T15:48:14Z

Thrift CPI service Script for User Profile




---
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 #72: AIRAVATA-2190 clone experiment in different proje...

2016-11-04 Thread asfgit

Github user asfgit closed the pull request at:

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


---
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-2190) User A shared a single experiment with User B, read access. Project is also shared now with User B.

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


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

ASF GitHub Bot commented on AIRAVATA-2190:
--

Github user asfgit closed the pull request at:

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


> 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-2190) User A shared a single experiment with User B, read access. Project is also shared now with User B.

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


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

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

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

Merge branch 'AIRAVATA-2190-clone-experiment-in-different-project' of 
https://github.com/machristie/airavata into develop
lternatively you can review and apply these changes as the patch at:


> 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-2190) User A shared a single experiment with User B, read access. Project is also shared now with User B.

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


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

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

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

AIRAVATA-2190 cloneExperiment: check for project write access


> 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-2190) User A shared a single experiment with User B, read access. Project is also shared now with User B.

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


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

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

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

AIRAVATA-2190 Add newExperimentProjectId to cloneExperiment


> 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)

[GitHub] airavata pull request #72: AIRAVATA-2190 clone experiment in different proje...

2016-11-04 Thread machristie

GitHub user machristie opened a pull request:

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

AIRAVATA-2190 clone experiment in different project



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

$ git pull https://github.com/machristie/airavata 
AIRAVATA-2190-clone-experiment-in-different-project

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

https://github.com/apache/airavata/pull/72.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 #72


commit a36adaf96f492c0dd5038236772df7d19b7e2668
Author: Marcus Christie 
Date:   2016-11-04T14:30:55Z

AIRAVATA-2190 Add newExperimentProjectId to cloneExperiment

commit e275b7bc55980ee5360a547288eaa7f50664c7dd
Author: Marcus Christie 
Date:   2016-11-04T15:05:42Z

AIRAVATA-2190 cloneExperiment: check for project write access




---
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.
---

Jenkins build is still unstable: airavata-dev #1134

2016-11-04 Thread Apache Jenkins Server

See

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

2016-11-04 Thread Apache Jenkins Server

See

Jenkins build is unstable: airavata-dev #1133

2016-11-04 Thread Apache Jenkins Server

See

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

2016-11-04 Thread Apache Jenkins Server

See

Build failed in Jenkins: airavata-dev #1132

2016-11-04 Thread Apache Jenkins Server

See 

--
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on ubuntu-us1 (Ubuntu ubuntu docker) in workspace 
/home/jenkins/jenkins-slave/workspace/airavata-dev
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/airavata.git # timeout=10
Fetching upstream changes from 
https://git-wip-us.apache.org/repos/asf/airavata.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/airavata.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/develop^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/develop^{commit} # timeout=10
Checking out Revision 0717ae34a3b6760b7ce36bfa8191b27d708e2f52 
(refs/remotes/origin/develop)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 0717ae34a3b6760b7ce36bfa8191b27d708e2f52
 > git rev-list 0717ae34a3b6760b7ce36bfa8191b27d708e2f52 # timeout=10
Parsing POMs
Modules changed, recalculating dependency graph
ERROR: Processing failed due to a bug in the code. Please report this to 
jenkinsci-us...@googlegroups.com
hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown
at hudson.remoting.Request.abort(Request.java:303)
at hudson.remoting.Channel.terminate(Channel.java:847)
at hudson.remoting.Channel$CloseCommand.execute(Channel.java:1080)
at hudson.remoting.Channel$1.handle(Channel.java:501)
at 
hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:83)
at ..remote call to ubuntu-us1(Native Method)
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416)
at hudson.remoting.Request.call(Request.java:172)
at hudson.remoting.Channel.call(Channel.java:780)
at 
hudson.maven.AbstractMavenProcessFactory.newProcess(AbstractMavenProcessFactory.java:266)
at hudson.maven.ProcessCache.get(ProcessCache.java:236)
at 
hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:778)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534)
at hudson.model.Run.execute(Run.java:1741)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:410)
Caused by: hudson.remoting.Channel$OrderlyShutdown
at hudson.remoting.Channel$CloseCommand.execute(Channel.java:1080)
at hudson.remoting.Channel$1.handle(Channel.java:501)
at 
hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:83)
Caused by: Command close created at
at hudson.remoting.Command.(Command.java:56)
at hudson.remoting.Channel$CloseCommand.(Channel.java:1074)
at hudson.remoting.Channel$CloseCommand.(Channel.java:1072)
at hudson.remoting.Channel.close(Channel.java:1156)
at hudson.remoting.Channel.close(Channel.java:1138)
at hudson.remoting.Channel$CloseCommand.execute(Channel.java:1079)
... 2 more
project=hudson.maven.MavenModuleSet@5dd34e55[airavata-dev]
project.getModules()=[hudson.maven.MavenModule@4748f212[airavata-dev/org.apache.airavata:airavata][airavata-dev/org.apache.airavata:airavata][relativePath:],
 
hudson.maven.MavenModule@2afaec5d[airavata-dev/org.apache.airavata:airavata-api][airavata-dev/org.apache.airavata:airavata-api][relativePath:airavata-api],
 
hudson.maven.MavenModule@12fb150e[airavata-dev/org.apache.airavata:airavata-api-server][airavata-dev/org.apache.airavata:airavata-api-server][relativePath:airavata-api/airavata-api-server],
 
hudson.maven.MavenModule@5dd1136c[airavata-dev/org.apache.airavata:airavata-api-stubs][airavata-dev/org.apache.airavata:airavata-api-stubs][relativePath:airavata-api/airavata-api-stubs],
 
hudson.maven.MavenModule@180d13a8[airavata-dev/org.apache.airavata:airavata-client-configuration][airavata-dev/org.apache.airavata:airavata-client-configuration][relativePath:modules/configuration/client],
 
hudson.maven.MavenModule@49fbc49a[airavata-dev/org.apache.airavata:airavata-client-samples][airavata-dev/org.apache.airavata:airavata-client-samples][relativePath:airavata-api/airavata-client-sdks/java-client-samples],
 
hudson.maven.MavenModule@4a805634[airavata-dev/org.apache.airavata:airavata-client-sdks][airavata-dev/org.apache.airavata:airavata-client-sdks][relativePath:airavata-api/airavata-client-sdks],
 
hudson.maven.MavenModule@146cf24e[airavata-dev/org.apache.airavata:airavata-cloud][airavata-dev/org.apache.airavata:airavata-cloud][relativePath:modules/cloud],