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

2016-10-12 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on AIRAVATA-2163:
--

Github user anujbhan commented on the issue:

https://github.com/apache/airavata/pull/54
  
@shamrath,

Here is the follow up JIRA : 
https://issues.apache.org/jira/browse/AIRAVATA-2163, and I have moved the 
credential store thrift file to data-models directory, though the actual data 
models will be created in credential-store modules directory.


> 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 issue #54: Adding SSH Credential summary data model

2016-10-12 Thread anujbhan 
Github user anujbhan commented on the issue:

https://github.com/apache/airavata/pull/54
  
@shamrath,

Here is the follow up JIRA : 
https://issues.apache.org/jira/browse/AIRAVATA-2163, and I have moved the 
credential store thrift file to data-models directory, though the actual data 
models will be created in credential-store modules directory.


---
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-2163) optimize credential store data models

2016-10-12 Thread Anuj Bhandar (JIRA) 
Anuj Bhandar created AIRAVATA-2163:
--

 Summary: 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


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 #54: Adding SSH Credential summary data model

2016-10-12 Thread shamrath 
Github user shamrath commented on the issue:

https://github.com/apache/airavata/pull/54
  
@anujbhan ,
Ok let's make this an exception. Please create follow up JIRA to track the 
pending improvements. I will review and merge this.


---
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 #52: Local provider Fix

2016-10-12 Thread asfgit 
Github user asfgit closed the pull request at:

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


---
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-2113) Resolve Local Provider Issues

2016-10-12 Thread ASF subversion and git services (JIRA) 

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

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

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

AIRAVATA-2113. Fixing local provider


> Resolve Local Provider Issues
> -
>
> Key: AIRAVATA-2113
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2113
> Project: Airavata
>  Issue Type: Task
>Reporter: Ajinkya
>Assignee: Ajinkya
>




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

[GitHub] airavata issue #54: Adding SSH Credential summary data model

2016-10-12 Thread anujbhan 
Github user anujbhan commented on the issue:

https://github.com/apache/airavata/pull/54
  
@smarru & @shamrath,

Optimization to this PR may take some time. Since this PR is critical, 
Please consider merging. I will submit the changes as soon as possible with 
another pull request.

The build is passing in my local environment, don't know why Travis is 
failing.


---
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-2162) Allow admin to see/edit user's compute/storage resource accounts

2016-10-12 Thread Marcus Christie (JIRA) 
Marcus Christie created AIRAVATA-2162:
-

 Summary: Allow admin to see/edit user's compute/storage resource 
accounts
 Key: AIRAVATA-2162
 URL: https://issues.apache.org/jira/browse/AIRAVATA-2162
 Project: Airavata
  Issue Type: New Feature
  Components: PGA PHP Web Gateway
Reporter: Marcus Christie
Assignee: Marcus Christie


This is relevant for the campus gateway type gateways. It will be useful for 
admins to be able to see and edit a user's registered compute/storage accounts, 
for example, in order to troubleshoot a problem a user is having with their 
account.



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

[jira] [Created] (AIRAVATA-2161) Display credentials per user in the Admin Credential Store

2016-10-12 Thread Marcus Christie (JIRA) 
Marcus Christie created AIRAVATA-2161:
-

 Summary: Display credentials per user in the Admin Credential Store
 Key: AIRAVATA-2161
 URL: https://issues.apache.org/jira/browse/AIRAVATA-2161
 Project: Airavata
  Issue Type: New Feature
  Components: PGA PHP Web Gateway
Reporter: Marcus Christie
Assignee: Marcus Christie


With the campus users adding their own credentials, the list of credentials in 
the Admin Credential Store view will grow to be very long. So we need to give 
the admin user a way to filter the list.  It will be useful for admins to be 
able to see user generated credentials so that they can help troubleshoot user 
issues.




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

[GitHub] airavata issue #54: Adding SSH Credential summary data model

2016-10-12 Thread anujbhan 
Github user anujbhan commented on the issue:

https://github.com/apache/airavata/pull/54
  
All the festures requested are there in  this PR. But i am working on the
additional changes prescribed by shameera

On Oct 12, 2016 2:16 PM, "Suresh Marru"  wrote:

Can we review and merge this now? I mean are you done working on this PR?

> On Oct 12, 2016, at 1:19 PM, Anuj Bhandar 
wrote:
>
> @smarru ,
> Method to fetch specific user's public keys with summary is added
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub <
https://github.com/apache/airavata/pull/54#issuecomment-253278638>, or mute
the thread .

>

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
, or mute
the thread


.



---
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 issue #54: Adding SSH Credential summary data model

2016-10-12 Thread smarru 
Github user smarru commented on the issue:

https://github.com/apache/airavata/pull/54
  
Can we review and merge this now? I mean are you done working on this PR?

> On Oct 12, 2016, at 1:19 PM, Anuj Bhandar  
wrote:
> 
> @smarru ,
> Method to fetch specific user's public keys with summary is added
> 
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub 
, or mute 
the thread 
.
> 




---
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 issue #54: Adding SSH Credential summary data model

2016-10-12 Thread anujbhan 
Github user anujbhan commented on the issue:

https://github.com/apache/airavata/pull/54
  
@smarru,
Method to fetch specific user's public keys with summary is added


---
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 #52: Local provider Fix

2016-10-12 Thread shamrath 
Github user shamrath commented on a diff in the pull request:

https://github.com/apache/airavata/pull/52#discussion_r83044405
  
--- Diff: 
modules/orchestrator/orchestrator-core/src/main/java/org/apache/airavata/orchestrator/cpi/impl/SimpleOrchestratorImpl.java
 ---
