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 super-computing allocation. 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.

       The preliminary design document is located here : GSoC 2016, the design described is a naive interpretation of XRAS (XSEDE Resource Allocation Service) but will be prone to change with multiple iterations improving the design to suit Airavata's goal and purposes.

Phase 1:

Designing Use-Cases:

Link to JIRA sub-task : AIRAVATA-2108 - Getting issue details... STATUS

Types of Users who use Science Gateways:

             1.  User's without Allocation: Usually interested in community Allocation

             2.  Users with Allocation

                           - User's with third party Allocations in third party organizations ex: XSEDE Scholars

                           - User's with exclusive access to resources ex: personal laptop's, server etc.

Allocations:

 Resource & job management for user's with third party Allocations:

      * PI is required to register the third party resource, Gateways is responsible to verify/validate the resource

      * Users in this category are gauranteed allocation by PI until the resources are exhausted

      * The purpose of using the gateway is to manage the Allocations at hand by mapping jobs to resources

      * Gateway is also expected to provide job monitoring.

      * PI can assign sub-ordinate users (Ex: Students, peers etc) to use the third party allocations

      * The Sub-ordinate users will use PI's project ID to schedule jobs

      *  User have an option of using PI's allocation or fallback to community allocation if third party allocations are exhausted.

 Resource & job management for user's with exclusive allocations:

      * Only Job management

      * Resource registration, resource verification is not viable

      * A pointer that user has exclusive resources to run jobs.