Resource Pool

From EGIWiki
Revision as of 12:06, 12 September 2013 by Tferrari (talk | contribs) (CALL 1. 2013 QR3)
Jump to: navigation, search
Main EGI.eu operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security


In June 2013 the EGI Council approved the implementation of a EGI Resource Allocation Pool to support demands that is scientifically peer reviewed. Resource requests from user communities will be reviewed by a Scientific Review Committee (see the Terms of Reference). This page provides information for partners interested in contributing resources to the EGI federated pool about resource allocation in EGI.

Through this page you can submit your resource offer to contribute to the federated pool.

How can I contribute to the federated EGI resource pool?

CALL 1. 2013 QR3

The call for contributions of resource to the EGI federated resource pool CALL1.2013.QR3 is now open to Resource Providers (NGIs and Resource Centres).

Click here to submit your resource offer to contribute to the EGI Resource Pool (see the pdf version of the on-line offer form) .

DEADLINE for submission: 30 September 2013

Terminology

Computing: QoS levels

For computing resources a Resource Provider can offer different types of access to resources according to its local policies and the user requirements:

Storage: QoS levels

For storage resources a Resource Provider can offer different types of access to resources according to its local policies and the user requirements:

  • Level S1. Opportunistic. Storage space is provided depending on availability of local resources at a time without any guarantees in terms of quota and duration of the allocation.
  • Level S2. Guaranteed. Storage space is reserved.

Resource allocation policies

For the resources offered to the EGI Pool, the Resource Provider can play different roles in the resource brokerage process according to its local requirements.

  • Free hands: the broker, responsible of matching demand and offer, is free to allocate the resources from one RP Pool according to local criteria which aim to optimize usage of available resources and user demand. The Resource Provider delegates the responsibility of accepting a proposed resource allocation to the Broker.
  • Right to revoke: the broker matches demand and offer and defines a resource allocation proposal. The RP Pool Manager is responsible of accepting or rejecting the resource allocation proposal of the Broker (EGI.eu), in case of no reply to a Broker's proposal after a default time, the resource allocation proposal is considered to be accepted.
  • Negotiated: the broker matches demand and offer and defines a resource allocation proposal. The RP Pool Manager is responsible of accepting or rejecting the resource allocation proposal of the Broker (EGI.eu) and to explicitly accept or reject.

The table below illustrates the role of the Broker and of the Resource Provider in the resource allocation process according to the resource allocation policy of choice (one of the options above).

Scenario
Scope
EGI role
NGIs role
Review
Usage (guaranteed allocation/opportunistic)
Actions/steps
Free hands
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 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
Negotiated address 'heavy' requests central collector for requests; broker for the RPs resources; define all the technical aspects of the requests
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
it is up to the different RPs (NGIs and/or RCs) to agree on how many resources (if any) they want to provide to that specific request/user community. A broker's proposal is implemented only if explicitly acknowledged by the Resource Providers
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 description of the request (and recipes if necessary). Then the broker coordinates the setting up of the pools and informs the requester about the conditions for accessing and using the resources


Contact information

For more information about the EGI Pool please contact: operations (at) egi.eu