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.

Difference between revisions of "PROC19"

From EGIWiki
Jump to navigation Jump to search
Line 4: Line 4:


{{Ops_procedures
{{Ops_procedures
|Doc_title = Integration of new cloud stack and grid middleware in EGI Production Infrastructure
|Doc_title = Integration of new cloud management framework and grid middleware in EGI Production Infrastructure
|Doc_link = [[PROC19|https://wiki.egi.eu/wiki/PROC19]]
|Doc_link = [[PROC19|https://wiki.egi.eu/wiki/PROC19]]
|Version =  
|Version =  
Line 12: Line 12:
|Doc_status = DRAFT
|Doc_status = DRAFT
|Approval_date =  
|Approval_date =  
|Procedure_statement = A procedure for the steps to integrate new cloud stack (Cloud platform) or grid middleware (Grid Platform) in EGI Production Infrastructure.
|Procedure_statement = A procedure for the steps to integrate new cloud management framework (Cloud platform) or grid middleware (Grid Platform) in EGI Production Infrastructure.
}}  
}}  


Line 19: Line 19:
= Overview  =
= 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.  
To assure production quality of EGI Infrastructure every cloud management framework (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  =
= Definitions  =


Types of Technology Products:
Types of Technology Products:  
*'''cloud stack''': software for creating, managing, and deploying infrastructure cloud services.  
 
*'''cloud management framework''': software for creating, managing, and deploying infrastructure cloud services.  
*'''grid middleware''': software which allows the users to execute jobs in grid infrastructure.
*'''grid middleware''': software which allows the users to execute jobs in grid infrastructure.


<br> Please refer to the [[Glossary|EGI Glossary]] for the definitions of the terms used in this procedure.<br>  
<br> Please refer to the [[Glossary|EGI Glossary]] for the definitions of the terms used in this procedure.<br>  


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.
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  =
= Entities involved in the procedure  =
Line 61: Line 62:
| 1  
| 1  
| Applicant<br>  
| Applicant<br>  
| Opens a [https://ggus.eu/ GGUS] ticket to Operations to start the process. <pre>Subject: Request for integration of XXX to EGI Production Infrastructure
| Opens a [https://ggus.eu/ GGUS] ticket to Operations to start the process. <pre>Subject: Request for integration of XXX to EGI Production Infrastructure (PROC19)


Dear Operations,
Dear Operations,


We would like to request for starting procedure of integrating XXX to EGI Production Infrastructure
We would like to request for starting procedure of integrating XXX to EGI Production Infrastructure
https://wiki.egi.eu/wiki/PROC19


Prerequisite data:
Prerequisite data:
Line 71: Line 73:
* customers of the Product (eg. user community, Operations Centre)
* customers of the Product (eg. user community, Operations Centre)
*&nbsp;motivation:
*&nbsp;motivation:


Best Regards
Best Regards
Line 80: Line 83:
| Operations contacts the OMB to request the approval of the request.
| Operations contacts the OMB to request the approval of the request.
|}
|}
== Integration steps  ==
== Integration steps  ==


Line 96: Line 100:


*Operations tools representative<br>  
*Operations tools representative<br>  
*NGI representatives (wanting to deploy Technology Product)<br>
*NGI representatives (wanting to deploy Technology Product) with Pilot Site
*EGI Operations representative<br>  
*EGI Operations representative<br>  
*User communities representative (interested in deployment of Technology Product)  
*User communities representative (interested in deployment of Technology Product)  
Line 103: Line 107:


|- valign="top"
|- valign="top"
| 1
| colspan="3" |  
| EGIOps<br>
'''Configuration Management'''  
| Within Task Force framework coordinating work forward integration of Technology Product in following fields:<br>
#'''Management '''- integration with EGI&nbsp;Configuration Database [GOCDB] ([http://goc.egi.eu/ http://goc.egi.eu/])<br>
#*creation of service types<br>
#'''Monitoring '''- integration with EGI Monitoring [SAM] <br>
#*development of monitoring probes <br>
#*integration of probes into SAM release<br>
#*integration of probes with Ava/Rel profile<br>
#'''Accounting '''- integration with EGI Accounting Infrastructure<br>
#*enabling all the accounting data to be collected in one place for a unified view<br>
#'''Support '''- integration with EGI Helpdesk [GGUS] ([http://ggus.eu http://ggus.eu])<br>
#*creation of support unit and using it to provide support<br>
#'''Dashboard '''- integration with EGI&nbsp;Operations Portal ([http://operations-portal.egi.eu/ http://operations-portal.egi.eu/])
#*integration of probes into Operations Tests pool
#'''Documentation '''- integration with existing operations procedures and related documentation
#*integration with Resource Center OLA
#*integration with Operations Procedures
#*creation of documentation (Manuals, instructions) for Resource Centres and Users
#'''Information System''' - integration with EGI Information system
#'''Security'''
#'''UMD '''(where applicable)


|- valign="top"
|- valign="top"
| 2
| EGIOps<br>
|  
|  
Approve Technolgy Product as production.
1
 
|
GOCDB Team


Broadcast to Resorce Centers and NGI managers that Tecnology Product has been approved and can be deployed in Production Infrastructure.
|
Add new service types according to procedure<br>


|- valign="top"
| 2
| Pilot Site
| Deploy technical service instance and Register service instance in GOCDB.
|- valign="top"
|
|
|
|- valign="top"
|
|
|
|- valign="top"
|
|
|
|- valign="top"
|
|
|
|- valign="top"
|
|
|
|- valign="top"
|
|
|
|- valign="top"
|
|
|
|- valign="top"
|
|
|
|- valign="top"
|
|
|
|}
|}


<br>  
<br>  


<br>
<br>  


= Revision History  =
= Revision History  =
Line 150: Line 176:
|-
|-
| <br>  
| <br>  
|  
| <br>
|  
| <br>
| <br>
| <br>
|}
|}


[[Category:Operations_Procedures]]
[[Category:Operations_Procedures]]

Revision as of 17:18, 27 November 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


Baustelle.png This page is under construction.



Title Integration of new cloud management framework 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 integrate new cloud management framework (Cloud platform) or grid middleware (Grid Platform) in EGI Production Infrastructure.
Owner Owner of procedure



Overview

To assure production quality of EGI Infrastructure every cloud management framework (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

Types of Technology Products:

  • cloud management framework: 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

Request submition and validation

The requested can be send by:

  1. Operations Centre
  2. EGI Operations
  3. Technology Product 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 (PROC19)

Dear Operations,

We would like to request for starting procedure of integrating XXX to EGI Production Infrastructure
https://wiki.egi.eu/wiki/PROC19

Prerequisite data:
* name of Technology Product:
* customers of the Product (eg. user community, Operations Centre)
* motivation:


Best Regards
XXX
2 EGIOps Operations contacts the OMB to request the approval of the request.

Integration steps

Integration covers following areas:

# Responsible Action
0 EGIOps

Set up an integration Task force for given Technology Product composed of:

  • Operations tools representative
  • NGI representatives (wanting to deploy Technology Product) with Pilot Site
  • EGI Operations representative
  • User communities representative (interested in deployment of Technology Product)
  • EGI Security team representative
  • UMD representative

Configuration Management

1

GOCDB Team

Add new service types according to procedure

2 Pilot Site Deploy technical service instance and Register service instance in GOCDB.



Revision History

Version Authors Date Comments