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
(Deprecate page)
Tag: Replaced
 
(101 intermediate revisions by 6 users not shown)
Line 1: Line 1:
{{Template:Op menubar}} {{Template:Doc_menubar}}{{Template:Under_construction}} {{TOC_right}}
{{Template:Op menubar}} {{Template:Doc_menubar}}
 
[[Category:Deprecated]]
<br>
{| style="border:1px solid black; background-color:lightgrey; color: black; padding:5px; font-size:140%; width: 90%; margin: auto;"
 
| style="padding-right: 15px; padding-left: 15px;" |  
{{Ops_procedures
|[[File:Alert.png]] This page is '''Deprecated'''; the content has been moved to https://confluence.egi.eu/display/EGIPP/PROC19+Integration+of+new+cloud+management+framework+or+middleware+stack+in+the+EGI+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]]
|Version =  
|Policy_acronym = OMB
|Policy_name = Operations Management Board
|Contact_group = operations-support@mailman.egi.eu
|Doc_status = DRAFT
|Approval_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.
}}
 
<br>
 
= 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.
 
<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.
 
= Entities involved in the procedure  =
 
*'''Technology Provider team leader (TPL)''':&nbsp;person representing and leading Technology Providerteam
*'''EGI Operations''' '''(EGIOps)'''
*'''Operations Centre (OC)'''
*'''Resource Centre (RC)'''
*'''[[Operations Management Board|Operations Management Board]]''': EGI operations policy board
 
= Steps  =
 
== Request submition and validation  ==
 
The requested can be send by:  
 
#Operations Centre
#EGI Operations
#Technology Provider team leader
 
Resource Centre can also request integration of new cloud management framework or grid middleware. Such request should be first approved by Operations Centre, it belongs to. In such case OC&nbsp;is responsible to create a ticket on behalf of RC. <br>
 
<br>
 
{| class="wikitable"
|-
! Step
! Action on
! Action
|-
| 1
| 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 (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:
*&nbsp;Technology Provider contact details:
* customers of the Product (eg. user community, Operations Centre)
*&nbsp;motivation:
 
 
Best Regards
XXX
</pre>
|-
| 2
| EGIOps
|
Operations contacts the OMB to request the approval of the request.
 
*at least one site wanting to deploy
*at least one user community (?)
 
|}
|}
== Integration steps  ==
Integration covers following areas:
{| class="wikitable"
|-
! #
! Responsible
! Action
|- valign="top"
| 0
| EGIOps<br>
|
Set up an integration Task force for given Technology Product composed of:
*Technology Provider representative
*Operations tools representative<br>
*NGI representatives (wanting to deploy Technology Product) with Pilot Site
*EGI Operations representative<br>
*User communities representative (interested in deployment of Technology Product)
*EGI&nbsp;Security team representative
*UMD representative
|- valign="top"
| colspan="3" |
'''Configuration Management'''
|- valign="top"
|
1a
|
GOCDB Team
|
Add new service types according to procedure<br>
|- valign="top"
| 1b
| Pilot Site
| Deploy technical service instance and Register service instance in GOCDB.
|- valign="top"
| colspan="3" | '''Information System'''
|- valign="top"
| 2a
| Technology Provider
|
Develop software for integration with BDII.
Rules for integration, what data is necessary, where published?
|- valign="top"
| 2b
| Pilot Site
| Deploy software for integration with BDII.
|- valign="top"
| 2c
| &nbsp;?
| Verify integration
|- valign="top"
| colspan="3" | '''Availability Monitoring'''
|- valign="top"
| 3a
| Technology Provider
| Develop nagios probe
|- valign="top"
| 3b
| SAM team
| Check probe, verify results, add to SAM release. Add test to ROC profile&nbsp;
|- valign="top"
| 3c
| NGI/EGI Ops
| Deploy probe in production nagios
|- valign="top"
| colspan="3" | '''OPS Dashboard'''
|- valign="top"
| 4a
| EGI Ops Support
| Add test to operations profile
|- valign="top"
| colspan="3" | '''Support (parallel)'''
|- valign="top"
| 5a
| GGUS Team
| Decision on the name. Are QoS levels the same for all Product Teams? If not, should be defined. PT to agree on support QoS.
|- valign="top"
| colspan="3" | '''Documentation'''
|- valign="top"
| 6a
| EGI Ops
| Update documentation
|- valign="top"
| 6b
| Technology Provider
| Develop documentation for users and admins
|- valign="top"
| 6c
| EGI Ops
| Validate Documentation
|- valign="top"
| colspan="3" | '''Accounting'''
|- valign="top"
| 7a
| Technology Provider
|
Develop software for integration with APEL
Define integration, what data should be published. May be difficult depending on software
|- valign="top"
| 7b
| APEL Team
| Validate integration
|- valign="top"
| 7c
| EGI Accounting Portal Team
| Display data
|- valign="top"
| colspan="3" | '''Resource Allocation'''
|- valign="top"
| 8a<br>
| RA Team
|
Add new access method in e-GRANT
Define if the middleware is a new way of accessing resources
|- valign="top"
| 8b<br>
| Pilot site<br>
| Alter the pool or create a new one
|- valign="top"
| 8c<br>
| RA Team
| Validate the new pool
|- valign="top"
| colspan="3" | '''Security'''
|- valign="top"
| 9a<br>
| Security Team
|
Security Audit?
Need audit rules
|- valign="top"
| 9b<br>
| Technology Provider
| Implement audit recommendations
|- valign="top"
| 9c<br>
| Security Team
| Validate implementation of audit recommendations
|- valign="top"
| colspan="3" | '''UMD'''
|- valign="top"
| <br>
| <br>
| <br>
|- valign="top"
| <br>
| <br>
| <br>
|}
<br>
*add siging TP&nbsp;UAgremment
<br>
= Revision History  =
{| class="wikitable"
|-
! Version
! Authors
! Date
! Comments
|-
| <br>
| <br>
| <br>
| <br>
|}
[[Category:Operations_Procedures]]

Latest revision as of 16:19, 23 August 2022

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
Alert.png This page is Deprecated; the content has been moved to https://confluence.egi.eu/display/EGIPP/PROC19+Integration+of+new+cloud+management+framework+or+middleware+stack+in+the+EGI+Infrastructure
Retrieved from "https://wiki.egi.eu/w/index.php?title=PROC19&oldid=113879"