|Main||EGI.eu operations services||Support||Documentation||Tools||Activities||Performance||Technology||Catch-all Services||Resource Allocation||Security|
This page provides information about resource allocation in EGI and instructions on how to contribute resources to the EGI Pool.
Resource allocation QoS levels
For computing resources a Resource Provider can provide different types of access to resources according to its local policies and the user requests:
- Level C1: Opportunistic. Resources are not guaranteed and are subject to local availability.
- Level C2: Time allocation. Resources are available in fair share-like mode for a fixed time period.
- Level C3: Reserved allocation. Resources are exclusively reserved to the VO and the job will be executed immediately after submission.
Resource allocation scenarios
||Usage (guaranteed allocation/opportunistic)
|in free hand
||address requests below a defined threshold||central collector for requests; set up and coordinate the usage of the pool; investigate all the operational aspects; allocate resources; monitor the effectiveness of the pool resources usage
||provide resources directly; act as broker towards the Resource Centers
||no review as long as the pool's resources are enough to satisfy all requests. If a review is needed it is up to EGI.eu only to decide
||guaranteed allocation for a subset of the pool's resources; opportunistic for the rest||After the pool has been set up, EGI collects requests, defines the required operational steps to support the requests; RPs configure their resources that are part of the pool accordingly|
|right to revoke
||address request above the threshold||central collector for requests; set up and coordinate the usage of the pool; investigate all the operational aspects; allocate resources; monitor the effectiveness of the pool resources usage
||provide resources directly; act as broker towards the Resource Centers + option to withdraw if national/local policies are conflicting
||same as above, but if a review is needed a very lightweight procedure should be defined, involving EGI.eu and representatives of the RPs contributing to the pool
||guaranteed allocation for a subset of the pool's resources; opportunistic for the rest|
|negotiated (elastic pools)
||address 'heavy' requests||central collector for requests; broker for the RPs resources; define all the technical aspects of the requests; open calls to RPs in order to set up the pool through the NGIs
||broker for the RCs resources; provide support to RCs in order to ease the creation of a pool; monitor the effectiveness of the pool resources usage by the requester
||not at all; it is up to the different RPs (NGIs and/or RCs) to decide how many resources (if any) they want to provide to that specific request/user community
||the call shall look for resources whose allocation could be guaranteed; in addition opportunistic usage is an added value||for each request EGI investigates all the operational aspects, providing a technical descritption of the request (and recipes if necessary) and sets up a call to RPs (throug NGIs) to provide resources for the temporary (elastic) pool dedicated to that request. Then coordinates the setting up of the pools and informs the requester about the conditions for accessing and using the resources|