[jira] [Updated] (AIRAVATA-2999) [GSoC] Administration Dashboard for Airavata Services

2019-03-21 Thread Suresh Marru (JIRA)


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

Suresh Marru updated AIRAVATA-2999:
---
Labels: gsoc2019  (was: )

> [GSoC] Administration Dashboard for Airavata Services
> -
>
> Key: AIRAVATA-2999
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2999
> Project: Airavata
>  Issue Type: New Feature
>Reporter: Dimuthu Upeksha
>Priority: Major
>  Labels: gsoc2019
>
> Typical Apache Airavata deployment consists of multiple microservices (API 
> Server, Participant, Controller, Pre Workflow Manager, Post Workflow Manager, 
> Job Monitors and etc) and several other services (Database, Kafka, RabbitMQ, 
> Keycloak, Zookeeper, Apache Helix). As it is a deployment with multiple 
> components, when it comes to an issue,  it is time consuming to find which 
> component is having the problem. So we need an Administration Dashboard which 
> can visualize the system health and provide some handle to administrators to 
> control those services like stopping or restarting each component through the 
> dashboard.
> Additionally, this dashboard should be able to authenticate users through 
> Keycloak which is the identity provider for Airavata and  only system 
> administrators should be given access to those operations.



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


[jira] [Updated] (AIRAVATA-2999) [GSoC] Administration Dashboard for Airavata Services

2019-03-21 Thread Dimuthu Upeksha (JIRA)


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

Dimuthu Upeksha updated AIRAVATA-2999:
--
Description: 
Typical Apache Airavata deployment consists of multiple microservices (API 
Server, Participant, Controller, Pre Workflow Manager, Post Workflow Manager, 
Job Monitors and etc) and several other services (Database, Kafka, RabbitMQ, 
Keycloak, Zookeeper, Apache Helix). As it is a deployment with multiple 
components, when it comes to an issue,  it is time consuming to find which 
component is having the problem. So we need an Administration Dashboard which 
can visualize the system health and provide some handle to administrators to 
control those services like stopping or restarting each component through the 
dashboard.

Additionally, this dashboard should be able to authenticate users through 
Keycloak which is the identity provider for Airavata and  only system 
administrators should be given access to those operations.

  was:
Typical Apache Airavata deployment consists of multiple microservices (API 
Server, Participant, Controller, Pre Workflow Manager, Post Workflow Manager, 
Job Monitors and etc) and several other services (Database, Kafka, RabbitMQ, 
Keycloak, Zookeeper, Apache Helix). As it is a deployment with multiple 
components, when it comes to an issue,  it is time consuming to find which 
component is having the problem. So we need an Administration Dashboard which 
can visualize the system health and provide some handle to Administrators to 
control those services like stopping or restarting each component through the 
dashboard.

Additionally, this dashboard should be able to Authenticate users through 
Keycloak which is the identity provider for Airavata and  only system 
administrators should be given access to those operations.

Summary: [GSoC] Administration Dashboard for Airavata Services  (was: 
[GSoC] Administration ashboard for Airavata Services)

> [GSoC] Administration Dashboard for Airavata Services
> -
>
> Key: AIRAVATA-2999
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2999
> Project: Airavata
>  Issue Type: New Feature
>Reporter: Dimuthu Upeksha
>Priority: Major
>
> Typical Apache Airavata deployment consists of multiple microservices (API 
> Server, Participant, Controller, Pre Workflow Manager, Post Workflow Manager, 
> Job Monitors and etc) and several other services (Database, Kafka, RabbitMQ, 
> Keycloak, Zookeeper, Apache Helix). As it is a deployment with multiple 
> components, when it comes to an issue,  it is time consuming to find which 
> component is having the problem. So we need an Administration Dashboard which 
> can visualize the system health and provide some handle to administrators to 
> control those services like stopping or restarting each component through the 
> dashboard.
> Additionally, this dashboard should be able to authenticate users through 
> Keycloak which is the identity provider for Airavata and  only system 
> administrators should be given access to those operations.



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