PROC19
Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
Documentation menu: | Home • | Manuals • | Procedures • | Training • | Other • | Contact ► | For: | VO managers • | Administrators |
This page is under construction. |
Title | Introducing new cloud stack and grid middleware in EGI Production Infrastructure |
Document link | https://wiki.egi.eu/wiki/PROC19 |
Last modified | |
Policy Group Acronym | OMB |
Policy Group Name | Operations Management Board |
Contact Group | operations-support@mailman.egi.eu |
Document Status | DRAFT |
Approved Date | |
Procedure Statement | A procedure for the steps to introduce new cloud stack (Cloud platform) or grid middleware (Grid Platform) in EGI Production Infrastructure. |
Owner | Owner of procedure |
Overview
To assure production quality of EGI Infrastructure every stack (Cloud platform) or middleware (Grid Platform) supported by Production Resource Centres needs to fulfil certain requirements. The goal of this procedure is to assure EGI Infrastructure compliance.
Definitions
- cloud stack: software for creating, managing, and deploying infrastructure cloud services.
- grid middleware: software which allows the users to execute jobs in grid infrastructure.
Please refer to the EGI Glossary for the definitions of the terms used in this procedure.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
Entities involved in the procedure
- Technology Product team leader (TPL): person representing and leading Technology Product team
- EGI Operations (EGIOps)
- Operations Centre (OC)
- Resource Centre (RC)
- Operations Management Board: EGI operations policy board
Steps
Sending a request
The requested can be send by:
- Operations Centre
- EGI Operations
- Technology Provider team leader
Resource Centre can also request integration of new cloud stack or grid middleware. Such request should be first approved by Operations Centre, it belongs to. In such case OC is responsible to create a ticket on behalf of RC.
Step | Action on | Action |
---|---|---|
1 | Applicant |
Opens a GGUS ticket to Operations to start the process. Subject: Request for integration of XXX to EGI Production Infrastructure Dear Operations, We would like to request for setting XXX test an operations test Prerequisite data: * name of nagios probe: * name of service on which the test runs: * link to documentation page: * motivation (which part of the infrastructure will be improved by making XXX test or description of users' problems which will be avoided in future - provide list of GGUS tickets is possible) Best Regards XXX |
2 | EGIOps | Operations contacts the OMB to request the approval of the request. |
Request Validation
Step | Substep | Action on | Action |
---|---|---|---|
1 | 1 | RC |
As soon as the problem is detected, notify your NGI operations centre by opening a GGUS ticket. Please address the ticket to your Operations Centre support unit, who is responsible of validating the request. In the GGUS ticket you must mention:
|
2 | TPL |
The NGI operations centre validates the request. | |
3 | OC |
If the request is deemed valid, a GGUS ticket is sent to Service Level Management(SLM) Support Unit. The SLM support team will take care of discussing all requests received with the SAM team. | |
4 | SLM SU |
| |
5 |
SLM SU |
| |
6 | SLM SU | Close the parent ticket. |
Integration steps
Integration covers following areas:
- Management - integration with Grid Configuration Database [GOCDB] (http://goc.egi.eu/)
- e.g. creation of a service type
- e.g. creation of a service type
- Monitoring - integration with Service Availability Monitoring [SAM]
- development of monitoring probes
- integration of probes into SAM release
- integration of probes with Ava/Rel profile
- development of monitoring probes
- Accounting - integration with EGI Accounting Infrastructure
- enabling all the accounting data to be collected in one place for a unified view
- enabling all the accounting data to be collected in one place for a unified view
- Support - integration with EGI Helpdesk [GGUS] (http://ggus.eu)
- creation of support unit and using it to provide support
- creation of support unit and using it to provide support
- Dashboard - integration with Operations Portal (http://operations-portal.egi.eu/)
- integration of probes into Operations Tests pool
- Documentation - integration with existing operations procedures
- integration with Resource Center OLA
- integration with Resource Center registration and certyfication procedure
- creation of how to manually test the middleware
- Information System - integration with EGI Information system
# | Responsible | Action |
---|---|---|
0 | RC |
Contact your Resource Infrastructure Operations Manager (contact information is available at EGI web site).
|
1 | RP |
Accept or reject registration request and communicate this result back to applicant.
|
2 | OC |
Include the Operations Centre ROD, CSIRT, or help-desk teams in the step if necessary. |
3 | OC |
|
4 | RC |
|
5 | OC |
Check GOC DB that the Resource Centre's information is correct.
|
6 | OC |
Any other Operations Centre-specific requirements (e.g. join a certain VO and/or mailing list, etc.) |
7 | OC |
If all previous actions have been completed with success, notify the Resource Centre Operations Manager that the Registration is completed, and contact the Resource Infrastructure Operations Manager to notify that a new candidate Resource Centre exists and is ready to be certified. |
After the successful completion of all these steps, the registration phase is completed and the Resource Centre is ready for the start of the certification phase.
Revision History
Version | Authors | Date | Comments |
---|---|---|---|