date:20170124

GitHub user anujbhan opened a pull request:

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

Making corrections to user profile service code

Several changes in source code were needed to make this service working:

1. Added the user-profile service cpi thrift file to develop branch, it was 
missing
2. regenerated the thrift files to match other auto generated files (Add 
license, remove date through maven plugin)
3. made changes to all pom files related to user-profile service, made them 
consistant with other module pom files
4. changed the folder structure of user profile service to make it 
consistant with other modules
5. added correct class path for user-profile service in 
airavata-server.properties
6. Added dependency for user-profile service in distribution pom, to make 
the service discoverable when starting server
7. Made changes to thrift generation scripts to add user-profile thrift file
8. Removed unnecessary files
9. made changes to user profile server and handler files (Licence header 
etc)
10. Adding user profile service to serverMain.class (to start the server)

All the changes have been tested on jet stream airavata deployment.

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

$ git pull https://github.com/anujbhan/airavata userProfileService

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

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


commit 8f6f2183c42b1ce1432b93b4ade892f1f122fb2d
Author: Anuj Bhandar 
Date:   2017-01-24T23:45:59Z

making corrections to user profile service code

commit aa98eee4f34949a4a8fe09361fe59d6e93e22e36
Author: Anuj Bhandar 
Date:   2017-01-24T23:57:11Z

adding the server property file, which was left out in last commit

commit baaed53a372e7ab51eaed83b997dd604a29baf46
Author: Anuj Bhandar 
Date:   2017-01-25T00:00:16Z

adding dependancy for user-profile service in distribution pom

commit c6ba43bf685b953f575760894fb89910e2c22d14
Author: Anuj Bhandar 
Date:   2017-01-25T00:05:59Z

adding user profile service to server module




---
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 #3042

2017-01-24 Thread Apache Jenkins Server

See

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

2017-01-24 Thread Apache Jenkins Server

See

Jenkins build is still unstable: airavata-dev #3041

2017-01-24 Thread Apache Jenkins Server

See

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

2017-01-24 Thread Apache Jenkins Server

See

[jira] [Closed] (AIRAVATA-779) Xbaya: handling of StringArray is not consistent with URIArray

2017-01-24 Thread Eroma (JIRA)


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

Eroma closed AIRAVATA-779.
--

> Xbaya: handling of StringArray is not consistent with URIArray
> --
>
> Key: AIRAVATA-779
> URL: https://issues.apache.org/jira/browse/AIRAVATA-779
> Project: Airavata
>  Issue Type: Bug
>  Components: GFac, XBaya
>Reporter: Suresh Marru
>Assignee: Lahiru Gunathilake
> Fix For: 0.17
>
>
> Reported by Airavata user at - 
> https://gateways.atlassian.net/browse/PARAMCHEM-115



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

[jira] [Closed] (AIRAVATA-1118) Adding Permission attribute to XBaya main jar to follow recent JAVA security update guide line

2017-01-24 Thread Eroma (JIRA)


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

Eroma closed AIRAVATA-1118.
---

> Adding Permission attribute to XBaya main jar to follow recent JAVA security 
> update guide line
> --
>
> Key: AIRAVATA-1118
> URL: https://issues.apache.org/jira/browse/AIRAVATA-1118
> Project: Airavata
>  Issue Type: Improvement
>  Components: XBaya
>Affects Versions: 0.11
>Reporter: Heejoon Chae
>  Labels: patch, security
> Fix For: 0.17
>
> Attachments: issue_1118.patch
>
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> To follow recent JAVA security update guide (JAVA 7 update 51) below
> https://www.java.com/en/download/help/java_blocked.xml
> XBaya jnlp need to be updated with adding 'Permission' attribute within main 
> jar manifest file 



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

[jira] [Closed] (AIRAVATA-866) Automatically updating the user context (XBaya)

2017-01-24 Thread Eroma (JIRA)


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

Eroma closed AIRAVATA-866.
--

> Automatically updating the user context (XBaya) 
> 
>
> Key: AIRAVATA-866
> URL: https://issues.apache.org/jira/browse/AIRAVATA-866
> Project: Airavata
>  Issue Type: Improvement
>  Components: XBaya
>Affects Versions: 0.7
>Reporter: Taynov Alexey
>Assignee: Chathuri Wimalasena
> Fix For: 0.17
>
>
> Automatically updating the user context (XBaya) when adding new application 
> in registry.
> Now user must Refresh or reset active registry for getting new component in 
> xbaya component tree.



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

[jira] [Resolved] (AIRAVATA-2178) GFAC changes for user specific compute resource preferences

2017-01-24 Thread Eroma (JIRA)


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

Eroma resolved AIRAVATA-2178.
-
Resolution: Fixed

This is currently implemented and tested in https://dev.seagrid.org/


> GFAC changes for user specific compute resource preferences
> ---
>
> Key: AIRAVATA-2178
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2178
> Project: Airavata
>  Issue Type: Sub-task
>  Components: GFac
>Reporter: Eroma
>Assignee: Shameera Rathnayaka
> Fix For: 0.17
>
>




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

[jira] [Closed] (AIRAVATA-2178) GFAC changes for user specific compute resource preferences

2017-01-24 Thread Eroma (JIRA)


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

Eroma closed AIRAVATA-2178.
---

> GFAC changes for user specific compute resource preferences
> ---
>
> Key: AIRAVATA-2178
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2178
> Project: Airavata
>  Issue Type: Sub-task
>  Components: GFac
>Reporter: Eroma
>Assignee: Shameera Rathnayaka
> Fix For: 0.17
>
>




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

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

2017-01-24 Thread Apache Jenkins Server

See

Jenkins build is still unstable: airavata-dev #3040

2017-01-24 Thread Apache Jenkins Server

See

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

2017-01-24 Thread Eroma (JIRA)


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

Eroma closed AIRAVATA-2200.
---

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

Individual users can define their own account details in compute resources and 
run jobs. When they have their own account registered in the gateway they it 
will be selected as the default allocation to submit the job unless user 
selects community allocation by deselecting the use of his own allocation. 

> 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
> Fix For: 0.17
>
>
> 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
> ** verified on dev.seagrid.org



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