Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "Resource Allocation Process"

From EGIWiki
Jump to navigation Jump to search
Line 1: Line 1:
{{Template:Op menubar}} {{TOC_right}}  
{{Template:Op menubar}} {{TOC_right}}[[Resource Allocation Task Force|<< Resource Allocation Task Force]]  
[[Category:Task_forces]]
 
[[Resource_Allocation_Task_Force| << Resource Allocation Task Force]]


<br>


= Introduction  =
= Introduction  =
Line 30: Line 28:
*allocation based on negotiations  
*allocation based on negotiations  
*for requests that proved to be:  
*for requests that proved to be:  
**at least good in EGI scientific review
**at least good in EGI scientific review  
**has members in NGI X
**has members in NGI X  
**each requests can be supported up to 50%
**each requests can be supported up to 50%


=Process=
= Process =
 
[[Image:Ra egi process.png|600px|Resource allocation process]]


[[Image:Ra_egi_process.png|600px| Resource allocation process]]
== Step 1 Pools definition preparation  ==
== Step 1 ==


*NGI/Sites defines pools and register them in EGI  
*NGI/Sites defines pools and register them in EGI  
*Pools definition may be subject of change according to specific policy
*Pools definition may be subject of change according to specific policy


== Step 2  ==
== Step 2 Request Submission ==
 
VO specifies and submits a resource request
 
== Step 3 Pool matching  ==
 
EGI Operator matches the resources request with currently available pools and decide on actions (may be more that one)
 
== Step 4 Actions ==
 
=== Step 4a  ===
 
In case some pools are matching the request, EGI operator can proceed with allocation according to process specified in the selected pool definition
 
=== Step 4b  ===


VO specifies and submits a resource request
In case the are missing resources EGI Operator can forward the request to scientific review.


== Step 3 ==
After scientific review the request goes to step 3 again (GOTO 3).


EGI Operator matches the resources request with currently available  pools and decide on actions (may be more that one)


==Step 4==
=== Step 4c  ===


=== Step 4a ===
EGI Operator sends back the offer to the VO, in case:
*it covers the request,
*it covers the request partially, but there is no option to improve the situation


In case some pools are matching the request, EGI operator can proceed with allocation according to process specified in the selected pool definition
VO can accept the offer or reject it (or continue the negotiation with modified request – step 2 again (GOTO 2))


=== Step 4b ===
 
=== Step 4c ===
[[Category:Task_forces]]

Revision as of 16:17, 8 March 2013

Main EGI.eu operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security


<< Resource Allocation Task Force


Introduction

Definition
Let a pool be a specific capacity of resources available for EGI allocation according to defined process under defined conditions

Note: Pools covers all scenarios mentioned ever in RATF including “free hand”, “right to revoke”, “negotiation (elastic pool)”

The pool are defined in the Site/NGI declaration

  • previously referred as pre-agreement, but it should not require EGI to agree/negotiate
  • can be subject of change in time (some limitation apply)

Example

Pool-1-SiteA will offer:

  • up to 100 cores in 2013 as reserved pool (as a whole), opportunistic inside pool
  • “free hand” to EGI
  • each VO should not be allocated more than 10% of the pool

Pool-2-SiteB will offer:

  • up to 4000 cores between Jun’13 – Feb’14 with assigned fair-share
  • allocation based on negotiations
  • for requests that proved to be:
    • at least good in EGI scientific review
    • has members in NGI X
    • each requests can be supported up to 50%

Process

Resource allocation process

Step 1 Pools definition preparation

  • NGI/Sites defines pools and register them in EGI
  • Pools definition may be subject of change according to specific policy

Step 2 Request Submission

VO specifies and submits a resource request

Step 3 Pool matching

EGI Operator matches the resources request with currently available pools and decide on actions (may be more that one)

Step 4 Actions

Step 4a

In case some pools are matching the request, EGI operator can proceed with allocation according to process specified in the selected pool definition

Step 4b

In case the are missing resources EGI Operator can forward the request to scientific review.

After scientific review the request goes to step 3 again (GOTO 3).


Step 4c

EGI Operator sends back the offer to the VO, in case:

  • it covers the request,
  • it covers the request partially, but there is no option to improve the situation

VO can accept the offer or reject it (or continue the negotiation with modified request – step 2 again (GOTO 2))