[
https://issues.apache.org/jira/browse/AIRAVATA-3600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eroma updated AIRAVATA-3600:
----------------------------
Summary: Gateway adminportal monitoring module (was: CLONE - SciGaP
adminportal monitoring module)
> Gateway adminportal monitoring module
> -------------------------------------
>
> Key: AIRAVATA-3600
> URL: https://issues.apache.org/jira/browse/AIRAVATA-3600
> 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.
> Another main aspect of the monitoring module would be to have an audit trail.
> Audit trail is required both at parent ScIGaP portal level as well as at
> individual gateway level. The audit is to generate report which states who
> has changed what in gateway Settings level. The audit is required to all
> aspects of Admin Settings and should display who has created, updated or
> deleted records within the gateway.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