@@ -406,11 +406,17 @@ private String getTaskDag(List taskIdList) {
 DataType type = processOutput.getType();
 switch (type) {
 case STDOUT :
-processOutput.setValue(appName + ".stdout");
+if(null == processOutput.getValue() ||
+(null != processOutput.getValue() && 
processOutput.getValue().trim().isEmpty())){
+processOutput.setValue(appName + ".stdout");
+}
 createOutputDataSatagingTasks(processModel, 
gatewayId, dataStagingTaskIds, processOutput);
 break;
 case STDERR:
-processOutput.setValue(appName + ".stderr");
+if(null == processOutput.getValue() ||
--- End diff --

Simplify the logic


---
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 #52: Local provider Fix

2016-10-12 Thread shamrath 
Github user shamrath commented on a diff in the pull request:

https://github.com/apache/airavata/pull/52#discussion_r83044484
  
--- Diff: 
modules/orchestrator/orchestrator-core/src/main/java/org/apache/airavata/orchestrator/cpi/impl/SimpleOrchestratorImpl.java
 ---
@@ -406,11 +406,17 @@ private String getTaskDag(List taskIdList) {
 DataType type = processOutput.getType();
 switch (type) {
 case STDOUT :
-processOutput.setValue(appName + ".stdout");
+if(null == processOutput.getValue() ||
+(null != processOutput.getValue() && 
processOutput.getValue().trim().isEmpty())){
--- End diff --

You can simplify this logic to (processOutput.getValue == null || 
processOutput.getvalue().trim().isEmpty())


---
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-2156) UI for credential store token + key generation for portal users to use with their campus logins.

2016-10-12 Thread Marcus Christie (JIRA) 

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

Marcus Christie commented on AIRAVATA-2156:
---

Discussed my questions with [~smarru], [~anujbhan]:
* Anuj will add an API method to get SSH public keys for a given user
** we'll use the username field of the SSH public key data model. The username 
is the portal username, not the login username
* the UI DOES NOT need to allow a user to generate password credentials. We 
only currently use that for password access to Identity Server.
* We need to have some way to display credentials per user in the admin 
credential store page, otherwise it will be too long/overwhelming

At some point we need some interface that would allow an admin to see and 
change user's compute and storage settings.

> UI for credential store token + key generation for portal users to use with 
> their campus logins.
> 
>
> Key: AIRAVATA-2156
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2156
> Project: Airavata
>  Issue Type: Bug
>  Components: PGA PHP Web Gateway
>Reporter: Marcus Christie
>Assignee: Marcus Christie
>




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

[jira] [Created] (AIRAVATA-2160) In 'Data Sharing' what access are provided for 'read' access and 'write' access?

2016-10-12 Thread Eroma (JIRA) 
Eroma created AIRAVATA-2160:
---

 Summary: In 'Data Sharing' what access are provided for 'read' 
access and 'write' access?
 Key: AIRAVATA-2160
 URL: https://issues.apache.org/jira/browse/AIRAVATA-2160
 Project: Airavata
  Issue Type: Brainstorming
  Components: Airavata System, PGA PHP Web Gateway
Reporter: Eroma
Assignee: Supun Chathuranga Nakandala


In 'Data Sharing' what access are provided for 'read' access and 'write' access?

IMO
Read Access
1. Should be able to view the experiment or the project.
2. If its an experiment should be able to download inputs and outputs.
3. Should be able to launch, clone the experiment.
4. Should not be able to Cancel an ongoing experiment.
5. Should not be able to share or un-share the shared experiment or project 
with others.

Write Access
1. All above privileges 1, 2, 3 of 'Read' access should be available.
2. Should be able to cancel an ongoing shared experiment.
3, Should be able to share the experiment and projects with others.
4. Should not be able to remove the owner of the project or experiment.



--
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-10-12 Thread Eroma (JIRA) 

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

Eroma commented on AIRAVATA-2015:
-

Should this be handled from airavata side or PGA side?
The notification will inform the users about shared projects and experiments.

> 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: Sub-task
>  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] [Updated] (AIRAVATA-2015) When a gateway user shares a project or an experiment have a notification sent

2016-10-12 Thread Eroma (JIRA) 

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

Eroma updated AIRAVATA-2015:

Assignee: Supun Chathuranga Nakandala  (was: Jeff Kinnison)

> 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: Sub-task
>  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] [Updated] (AIRAVATA-2021) User shared only a single experiment; project also got shared with the new user

2016-10-12 Thread Eroma (JIRA) 

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

Eroma updated AIRAVATA-2021:

Assignee: Supun Chathuranga Nakandala  (was: Jeff Kinnison)

> 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: Sub-task
>  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] [Commented] (AIRAVATA-2021) User shared only a single experiment; project also got shared with the new user

2016-10-12 Thread Eroma (JIRA) 

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

Eroma commented on AIRAVATA-2021:
-

So the without even original project owners knowledge other user can use the 
project and create experiment and also remove the original owner of the project 
from the sharing. Ideally the owner of a project should not be removed from the 
project or experiment even if the user has write access.

> 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: Sub-task
>  Components: PGA PHP Web Gateway
>Affects Versions: 0.17-SNAPSHOT
> Environment: https://dev.seagrid.org
>Reporter: Eroma
>Assignee: Jeff Kinnison
>
> 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] [Commented] (AIRAVATA-2021) User shared only a single experiment; project also got shared with the new user

2016-10-12 Thread Eroma (JIRA) 

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

Eroma commented on AIRAVATA-2021:
-

tested the same in current data sharing in https://dev.seagrid.org
When a single experiment is shared the whole project gets shared but under 
experiment shows only the shared experiment. So technically no harm there. When 
the user creates another experiment (he only has read rights to a single 
experiment) he can use the shared project and remove the owner of the project 
from the new experiment.

> 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: Sub-task
>  Components: PGA PHP Web Gateway
>Affects Versions: 0.17-SNAPSHOT
> Environment: https://dev.seagrid.org
>Reporter: Eroma
>Assignee: Jeff Kinnison
>
> 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] [Commented] (AIRAVATA-2159) SEAGrid Notice creation error.

2016-10-12 Thread Marcus Christie (JIRA) 

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

Marcus Christie commented on AIRAVATA-2159:
---

