PROC19
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 | 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 Provider (TP): person representing and leading Technology Provider team
- EGI Operations (EGIOps)
- Operations Centre (OC)
- Resource Centre (RC)
- Operations Management Board: EGI operations policy board
Prerequisites
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
Steps
Request submition and validation
The request can be send by:
- Operations Centre
- EGI Operations
- 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 https://wiki.egi.eu/wiki/PROC19 Prerequisite data: * name of Technology Product: * Technology Provider contact details: * 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. |
3 | EGIOps | When Approved, EGIOps and TP should sign Underpinning Agreement (UA) |
Integration steps
Integration covers following areas:
# | Responsible | Action | |
---|---|---|---|
0 | EGIOps |
Set up an integration Task force for given Technology Product composed of:
|
|
Configuration Management | |||
1a |
GOCDB |
Add new service types agreed within Task Force. |
|
1b | Pilot Site | Deploy technical service instance and register in GOCDB. | |
Information System | |||
2a | Technology Provider |
Develop software for integration with BDII.
|
Rules for integration, what data is necessary, where published? |
2b | Pilot Site | Deploy software for integration with BDII. | |
2c | |
Verify integration | Verify integration who? |
Availability Monitoring | |||
3a | Technology Provider | Develop nagios probe with support from SAM team |
|
3b | SAM |
Check probe, verify results, add to SAM release. Add test to ROC profile |
|
3c | NGI/EGI Ops | Deploy probe in production nagios | |
OPS Dashboard | |||
4a | EGI Ops Support | Add test to Operations profile | |
Support | |||
5a | Technology Provider | Declare Quality of Support for Support Unite | |
5b | GGUS | Create Support Unite under "Product Teams" category |
|
Documentation | |||
6a | EGI Ops | Update relevant documentation |
|
6b | Technology Provider | Develop documentation for users and admins | |
6c | EGI Ops | Validate Documentation | |
Accounting | |||
7a | Technology Provider |
Develop software for integration with APEL
|
Define integration, what data should be published. May be difficult depending on software |
7b | APEL | Validate integration | |
7c | EGI Accounting Portal | Display data | |
Resource Allocation | |||
8a |
Resource Allocation |
Add new access method in e-GRANT Define if the middleware is a new way of accessing resources |
|
8b |
Pilot site |
Alter the pool or create a new one | |
8c |
Resource Allocation | Validate the new pool | |
Security | |||
9a |
Security Team |
Security Audit? Need audit rules | |
9b |
Technology Provider | Implement audit recommendations | |
9c |
Security Team | Validate implementation of audit recommendations | |
UMD | |||
Revision History
Version | Authors | Date | Comments |
---|---|---|---|