Difference between revisions of "Resource Allocation Task Force brainstorming page"
Jump to navigation
Jump to search
Pros
Cons
Use cases
Role of Actors
Pros
Cons
Use cases
Role of Actors
(→Models) |
|||
Line 52: | Line 52: | ||
Different models can be applied for different requests: | Different models can be applied for different requests: | ||
* Mature VO vs New VO | * Mature VO vs New VO | ||
* International or regional VO | |||
* „Big” request vs „Small” request | * „Big” request vs „Small” request | ||
or NGIs. | or NGIs. |
Revision as of 17:54, 22 January 2013
Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
The main goals are:
- Attract new users and allocate them some grid resources
- Provide users with a simplified procedure to find grid resources for their needs and by means of a central unique reference point
The high level concept
EGI as a place where EGI customer and EGI provider meet and negotiate resource allocation.
Resource allocation components
Actors
EGI
EGI Provider
- NGIs that can directly decide on resource allocation on a pool of resources on specific sites
- NGIs that can coordinate resources allocation with their sites
- sites that are identified to allocate resources by passing its NGI
EGI Customer
- Regional or international VO
- New or existing VO
Regional VO:
- Should be up to NGIs to help the VO and allocate resources within NGI
- EGI provides single point of contact for resource allocation for Customers
International VO:
- EGI provides
- Single point of contact for resource allocation for their Customers
- Negotiation and signing procedures
- Monitoring
- Reporting
New VOs might require additional support.
Prerequisites
Models
Different models can be applied for different requests:
- Mature VO vs New VO
- International or regional VO
- „Big” request vs „Small” request
or NGIs.
Model 1
Pros
Cons
Use cases
Role of Actors
NGI, EGI and RP
Model 2
Pros
Cons
Use cases
Role of Actors
NGI, EGI and RP
Model 3
Pros
Cons
Use cases
Role of Actors
NGI, EGI and RP
Issues for discussion
- The role of NGI, EGI, RC
- Need for scientific request review
- With whom should be signed SLA? EGI, NGI, RP?
Ideas received
- Freedom to express what is possible for NGIs (law,resources etc.). Not all of them are able to support given VO, even if they want to.
- The SLA should be easy enough to be filled in, which means that many service levels should be made optional, as we do now in the VO ID card.
- The resource allocation process should not only allow to address a resource request with an offer, but also vice versa a site with free resources to advertise it.
- National VOs need to talk to their NGIs, however, the same processes and interfaces used for EGI international users could be adopted for regional ones.
- The internal allocation processes and liaison to individual resource contributors should be made transparent.
- The same processes that are being defined for resource allocation, could be generalized to request services, i.e. to allow new user communities to request services to be provided by NGIs, such as application porting.