The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.
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
| 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 processes
Actors
Prerequisites
Models
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
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.