Difference between revisions of "Pool concept: example"

From EGIWiki
Jump to: navigation, search
(Created page with "=== Pool concept: example === <u>Pool-1 SiteA will offer:</u> *up to 100 cores in 2013 as reserved pool (as a whole -> reservation applies to the whole pool not given usag...")
 
 
Line 1: Line 1:
 +
{{Template:Op menubar}} {{TOC_right}}[[Resource Allocation Task Force|&lt;&lt; Resource Allocation Task Force]]
 +
<br>
 
=== Pool concept: example  ===
 
=== Pool concept: example  ===
  
Line 17: Line 19:
 
**each requests can be supported up to 50%<br>  
 
**each requests can be supported up to 50%<br>  
 
*can be suitable for big resource requests<br>
 
*can be suitable for big resource requests<br>
 +
<br>
 +
 +
[[Category:Task_forces]]

Latest revision as of 23:28, 7 April 2013

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


<< Resource Allocation Task Force

Pool concept: example

Pool-1 SiteA will offer:

  • up to 100 cores in 2013 as reserved pool (as a whole -> reservation applies to the whole pool not given usage), opportunistic inside pool
  • “free hand” to EGI - EGI has free choice to allocate resources 
  • each VO should not be allocated more than 10% of the pool
  • can be suitable for small resource requests

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%
  • can be suitable for big resource requests