Difference between revisions of "Resource Allocation Process"
Jump to navigation
Jump to search
(→Step 1) |
|||
Line 5: | Line 5: | ||
=Introduction= | = 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) | |||
=Process= | =Process= |
Revision as of 16:12, 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)
Process
Step 1
- NGI/Sites defines pools and register them in EGI
- Pools definition may be subject of change according to specific policy