Supun found the problem. The NOTIFICATION_MESSAGE doesn't allow messages longer 
than 256 characters.  From the airavata.log on gw77
{noformat}
Caused by:  
org.apache.openjpa.persistence.Persisten
ceException: Data truncation: Data too long for column 'NOTIFICATION_MESSAGE' 
at row 1 {prepstmnt 13516
55151 
INSERT INTO NOTIFICATION (NOTIFICATION_ID, CREATION_DATE, 
EXPIRATION_DATE, GATEWAY_ID, NOTIFICATION_MESSAGE, PRIORITY, 
PUBLISHED_DATE, TITLE) 
VALUES (?, ?, ?, ?, ?, ?, ?, ?) 
[params=(String) 33ffca17-d998-4deb-9fb4-8e725c40b799, (Timestamp) 2016-10-12 
10:41:00.457, (Timestamp)
 2016-10-26 10:40:00.0, (String) seagrid, (String) We will be performing 
maintenance on the SDSC Datace
nter power infra..., (String) NORMAL, (Timestamp) 2016-10-19 10:40:00.0, 
(String) SDSC Comet, Gordon Ma
intenance]} [code=1406, state=22001]
FailedObject: 
org.apache.airavata.registry.core.experiment.catalog.model.Notification@74657c26
at 
org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDictionary.java:4918)
at 
org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionary.java:4878)
at 
org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:136)
at 
org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:78)
at 
org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushAndUpdate(PreparedStatement
ManagerImpl.java:143)
at 
org.apache.openjpa.jdbc.kernel.BatchingPreparedStatementManagerImpl.flushAndUpdate(BatchingP
reparedStatementManagerImpl.java:79)
at 
org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushInternal(PreparedStatementM
anagerImpl.java:99)
at 
org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flush(PreparedStatementManagerIm
pl.java:87)
at 
org.apache.openjpa.jdbc.kernel.ConstraintUpdateManager.flush(ConstraintUpdateManager.java:55
0)
at 
org.apache.openjpa.jdbc.kernel.ConstraintUpdateManager.flush(ConstraintUpdateManager.java:10
6)
at 
org.apache.openjpa.jdbc.kernel.BatchingConstraintUpdateManager.flush(BatchingConstraintUpdat
eManager.java:59)
at 
org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:103)
at 
org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:76)
at 
org.apache.openjpa.jdbc.kernel.JDBCStoreManager.flush(JDBCStoreManager.java:713)
at 
org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreManager.java:131)
... 28 more
Caused by: org.apache.openjpa.lib.jdbc.ReportingSQLException: Data truncation: 
Data too long for column
 'NOTIFICATION_MESSAGE' at row 1 {prepstmnt 1351655151 
INSERT INTO NOTIFICATION (NOTIFICATION_ID, CREATION_DATE, 
EXPIRATION_DATE, GATEWAY_ID, NOTIFICATION_MESSAGE, PRIORITY, 
PUBLISHED_DATE, TITLE) 
VALUES (?, ?, ?, ?, ?, ?, ?, ?) 
[params=(String) 33ffca17-d998-4deb-9fb4-8e725c40b799, (Timestamp) 2016-10-12 
10:41:00.457, (Timestamp) 2016-10-26 10:40:00.0, (String) seagrid, (String) We 
will be performing maintenance on the SDSC Datacenter power infra..., (String) 
NORMAL, (Timestamp) 2016-10-19 10:40:00.0, (String) SDSC Comet, Gordon 
Maintenance]} [code=1406, state=22001]
at 
org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:247)
at 
org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:223)
at 
org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.access$1000(LoggingConnectionDecorator.java:72)
...
{noformat}


