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 @

Difference between revisions of "PROC19"

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

=== OPS Dashboard ===
=== Operations (ROD) Dashboard ===

{| class="wikitable"
{| class="wikitable"
Line 238: Line 238:
! Additional temporary comments<br>
! Additional temporary comments<br>
|- valign="top"
| colspan="4" | '''OPS Dashboard'''
|- valign="top"
| 4  
| 4  
| EGI Ops&nbsp;  
| EGI Ops&nbsp;  

Revision as of 13:59, 19 February 2019

Main 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

Title Integration of new cloud management framework and grid middleware in EGI Production Infrastructure
Document link
Last modified
Policy Group Acronym OMB
Policy Group Name Operations Management Board
Contact Group
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 Alessandro Paolini


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.


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 Provider (TP): person representing or leading Technology Provider team
  • EGI Operations (EGIOps)
  • Operations Centre (OC)
  • Resource Centre (RC)
  • Operations Management Board: EGI operations policy board


Before sending a request:

  • OC has to have
    • the support of TP with effort to integrate with EGI Infrastructure (information system, accounting, monitoring etc), provide support via GGUS and maintain software via UMD
    • one or more RC available to deploy the new platform
  • TP has to have
    • effort to integrate with EGI Infrastructure (information system, accounting, monitoring etc), provide support via GGUS and maintain software via UMD
    • the support of one or more OC, with one or more RC available to deploy the new platform and the integration-software developed by the TP


Request submission and validation

The request can be send by:

  1. Operations Centre
  2. EGI Operations
  3. Technology Provider

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 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

Prerequisite data:
* name of Technology Product:
* Technology Provider (person representing or leading the team) contact details(name, email):
* customers of the Product (eg. user community, Operations Centre):
* motivation:

Best Regards
2 EGIOps

Operations contacts the OMB to request the approval of the request.

Functional requirements

Functional requirements for new product to be integrated:

  • support VO concept
  • support X.509 certificates

Integration steps

Integration covers following areas (where possible steps can be done in parallel):

# Responsible Action Additional temporary comments
0a EGIOps When Approved, EGIOps and TP should agree on Underpinning Agreement (UA) agree on Corporate-level Technology Provider Underpinning Agreement or on a customised version
0b EGIOps

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

  • Technology Provider representative
  • 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

# Responsible Action Additional temporary comments



Add new service types agreed within Task Force.

1b Pilot Site Deploy technical service instance and register in GOCDB.

Information System

# Responsible Action Additional temporary comments
2a Technology Provider

Develop software for integration with BDII.

Analyse the use cases for deciding if the new technology has to be published in the BDII or not, and the relevant set of information to publish.

  • Must the new technology be published in the BDII?
    • it has to be created the information providers
  • Is it necessary any modification to the Glue Schema for properly publishing the new technology information?
    • any modification to the Glue Schema has to be discussed with the Glue Working Group
2b Pilot Site Deploy software for integration with BDII and documentation.
2c   EGI Operations
Verify integration Alessandro Paolini, Enol Fernandez, Baptiste Grenier, Operations checks documentation


# Responsible Action Additional temporary comments
3a Technology Provider Develop nagios probe with support from SAM team and documentation. ARGO Guidelines for monitoring probes
3b ARGO, EGI Ops

Check probe, verify results, add to SAM release.

Add test to ROC profile.

PROC06 and PROC07
3c ARGO, EGI Ops Deploy probe in production nagios and documentation. Operations checks documentation

Operations (ROD) Dashboard

# Responsible Action Additional temporary comments
4 EGI Ops  Add test to Operations profile Setting a Nagios test status to OPERATIONS
# Responsible Action Additional temporary comments
5a Technology Provider

Declare Quality of Support for 3rd level Support Unit (SU) and name of SU

FAQ GGUS-New-Support-Unit

5b GGUS   Create Support Unit under "Product Teams" category

6a Technology Provider

Develop software for integration with APEL

Define integration and what data should be published.

  • if the new technology is using computing or storage services for which accounting data are already collected, there is no need of new parser/software for integration with APEL
6b APEL  Validate integration Ops support check documentation
6c EGI Accounting Portal  Display data
7a Technology Provider Ensure software developed for the integration of the new Technology Product satisfies UMD Minimal Requirements

Request the inclusion into UMD

7b EGI Ops (UMD representative) Technology Provider info is added in TechnologyProviders List and UMD Product ID card
7c EGI Software provisioning Team Applies the UMD Software Provisioning process to assess the quality of the new product
7d EGI Ops (UMD representative)
 Once confirmed a successful provisioning (step 11c) includes the new product/products into an UMD release and makes it available to the production infrastricture, in the UMD repositories
VM image Marketplace (Cloud management framework ONLY)
8a Technology Provider Implement subscription to VM image lists from EGI MarketPlace and create documentation.
8b Pilot Site Add service endpoint to GOCDB (type:
8c NGI/EGI Ops Check is passing 
8d EGI Cloud VM Image Management SU Validate integration Ops support check documentation
9a EGI Ops Update relevant documentation

9b Technology Provider Develop documentation for users and admins where missing

9c EGI Ops Validate Documentation
Resource Allocation
Resource Allocation

Add new access method in e-GRANT(if needed)

Define if the middleware is a new way of accessing resources

e-GRANT was dismissed. To evaluate if similar steps are necessary for the AoD service or EGI Marketplace
Technology Provider complete the EGI SVG Software Security Checklist A brief written response to Chair of SVG (Linda.Cornwall <AT> is requested
Security team
Provide recommendations based on provided input

11c Technology Provider Implement recommendations
Security Team Validate implementation of recommendations
12a EGI Ops Announces the availability of new product to OMB and includes the announcement in the monthly EGI Broadcast to communicate the availability of the new product to NGIs, VOs, RCs managers

Revision History

Version Authors Date Comments

A. Paolini 2016-06-03 Trying to define some rules for integrating the new technology with the information and the accounting system
Alessandro Paolini 2016-06-08 "EGI Operations Support" was decommissioned, changed all the references to "Operations"
Alessandro Paolini 2019-01-09 some minor updates; to decide if keeping the step 9 about "Resource Allocation" or discard it.
Alessandro Paolini 2019-02-04 step 10a: added the link to the Software Security Checklist