[
https://issues.apache.org/jira/browse/AIRAVATA-3315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17170119#comment-17170119
]
ASF subversion and git services commented on AIRAVATA-3315:
-----------------------------------------------------------
Commit 14e6e7599c120d16a12bb4f883d803a4190e544b in airavata's branch
refs/heads/AIRAVATA-3315-storage-quotas from Marcus Christie
[ https://gitbox.apache.org/repos/asf?p=airavata.git;h=14e6e75 ]
Merge branch 'AIRAVATA-3315-storage-quotas' into develop
> Implement Storage Quotas for multiple types of storages
> -------------------------------------------------------
>
> Key: AIRAVATA-3315
> URL: https://issues.apache.org/jira/browse/AIRAVATA-3315
> Project: Airavata
> Issue Type: Epic
> Reporter: Suresh Marru
> Assignee: Vivek Shresta Bandaru
> Priority: Major
> Labels: gsoc2020
>
> Airavata based science gateways store data in gateway storage, typically
> mounted with the portal's hosting server. Each user's data is organized
> within user directories on these storage devices. As storage gets full, it
> often creates an issue in rationing the disks.
> This Epic is to track a new capability to implement user-specific quotas
> within Airavata and track usage. This will involve:
> * Adding a configurable user-specific storage per gateway. This should be
> adding an entry to Gateway Resource Profile -
> [https://github.com/apache/airavata/blob/master/thrift-interface-descriptions/data-models/resource-catalog-models/gateway_resource_profile_model.thrift#L84-L89]
> * Record user-specific usage within Airavata's experiment catalog
> * Add user interfaces to display user-specific quota and current usage.
> * Use Airavata MFT service to fetch current information on users storage to
> cross validate.
>
> Mentors: Sudhakar, Suresh, Dimuthu
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