> SEAGrid Notice creation error. 
> ---
>
> Key: AIRAVATA-2159
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2159
> Project: Airavata
>  Issue Type: Bug
>Reporter: Sudhakar Pamidighantam
>Assignee: Marcus Christie
>
> When I tried to create a new notice out of the recent XSEDE new from Mahidhar 
> (copied below) I get an error as follows 
> An error has occurred. Please try again later.
> Which repreats if I click on create button again. 
> Not sure if I am doing something. 
> Begin forwarded message:
> From: XSEDE User News 
> Subject: SDSC Comet, Gordon Maintenance: 6AM-6PM (PT), Oct 25, 2016
> Date: October 11, 2016 at 1:14:44 PM EDT
> To: 
> Reply-To: No Reply 
> A new message has been posted to XSEDE User News.
> Categories: Comet (SDSC), Gordon (SDSC)
> Start time: 25 Oct, 2016 06:00 PDT
> End time: 25 Oct, 2016 18:00 PDT
> Posted on 11 Oct, 2016 16:49 UTC by Mahidhar Tatineni
> We will be performing maintenance on the SDSC Datacenter power infrastructure 
> on Oct

[jira] [Commented] (AIRAVATA-2159) SEAGrid Notice creation error.

2016-10-12 Thread Marcus Christie (JIRA) 

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

Marcus Christie commented on AIRAVATA-2159:
---

[~scnakandala], looks like the database script already has the column at 4096: 
https://github.com/apache/airavata/blob/bfff64c58c58b62116f64d7c81b6fbc4d23d7d52/modules/registry/registry-core/src/main/resources/expcatalog-mysql.sql#L51-L51

Did this just not get migrated?

> SEAGrid Notice creation error. 
> ---
>
> Key: AIRAVATA-2159
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2159
> Project: Airavata
>  Issue Type: Bug
>Reporter: Sudhakar Pamidighantam
>Assignee: Marcus Christie
>
> When I tried to create a new notice out of the recent XSEDE new from Mahidhar 
> (copied below) I get an error as follows 
> An error has occurred. Please try again later.
> Which repreats if I click on create button again. 
> Not sure if I am doing something. 
> Begin forwarded message:
> From: XSEDE User News 
> Subject: SDSC Comet, Gordon Maintenance: 6AM-6PM (PT), Oct 25, 2016
> Date: October 11, 2016 at 1:14:44 PM EDT
> To: 
> Reply-To: No Reply 
> A new message has been posted to XSEDE User News.
> Categories: Comet (SDSC), Gordon (SDSC)
> Start time: 25 Oct, 2016 06:00 PDT
> End time: 25 Oct, 2016 18:00 PDT
> Posted on 11 Oct, 2016 16:49 UTC by Mahidhar Tatineni
> We will be performing maintenance on the SDSC Datacenter power infrastructure 
> on Oct 25, 2016. Both Comet and Gordon will be unavailable 6AM-6PM (PT) on 
> Tuesday, Oct 25, 2016. We have reservations in place on both machines so jobs 
> that do not fit in the window before the maintenance will be queued and run 
> after the maintenance is completed. Jobs will not run during the maintenance. 
> Please email h...@xsede.org if you have any questions.
> 
> This message was generated by XSEDE User News v3.0.  You can view this 
> message in the XSEDE User Portal at 
> https://portal.xsede.org/web/xup/user-news/-/news/item/7715.
> You can manage your XSEDE User News subscriptions at 
> https://portal.xsede.org/group/xup/user-news/-/news/manage-subscription.



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

[jira] [Commented] (AIRAVATA-2159) SEAGrid Notice creation error.

2016-10-12 Thread Marcus Christie (JIRA) 

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

Marcus Christie commented on AIRAVATA-2159:
---

Supun did a quick fix for this by making the NOTIFICATION_MESSAGE column 4096 
characters long.

I'll work on updating the SQL script.  Also, I think in the front end we can 
restrict the number of characters in the textarea.

