Alert.png 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.

EGI VO OLA guide

From EGIWiki
Revision as of 14:42, 5 January 2017 by Krakow (talk | contribs)
Jump to navigation Jump to search
Main EGI.eu operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security


EGI OLA/SLA/UA framework: EGI OLA SLA framework EGI OLA SLA status Metric Definitions RC performance RP performance EGI services performance




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

  • Direct communication with user communities and clarity on expectations    
  • Clear responsibilities and rules/policies concerning usage of the resources    
  • Recognition and greater visibility to role of the provider by requiring an explicit acknowledgment

For research communities

  • Better communication and clarity on expectations
  • Increased confidence that services will be delivered
  • Easier future planning of research activitie

For EGI Foundation

  • Promoting the EGI service value with funding agencies and policy makers at national and European level    
  • Being seen as mature partner    
  • Ensuring a foundation of a control process to what is being delivered in the EGI Federation

Scope

The EGI VO Agreements are covering delivery of IT services from EGI Catalogue

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:

  1. Firstly, EGI Foundation contacts the EGI national representatives of the countries that are supporting the Customer to find Providers willing to support its activity.
  2. If necessary, other Providers, from other countries, will be contacted direclty or through EGI Council.
  3. EGI Foundation takes care of negotiating with the resource Providers on behalf of the Customer to define the SLA.
  4. 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.
  5. Information needed for the creation of a SLA document can be found under the "SLA Required information" section.
  6. EGI Foundation opens a GGUS ticket and asks Operations Team to verify the configuration in the agreed providers.
  7. 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.
  8. 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:

EGI VO SLA OLA process.png


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
  • Platform description:
    • Short description for Customers
    • Url link
    • License
    • Technology provider
    • Operations provider
    • Technical activities
    • Coordination activities
    • Operation activities
    • Maintenance activities
  • Service Targets

Reporting

Following reports are required for the agreements:

Report title Contents When From To Frequency
Services Performance Report The document provides the overall assessment of service performance (per month) and Service target performance achieved given period. if part of EGI Catalogue EGI provider EGI Foundation Every six months
Platform Service report The document provides usage records (resources used, users) of the provider service during given period if part of EGI Catalogue or
provider runs a service on top of EGI Resources
EGI provider EGI Foundation Yearly and with the Agreement ending
Scientific Publications report The document provides list of scientific publications benefiting from the Service. if provider runs a service on top of EGI Resources EGI provider or EGI supplier EGI Foundation Yearly and with the Agreement ending

All reports shall follow predefined templates.