EGI-InSPIRE RI EGI-InSPIRE EGI-InSPIRE RI Resource allocation brainstorming space

EGI-InSPIRE RI RA brainstorming space – Task_Force_brainstorming_pagehttps://wiki.egi.eu/wiki/Resource_Allocation_ Task_Force_brainstorming_page –Proc, cons, use cases for models –Ideas –Requirements

EGI-InSPIRE RI Rename: EGI Provieder → Provider EGI Customer → Customer

EGI-InSPIRE RI Model 1 Open market Pros EGI knows what is going on in the infrastructure There are clear rules for resource allocation In case of agreement violation/negotiations EGI is a referee Providers knows what are the Customers' current needs Customer knows which resources are now available Cons For Provider - negotiation process may not be able to be adapted to its needs Strong need for a body to match needs to resources Use cases Standard resources' requests Scientific request review EGI decides if the review is needed. If yes then should be done before request is published to the open market.

EGI-InSPIRE RI Model 2 Boker Pros Best option for Customer: it gets single point of contact and support from one entity Cons EGI has to get and manage the knowledge what is available in the infrastructure (each site) Time consuming for EGI Some Providers want to talk with Customers directly EGI may not be able to match needs to resources. Use cases big international Customers specialized Customer requests new international Customers Scientific request review EGI decide is the review is needed. If yes then should be done before request is published to the open market.

EGI-InSPIRE RI Model 2 Boker Activities EGI: –collect resource demand from customers and related requirements –call for resource offer to create a resource pool –establish a resource pool in collaboration with the RPs –monitoring –accounting collect and provide information about resource usage –periodic assessment of usage –reporting –periodic assessment of acknowledgement of resource usage by VOs

EGI-InSPIRE RI Model 3 Freedom of choice Pros Each Provider may want to apply own procedures - pros for Provider Cons Some Providers may want to apply own procedures - cons for Customer Customer has to negotiate with each of the Providers separately We can end up with lots of different SLA and negotiation procedures Use cases Regional Customer Scientific request review It is up to Provider if it is needed

EGI-InSPIRE RI Issues for discussion 1.SLA –who should be the party of the contract –what should be included in SLA 2.The roles of NGI, EGI, RC in the process 3.Scientific request review 4.The acknowledgement for resources use 5.Monitoring of usage 6.Provider selection 7.Reporting and evaluation 8.Customer support 9.Reservations/resource pool assurance/guaranteed usage 10.Meeting specific needs of the VO in terms of OS, configuration, software etc.

EGI-InSPIRE RI Requirements received List of requirements collected from meetings, mailing list etc. #Requirements_received