> SEAGrid Notice creation error. 
> ---
>
> Key: AIRAVATA-2159
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2159
> Project: Airavata
>  Issue Type: Bug
>Reporter: Sudhakar Pamidighantam
>Assignee: Marcus Christie
>
> When I tried to create a new notice out of the recent XSEDE new from Mahidhar 
> (copied below) I get an error as follows 
> An error has occurred. Please try again later.
> Which repreats if I click on create button again. 
> Not sure if I am doing something. 
> Begin forwarded message:
> From: XSEDE User News 
> Subject: SDSC Comet, Gordon Maintenance: 6AM-6PM (PT), Oct 25, 2016
> Date: October 11, 2016 at 1:14:44 PM EDT
> To: 
> Reply-To: No Reply 
> A new message has been posted to XSEDE User News.
> Categories: Comet (SDSC), Gordon (SDSC)
> Start time: 25 Oct, 2016 06:00 PDT
> End time: 25 Oct, 2016 18:00 PDT
> Posted on 11 Oct, 2016 16:49 UTC by Mahidhar Tatineni
> We will be performing maintenance on the SDSC Datacenter power infrastructure 
> on Oct 25, 2016. Both Comet and Gordon will be unavailable 6AM-6PM (PT) on 
> Tuesday, Oct 25, 2016. We have reservations in place on both machines so jobs 
> that do not fit in the window before the maintenance will be queued and run 
> after the maintenance is completed. Jobs will not run during the maintenance. 
> Please email h...@xsede.org if you have any questions.
> 
> This message was generated by XSEDE User News v3.0.  You can view this 
> message in the XSEDE User Portal at 
> https://portal.xsede.org/web/xup/user-news/-/news/item/7715.
> You can manage your XSEDE User News subscriptions at 
> https://portal.xsede.org/group/xup/user-news/-/news/manage-subscription.



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

[jira] [Commented] (AIRAVATA-2159) SEAGrid Notice creation error.

2016-10-12 Thread Marcus Christie (JIRA) 

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

Marcus Christie commented on AIRAVATA-2159:
---

Sudhakar can you try to add your notice again?

> SEAGrid Notice creation error. 
> ---
>
> Key: AIRAVATA-2159
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2159
> Project: Airavata
>  Issue Type: Bug
>Reporter: Sudhakar Pamidighantam
>Assignee: Marcus Christie
>
> When I tried to create a new notice out of the recent XSEDE new from Mahidhar 
> (copied below) I get an error as follows 
> An error has occurred. Please try again later.
> Which repreats if I click on create button again. 
> Not sure if I am doing something. 
> Begin forwarded message:
> From: XSEDE User News 
> Subject: SDSC Comet, Gordon Maintenance: 6AM-6PM (PT), Oct 25, 2016
> Date: October 11, 2016 at 1:14:44 PM EDT
> To: 
> Reply-To: No Reply 
> A new message has been posted to XSEDE User News.
> Categories: Comet (SDSC), Gordon (SDSC)
> Start time: 25 Oct, 2016 06:00 PDT
> End time: 25 Oct, 2016 18:00 PDT
> Posted on 11 Oct, 2016 16:49 UTC by Mahidhar Tatineni
> We will be performing maintenance on the SDSC Datacenter power infrastructure 
> on Oct 25, 2016. Both Comet and Gordon will be unavailable 6AM-6PM (PT) on 
> Tuesday, Oct 25, 2016. We have reservations in place on both machines so jobs 
> that do not fit in the window before the maintenance will be queued and run 
> after the maintenance is completed. Jobs will not run during the maintenance. 
> Please email h...@xsede.org if you have any questions.
> 
> This message was generated by XSEDE User News v3.0.  You can view this 
> message in the XSEDE User Portal at 
> https://portal.xsede.org/web/xup/user-news/-/news/item/7715.
> You can manage your XSEDE User News subscriptions at 
> https://portal.xsede.org/group/xup/user-news/-/news/manage-subscription.



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

[jira] [Commented] (AIRAVATA-2159) SEAGrid Notice creation error.

2016-10-12 Thread Marcus Christie (JIRA) 

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

Marcus Christie commented on AIRAVATA-2159:
---

