You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@airavata.apache.org by "Eroma (Jira)" <ji...@apache.org> on 2020/03/26 18:03:00 UTC

[jira] [Updated] (AIRAVATA-3200) SciGaP adminportal monitoring module

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

Eroma updated AIRAVATA-3200:
----------------------------
    Labels: airavata-contribution gsoc2020  (was: airavata-contribution)

> SciGaP adminportal monitoring module
> ------------------------------------
>
>                 Key: AIRAVATA-3200
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-3200
>             Project: Airavata
>          Issue Type: Story
>          Components: Django Portal, PGA PHP Web Gateway, SciGaP Monitoring Module
>    Affects Versions: 0.18
>            Reporter: Eroma
>            Priority: Major
>              Labels: airavata-contribution, gsoc2020
>             Fix For: 0.19
>
>
> SciGaP gateway platform is multi tenanted and serves multiple gateways at the same time. In order to manage some gateway features such as 
> Compute resource creation
> Storage resource creation
> Deploying new gateways 
> The platform has a super gateway portal; https://scigap.org/. This portal has mainly two user groups, gateway providers who create new gateway requests and SciGaP admins(SGRC team). SciGaP admins process the new gateway requests and create compute and storage resources required for the gateways.
> The proposed monitoring module is to serve both SciGaP admins and individual gateway admins to generate report they need for various reporting and planning. This documentation will explain the monitoring requirements of SciGaP admins and gateway admins.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)