[
https://issues.apache.org/jira/browse/AIRAVATA-1893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15203361#comment-15203361
]
Suresh Marru commented on AIRAVATA-1893:
----------------------------------------
[~anujbhan] Since rest of the Airavata uses thrift based API, it will be easier
if your project also uses thrift so it will be easy to integrate with.
For UI's can you rather write them in PHP and plan to integrate into PGA -
https://github.com/apache/airavata-php-gateway you will leverage existing
integration with identity server for authentication and authorization. It will
be seamless for users and admins to have a single user interface. Ofcourse,
since there will be API's multiple interfaces could be developed anyway.
> 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)