I've tried to see if there is any information in the logs, but no luck.  On 
gw75 I can see 3 consecutive attempts by Sudhakar to add a notice, each 
resulting in a 500 response:
{noformat:title=/var/log/httpd/seagrid.requests.log}
...
149.160.206.11 - - [11/Oct/2016:15:45:35 -0400] "POST /add-notice HTTP/1.1" 500 
4390 "https://seagrid.o
rg/admin/dashboard/notices" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; 
rv:49.0) Gecko/20100101 Fire
fox/49.0"
149.160.206.11 - - [11/Oct/2016:15:46:01 -0400] "POST /add-notice HTTP/1.1" 500 
4390 "https://seagrid.o
rg/admin/dashboard/notices" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; 
rv:49.0) Gecko/20100101 Fire
fox/49.0"
146.200.73.77 - - [11/Oct/2016:16:28:14 -0400] "GET / HTTP/1.1" 200 15398 "-" 
"HELLO Crawler"
149.160.206.11 - - [11/Oct/2016:16:29:47 -0400] "POST /add-notice HTTP/1.1" 500 
4390 "https://seagrid.o
rg/admin/dashboard/notices" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; 
rv:49.0) Gecko/20100101 Fire
fox/49.0"
...
{noformat}

> SEAGrid Notice creation error. 
> ---
>
> Key: AIRAVATA-2159
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2159
> Project: Airavata
>  Issue Type: Bug
>Reporter: Sudhakar Pamidighantam
>Assignee: Marcus Christie
>
> When I tried to create a new notice out of the recent XSEDE new from Mahidhar 
> (copied below) I get an error as follows 
> An error has occurred. Please try again later.
> Which repreats if I click on create button again. 
> Not sure if I am doing something. 
> Begin forwarded message:
> From: XSEDE User News 
> Subject: SDSC Comet, Gordon Maintenance: 6AM-6PM (PT), Oct 25, 2016
> Date: October 11, 2016 at 1:14:44 PM EDT
> To: 
> Reply-To: No Reply 
> A new message has been posted to XSEDE User News.
> Categories: Comet (SDSC), Gordon (SDSC)
> Start time: 25 Oct, 2016 06:00 PDT
> End time: 25 Oct, 2016 18:00 PDT
> Posted on 11 Oct, 2016 16:49 UTC by Mahidhar Tatineni
> We will be performing maintenance on the SDSC Datacenter power infrastructure 
> on Oct 25, 2016. Both Comet and Gordon will be unavailable 6AM-6PM (PT) on 
> Tuesday, Oct 25, 2016. We have reservations in place on both machines so jobs 
> that do not fit in the window before the maintenance will be queued and run 
> after the maintenance is completed. Jobs will not run during the maintenance. 
> Please email h...@xsede.org if you have any questions.
> 
> This message was generated by XSEDE User News v3.0.  You can view this 
> message in the XSEDE User Portal at 
> https://portal.xsede.org/web/xup/user-news/-/news/item/7715.
> You can manage your XSEDE User News subscriptions at 
> https://portal.xsede.org/group/xup/user-news/-/news/manage-subscription.



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

[jira] [Commented] (AIRAVATA-2156) UI for credential store token + key generation for portal users to use with their campus logins.

2016-10-12 Thread Marcus Christie (JIRA) 

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

Marcus Christie commented on AIRAVATA-2156:
---

I have a few questions regarding this issue
# How can I query for just a user's SSH keys?  All I see in the API is 
getAllGatewaySSHPubKeys()
# Does the UI need to allow a user to generate password credentials as well?  
I've kind of assumed that only SSH credentials are needed.
# Somewhat related to #1, do we want to not show user generated credentials in 
the admin's Credential Store? Or should the admin be allowed to delete and 
otherwise manage a user's credentials?

> UI for credential store token + key generation for portal users to use with 
> their campus logins.
> 
>
> Key: AIRAVATA-2156
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2156
> Project: Airavata
>  Issue Type: Bug
>  Components: PGA PHP Web Gateway
>Reporter: Marcus Christie
>Assignee: Marcus Christie
>




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