[jira] [Created] (AIRAVATA-2652) Remove registry-core dependency on orchestrator and gfac modules

2018-01-24 Thread Sachin Kariyattin (JIRA)
Sachin Kariyattin created AIRAVATA-2652:
---

 Summary: Remove registry-core dependency on orchestrator and gfac 
modules
 Key: AIRAVATA-2652
 URL: https://issues.apache.org/jira/browse/AIRAVATA-2652
 Project: Airavata
  Issue Type: Improvement
  Components: Airavata Orchestrator, GFac, Registry API
Reporter: Sachin Kariyattin
Assignee: Sachin Kariyattin
 Fix For: 0.18


Refactor orchestrator and gfac modules to use registry-api instead of the 
existing registry-core dependency
 * Some of the Experiment Catalog methods used by the orchestrator and gfac are 
not present in the RegistryServerHandler. 
ex: _experimentCatalog.add(ExpCatChildDataType.EXPERIMENT_ERROR, details, 
experimentId);_
Some new methods related to experiment (ERROR, TASK, PROCESS etc) need to be 
created in the RegistryServerHandler.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (AIRAVATA-2651) Add method to get all accessible applications for a user

2018-01-24 Thread Sneha Tilak (JIRA)
Sneha Tilak created AIRAVATA-2651:
-

 Summary: Add method to get all accessible applications for a user
 Key: AIRAVATA-2651
 URL: https://issues.apache.org/jira/browse/AIRAVATA-2651
 Project: Airavata
  Issue Type: Bug
  Components: Airavata API
Reporter: Sneha Tilak
Assignee: Sneha Tilak






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (AIRAVATA-2650) Use ThriftClientPool in Profile Service

2018-01-24 Thread Marcus Christie (JIRA)
Marcus Christie created AIRAVATA-2650:
-

 Summary: Use ThriftClientPool in Profile Service
 Key: AIRAVATA-2650
 URL: https://issues.apache.org/jira/browse/AIRAVATA-2650
 Project: Airavata
  Issue Type: Bug
Reporter: Marcus Christie


We should use client pools and make sure clients are checked back into pool at 
the end of requests.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (AIRAVATA-2627) Letsencrypt auto renewal is preventing Apache from restarting

2018-01-24 Thread Marcus Christie (JIRA)

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

Marcus Christie commented on AIRAVATA-2627:
---

Ran these commands on pgadev.scigap.org as well.

