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.

PROC19

From EGIWiki
Revision as of 14:07, 14 October 2014 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


Documentation menu: Home Manuals Procedures Training Other Contact For: VO managers Administrators


Baustelle.png This page is under construction.



Title Integration of 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 integrate 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

Technology Product:

  • 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

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

Dear Operations,

We would like to request for starting procedure of integrating XXX to EGI Production Infrastructure

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)
  • EGI Operations representative
  • User communities representative (interested in deployment of Technology Product)
  • EGI Security team representative
  • UMD representative
1 EGIOps
Within Task Force framework coordinating work forward integration of Technology Product in following fields:
  1. Management - integration with EGI Configuration Database [GOCDB] (http://goc.egi.eu/)
    • creation of service types
  2. Monitoring - integration with EGI Monitoring [SAM]
    • development of monitoring probes
    • integration of probes into SAM release
    • integration of probes with Ava/Rel profile
  3. Accounting - integration with EGI Accounting Infrastructure
    • enabling all the accounting data to be collected in one place for a unified view
  4. Support - integration with EGI Helpdesk [GGUS] (http://ggus.eu)
    • creation of support unit and using it to provide support
  5. Dashboard - integration with EGI Operations Portal (http://operations-portal.egi.eu/)
    • integration of probes into Operations Tests pool
  6. 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
  7. Information System - integration with EGI Information system
  8. Security
  9. UMD (where applicable)
2



Revision History

Version Authors Date Comments