Difference between revisions of "EGI VO OLA guide"

From EGIWiki
Jump to: navigation, search
(Replaced content with "see https://confluence.egi.eu/display/EGISLM/EGI+VO+OLA+guide")
(Tag: Replaced)
Line 1: Line 1:
{{Template:Op menubar}} {{OLA_SLA_UA_menubar}}{{TOC_right}}
see https://confluence.egi.eu/display/EGISLM/EGI+VO+OLA+guide
= Purpose  =
The purpose of EGI VO Agreements is to create a reliable, trust-based communication channel between the Customer and the providers to agree on the services, their levels and the types of support. The EGI VO Agreements are not legal contracts but, as agreements, they outline the clear intentions to collaborate and support research.
= Benefits  =
== For resource providers<br>  ==
*Direct communication with user communities and clarity on expectations&nbsp;&nbsp;&nbsp;&nbsp; <br>
*Clear responsibilities and rules/policies concerning usage of the resources&nbsp;&nbsp;&nbsp;&nbsp;<br>
*Recognition and greater visibility to role of the provider by requiring an explicit acknowledgment<br>
== For research communities<br>  ==
*Better communication and clarity on expectations <br>
*Increased confidence that services will be delivered <br>
*Easier future planning of research activitie<br>
== For EGI Foundation  ==
*Promoting the EGI service value with funding agencies and policy makers at national and European level&nbsp;&nbsp;&nbsp;&nbsp; <br>
*Being seen as mature partner&nbsp;&nbsp;&nbsp;&nbsp; <br>
*Ensuring a foundation of a control process to what is being delivered in the EGI Federation
= Scope<br>  =
The EGI VO Agreements are covering delivery of IT services from [https://www.egi.eu/services/ EGI Catalogue] <br>
= Process  =
This section provides a high level description for the EGI VO Agreements' process. Through this process EGI Foundation is supporting the Customer's needs and communicating the status.
This process, which starts right after the end of the testing phase, can be described by the following steps:
#Firstly, EGI Foundation contacts the EGI national representatives of the countries that are supporting the Customer to find Providers willing to support its activity.
#*If necessary, other Providers, from other countries, will be contacted direclty or through EGI Council.
#EGI Foundation takes care of negotiating with the resource Providers on behalf of the Customer to define the SLA.
#*The SLA is a document describing the services and the amount of resources offered by EGI to the Customer for a given agreed time period.
#*Information needed for the creation of a SLA document can be found under the "SLA Required information" section.
#EGI Foundation opens a GGUS ticket and asks Operations Team to verify the configuration in the agreed providers.
#At the end of this process, if successful, the Customer will have the guarantee that a certain amount of resources for a given period will be available. This should help the Customer to plan future activity.
#Before the SLA expires, EGI Foundation will contact the Customer to work on renewal if there's still a need.
The whole process is depicted in the following figure:
[[Image:EGI VO SLA OLA process.png|center|EGI VO SLA OLA process.png|1200px]]
Usually, for a scientific use cases, the EGI Foundation is looking for free resources leveraging on the interest of the Providers to support cutting-edge research according to their national roadmap.
Another option is pay for use model. In this case EGI Foundation will facilitate the process by putting together the Customer and the Providers which could satisfy the demand. The agreement and the contract will be signed between the Customer and the Provider.
As defined in [https://documents.egi.eu/public/ShowDocument?docid=31 Resource Center OLA]. No additional responsibilities.
As defined in [https://documents.egi.eu/public/ShowDocument?docid=31 Resource Center OLA].
= Required information to start  =
The Provider should provide following information:
* Provider contact: person (and email address) who will agree on OLA
* Start date:  stat date of service to be delivered
* End date:  end date of service to be delivered
* Resources
** Monthly Availability %: the ability of a service component to fulfill its intended function at a specific time or over a calendar month (default 90%).
** Monthly Reliability %: the ability of a service component to fulfill its intended function at a specific time or over a calendar month, excluding maintenance periods (default 95%).
** Cloud compute: (if any, please fill in the section)
*** Number of Virtual CPU cores:
*** Memory:
*** Scratch/ephemeral storage:
*** Public IP addresses: if yes, required number
*** Payment mode offer:
*** Other technical requirements:
*** Duration:
*** Access type:
** High-Throughput Compute: (if any, please fill in the section)
*** Guaranteed computing time [HEPSPEC-hours]:
*** Opportunistic computing time [HEPSPEC-hours]:
*** Max job duration [hours]:
*** Min local storage [GB] (scratch space per each core used by the job):
*** Min physical memory per core [GB]:
*** Middleware:
*** Other technical requirements:
*** Duration:
*** Access type:
** Online Storage: (if any, please fill in the section)
*** Guaranteed storage capacity [TB]:
*** Opportunistic storage capacity [TB]:
*** Other technical requirements:
*** Duration:
*** Access type:
Possible access types:
* Pledged - Resources are exclusively reserved to the Community and the job will be executed immediately after submission
* Opportunistic - Resources are not exclusively allocated, but subject to local availability
* Time allocation - Resources are available in fair share-like mode for a fixed time period.

Latest revision as of 14:41, 25 August 2020