> Letsencrypt auto renewal is preventing Apache from restarting
> -
>
> Key: AIRAVATA-2627
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2627
> Project: Airavata
>  Issue Type: Bug
>  Components: PGA PHP Web Gateway
>Reporter: Marcus Christie
>Assignee: Marcus Christie
>Priority: Major
>
> The {{certbot renew --quiet}} command in the crontab is apparently causing 
> Apache to fail to reload:
> From the systemd journal ({{journalctl -xe}}):
> {noformat}
> -- Unit session-34124.scope has begun starting up.
> Jan 09 12:50:01 gridfarm004.ucs.indiana.edu CROND[11610]: (root) CMD 
> (/usr/lib64/sa/sa1 1 1)
> Jan 09 12:52:01 gridfarm004.ucs.indiana.edu systemd[1]: Started Session 34125 
> of user root.
> -- Subject: Unit session-34125.scope has finished start-up
> -- Defined-By: systemd
> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
> -- 
> -- Unit session-34125.scope has finished starting up.
> -- 
> -- The start-up result is done.
> Jan 09 12:52:01 gridfarm004.ucs.indiana.edu systemd[1]: Starting Session 
> 34125 of user root.
> -- Subject: Unit session-34125.scope has begun start-up
> -- Defined-By: systemd
> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
> -- 
> -- Unit session-34125.scope has begun starting up.
> Jan 09 12:52:01 gridfarm004.ucs.indiana.edu CROND[11692]: (root) CMD 
> (/usr/bin/certbot renew --quiet)
> Jan 09 12:52:03 gridfarm004.ucs.indiana.edu httpd[11725]: AH00112: Warning: 
> DocumentRoot [/www/default] does not exist
> Jan 09 12:52:03 gridfarm004.ucs.indiana.edu httpd[11725]: AH00526: Syntax 
> error on line 10 of /etc/httpd/conf.d/le_tls_sni_01_cert_challenge.conf:
> Jan 09 12:52:03 gridfarm004.ucs.indiana.edu httpd[11725]: SSLCertificateFile: 
> file '/var/lib/letsencrypt/YDnHNU3oKDOaT_oO2qXSoXR65gUb7k66KB0dF4nwT-8.crt' 
> does not exist or is empty
> Jan 09 12:52:03 gridfarm004.ucs.indiana.edu systemd[1]: httpd.service: 
> control process exited, code=exited status=1
> Jan 09 12:52:03 gridfarm004.ucs.indiana.edu systemd[1]: Reload failed for The 
> Apache HTTP Server.
> -- Subject: Unit httpd.service has finished reloading its configuration
> -- Defined-By: systemd
> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
> -- 
> -- Unit httpd.service has finished reloading its configuration
> -- 
> -- The result is failed.
> Jan 09 12:52:03 gridfarm004.ucs.indiana.edu httpd[11735]: AH00112: Warning: 
> DocumentRoot [/www/default] does not exist
> Jan 09 12:52:03 gridfarm004.ucs.indiana.edu systemd[1]: Reloaded The Apache 
> HTTP Server.
> -- Subject: Unit httpd.service has finished reloading its configuration
> -- Defined-By: systemd
> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
> -- 
> -- Unit httpd.service has finished reloading its configuration
> -- 
> -- The result is done.
> Jan 09 12:52:05 gridfarm004.ucs.indiana.edu httpd[11757]: AH00112: Warning: 
> DocumentRoot [/www/default] does not exist
> Jan 09 12:52:05 gridfarm004.ucs.indiana.edu httpd[11757]: AH00526: Syntax 
> error on line 10 of /etc/httpd/conf.d/le_tls_sni_01_cert_challenge.conf:
> Jan 09 12:52:05 gridfarm004.ucs.indiana.edu httpd[11757]: SSLCertificateFile: 
> file '/var/lib/letsencrypt/9qLZfLerTerU_bGLYPfXWXq-EXktXgYfNQAEQcdHSpE.crt' 
> does not exist or is empty
> Jan 09 12:52:05 gridfarm004.ucs.indiana.edu systemd[1]: httpd.service: 
> control process exited, code=exited status=1
> Jan 09 12:52:05 gridfarm004.ucs.indiana.edu systemd[1]: Reload failed for The 
> Apache HTTP Server.
> -- Subject: Unit httpd.service has finished reloading its configuration
> -- Defined-By: systemd
> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
> -- 
> -- Unit httpd.service has finished reloading its configuration
> -- 
> -- The result is failed.
> Jan 09 12:52:05 gridfarm004.ucs.indiana.edu httpd[11767]: AH00112: Warning: 
> DocumentRoot [/www/default] does not exist
> Jan 09 12:52:05 gridfarm004.ucs.indiana.edu systemd[1]: Reloaded The Apache 
> HTTP Server.
> -- Subject: Unit httpd.service has finished reloading its configuration
> -- Defined-By: systemd
> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
> -- 
> -- Unit httpd.service has finished reloading its configuration
> -- 
> -- The result is done.
> Jan 09 12:52:07 gridfarm004.ucs.indiana.edu httpd[11796]: AH00112: Warning: 
> DocumentRoot [/www/default] does not exist
> Jan 09 12:52:07 gridfarm004.ucs.indiana.edu httpd[11796]: AH00526: Syntax 
> error on line 10 of 

[jira] [Commented] (AIRAVATA-2625) Derive and present Text outputs in Experiment summary

2018-01-24 Thread Dimuthu Upeksha (JIRA)

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

