Difference between revisions of "PROC19"
Line 1: | Line 1: | ||
{{Template:Op menubar}} {{Template:Doc_menubar}} {{TOC_right}} | {{Template:Op menubar}} {{Template:Doc_menubar}}{{Template:Under_construction}} {{TOC_right}} | ||
{{Ops_procedures | {{Ops_procedures |
Revision as of 11:29, 21 August 2014
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 | |
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 |
Under construction
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 that EGI Infrastructure is fully supported by operations tools.
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
Prerequisites and responsibilities
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.
Resource Centre certification
Requirements
- The Resource Centre Certification procedure is only applicable for both Resource Centres in "Candidate" or "Suspended" status state in GOC DB.
- A Resource Centre can successfully pass certification only if the conditions required by the Resource Centre OLA are met.
Steps
The following is a detailed description of the steps required for the transition from the "Candidate"/"Suspended" to the "Certified" state of the Resource Centre.
- Actions tagged RC are the responsibility of the Resource Centre Operations Manager.
- Actions tagged RP are the responsibility of the Resource Infrastructure Operations Manager.
- Actions tagged OC are the responsibility of the Operations Centre
- Actions tagged CSIRT are the responsibility of the Computer Security Incident Response Team
# | Responsible | Action |
---|---|---|
0 | RP |
The Resource Infrastructure Operations Manager contacts the Resource Centre Operations Manager to request the subscription of the Resource Centre OLA. |
1 | RC |
The Resource Centre Operations Manager notifies the Resource Infrastructure Operations Manager that the Resource Centre OLA is accepted (if the Resource Centre is has not already endorsed it before for example in case of a suspended Resource Centre), and the Resource Centre is ready to start certification. |
2 | RP |
The Resource Infrastructure Operations Manager contacts the Operations Centre asking to start the certification process. |
Revision History
Version | Authors | Date | Comments |
---|---|---|---|