[ 
https://issues.apache.org/jira/browse/AIRAVATA-2108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15512194#comment-15512194
 ] 

Anuj Bhandar commented on AIRAVATA-2108:
----------------------------------------

 h4.*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. 

h4.*Allocations:*

*1*. !Community_Allocations.png!

*2*. !Campus_Allocations.png!

*3. 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.

*4. 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.      

> Use cases to consider
> ---------------------
>
>                 Key: AIRAVATA-2108
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-2108
>             Project: Airavata
>          Issue Type: Sub-task
>          Components: Airavata API
>         Environment: Software platform, Middleware serivice
>            Reporter: Anuj Bhandar
>            Assignee: Anuj Bhandar
>              Labels: Y790
>         Attachments: 20160921_152350.jpg, 20160921_153814.jpg, 
> 20160921_155710.jpg, 20160921_160212.jpg, 20160921_161602.jpg, 
> Campus_Allocations.png, Community_Allocations.png
>
>
> Resource Allocation use-cases:
> 1. Establish an allocations process:  The allocation administrator interacts 
> with Airavata staff to establish an allocations process for a client 
> organization. 
> Note: This may be a extra feature request, because the allocation procNote: 
> This may be a extra feature request, because the allocation process can be 
> same (predefined) to all the clients
> ess can be same (predefined) to all the clients
> 2. Establish and manage review panel: The allocation administrator 
> establishes one or more review panels and designates panelists, their terms, 
> and areas of expertise.
> Note: 
>        *  The level of depth and role privileges are to be thought about and  
>     finalized.
>        *  Parameters such as least number of approvals and number of 
> panelists should be finalized.
> 3.  Add resources: Airavata resource allocation service queries Airavata's 
> resource discovery service to identify resources that services providers have 
> designated to be part of a given allocation process.
> Note: 
>        *  Types of resources: Community and paid (XSEDE)
>        *  Are all the clients entitled to select all kinds of resources ? or 
> is it predefined
> 4. Establish a submission opportunity: The allocation administrator defines 
> and verifies the deadlines, review panel, and resources associated with a 
> submission opportunity. 
>  Note: As some of these use-cases are picked from "XRAS (XSEDE)", I need more 
> elaboration on submission opportunity
> 5. Submission of allocation request: Researchers visit the client 
> organization’s designated interface to submit their allocation requests.
> 6. Manage the review process: The allocation administrator identifies 
> conflicts of interest between reviewers and submissions, assigns and notifies 
> reviewers, and prepares for face-to-face panel meetings.
> Note: This may be an extra feature request.
> 7. Submission of a review: Panel members authenticate to the Airavata's 
> review interface using usernames and authentication, access request 
> documents, related accounting details, and complete assigned reviews.
> 8. Award or reject allocation requests: Following the panel meeting or other 
> decision process, the allocation administrator enters allocation amounts or 
> rejection information, notifies the submitter, and relays results to the
> service provider(s). 
> 9. Allocation data reporting and access: Airavata's will provide interfaces 
> to allow allocation administrators to generate basic reports and exchange 
> data with a reporting service.
> As this a tentative list of use-cases, any suggestion and improvements are 
> gladly welcome.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to