[
https://issues.apache.org/jira/browse/AIRAVATA-1893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15203486#comment-15203486
]
Anuj Bhandar commented on AIRAVATA-1893:
----------------------------------------
Yes [~smarru],
That would be a good design choice, I am trying to grasp the design for
airavata-php-gateway, will make changes to my initial draft soon and upload the
document. The document will also focus on detailed architectural design
choices, which will then form a base for further discussion on this project.
> Apache Airavata Allocation Manager
> ----------------------------------
>
> Key: AIRAVATA-1893
> URL: https://issues.apache.org/jira/browse/AIRAVATA-1893
> Project: Airavata
> Issue Type: Epic
> Reporter: Suresh Marru
> Labels: gsoc2016, mentor
> Attachments: GSOC_Proposal V0.1.docx, allocateme-master.zip,
> allocateme-master.zip, allocateme-master.zip, allocateme-master.zip
>
>
> A key missing component in Apache Airavata today is to give science gateway
> administrators the ability to assign and manage allocations to their users to
> make sure that a few users don’t use up the gateway’s entire supercomputing
> allocation. Students who participate in this activity will develop a new
> Apache Airavata component that will include a database backend, middleware,
> and an API for the component.
> The Allocation Manager enables tenant gateways define allocation policies and
> available resources. Users of gateways (typically researchers and educators)
> can request appropriate resources to accomplish their research objectives by
> providing a justification.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