Dimuthu Upeksha commented on AIRAVATA-2625:
---

This is might require few changes to output data staging task and there are few 
restrictions. Because we need to read the file to extract the values, we need 
to read the file content to the JVM heap. Risk of that is, if we read a large 
file (several gigs) into the heap, it will cause OOM error and eventually the 
whole JVM might crash. So we have to come up with a reasonable size cap for the 
files that are scanned (2 - 5 MB?) and if the file is larger than that, we 
simply ignore the file and notify the user that output file is too big to scan.

> Derive and present Text outputs in Experiment summary
> -
>
> Key: AIRAVATA-2625
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2625
> Project: Airavata
>  Issue Type: Bug
>  Components: Airavata System
>Affects Versions: 0.18
>Reporter: Eroma
>Assignee: Suresh Marru
>Priority: Major
>
> Currently the available application outputs are in the form of stdout, stderr 
> and URI (files). Going forward to have text (String, Integer, Float) outputs 
> directly in the experiment summary.
> These text outputs to be displayed as key+value pairs and when defining 
> should be defined a file to derive from, e.g. stdout
> At a given time from a single file one or many of these key+value pairs could 
> be derived. Also gateway admin can define multiple files to derive multiple 
> of these values.
> These would be displayed to user in experiment summary and in detailed 
> experiment summary in admin dashboard experiment statistics.
> These should also be displayed to any other gateway user it is shared with. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (AIRAVATA-2615) Experiment view page

2018-01-24 Thread Marcus Christie (JIRA)

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

Marcus Christie updated AIRAVATA-2615:
--
Description: 
TODO
 * (/) Load the Experiment model data together with the Project data, input and 
output DataProducts, ApplicationModule and ComputeResourceDescription (what I'm 
calling a FullExperiment)
 * If the experiment isn't completed or failed, poll the experiment

  was:
TODO

* Load the Experiment model data together with the Project data, input and 
output DataProducts, ApplicationModule and ComputeResourceDescription (what I'm 
calling a FullExperiment)


> Experiment view page
> 
>
> Key: AIRAVATA-2615
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2615
> Project: Airavata
>  Issue Type: Sub-task
>Reporter: Marcus Christie
>Assignee: Marcus Christie
>Priority: Major
>
> TODO
>  * (/) Load the Experiment model data together with the Project data, input 
> and output DataProducts, ApplicationModule and ComputeResourceDescription 
> (what I'm calling a FullExperiment)
>  * If the experiment isn't completed or failed, poll the experiment



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (AIRAVATA-2615) Experiment view page

2018-01-24 Thread Marcus Christie (JIRA)

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

Marcus Christie updated AIRAVATA-2615:
--
Description: 
TODO

* Load the Experiment model data together with the Project data, input and 
output DataProducts, ApplicationModule and ComputeResourceDescription (what I'm 
calling a FullExperiment)

> Experiment view page
> 
>
> Key: AIRAVATA-2615
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2615
> Project: Airavata
>  Issue Type: Sub-task
>Reporter: Marcus Christie
>Assignee: Marcus Christie
>Priority: Major
>
> TODO
> * Load the Experiment model data together with the Project data, input and 
> output DataProducts, ApplicationModule and ComputeResourceDescription (what 
> I'm calling a FullExperiment)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (AIRAVATA-2386) Fix issues with email monitoring

2018-01-24 Thread Eroma (JIRA)

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

Eroma reassigned AIRAVATA-2386:
---

Assignee: Dimuthu Upeksha

> Fix issues with email monitoring
> 
>
> Key: AIRAVATA-2386
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2386
> Project: Airavata
>  Issue Type: Task
>  Components: Airavata System, GFac
>Affects Versions: 0.17
>Reporter: Eroma
>Assignee: Dimuthu Upeksha
>Priority: Major
> Fix For: 0.18
>
> Attachments: jobstatus.ps
>
>
> There are few issues with email monitoring and the task is to collect them 
> and fix.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)