Difference between revisions of "PROC19"
Line 40: | Line 40: | ||
*'''[[Operations Management Board|Operations Management Board]]''': EGI operations policy board | *'''[[Operations Management Board|Operations Management Board]]''': EGI operations policy board | ||
= Prerequisites = | = Prerequisites = | ||
Before sending a request: | 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 | *OC has to have | ||
** one or more RC available to deploy the new platform | **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 | ||
* TP has to have | **one or more RC available to deploy the new platform | ||
** effort to integrate with EGI Infrastructure (information system, accounting, monitoring etc), provide support via GGUS and maintain software via UMD | *TP has to have | ||
** 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 | **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 = | = Steps = | ||
Line 96: | Line 97: | ||
|- | |- | ||
| 3 | | 3 | ||
| EGIOps | | EGIOps | ||
| When Approved, EGIOps and TP should sign [https://wiki.egi.eu/wiki/Glossary#Underpinning_Contract Underpinning Agreement (UA)] | | When Approved, EGIOps and TP should sign [https://wiki.egi.eu/wiki/Glossary#Underpinning_Contract Underpinning Agreement (UA)] | ||
|} | |} | ||
Line 105: | Line 106: | ||
Functional requirements for new product to be integrated: | Functional requirements for new product to be integrated: | ||
* support VO concept | *support VO concept | ||
* support X.509 certificates | *support X.509 certificates | ||
== Integration steps == | == Integration steps == | ||
Line 164: | Line 165: | ||
| | | | ||
'''Rules for integration, what data is necessary, where published? ''' | '''Rules for integration, what data is necessary, where published? ''' | ||
'''TBD''' | '''TBD''' | ||
|- valign="top" | |- valign="top" | ||
Line 191: | Line 192: | ||
Check probe, verify results, add to SAM release. | Check probe, verify results, add to SAM release. | ||
Add test to ROC profile .<br> | Add test to ROC profile .<br> | ||
| <br> | | <br> | ||
Line 197: | Line 198: | ||
| 3c | | 3c | ||
| NGI/EGI Ops | | NGI/EGI Ops | ||
| Deploy probe in production nagios and documentation. | | Deploy probe in production nagios and documentation. | ||
| <br> | | <br> | ||
|- valign="top" | |- valign="top" | ||
Line 221: | Line 222: | ||
| colspan="4" | '''Accounting''' | | colspan="4" | '''Accounting''' | ||
|- valign="top" | |- valign="top" | ||
| | | 6a | ||
| Technology Provider | | Technology Provider | ||
| | | | ||
Line 229: | Line 230: | ||
| | | | ||
'''Define integration, what data should be published. May be difficult depending on software''' | '''Define integration, what data should be published. May be difficult depending on software''' | ||
'''TBD''' | '''TBD''' | ||
|- valign="top" | |- valign="top" | ||
| | | 6b | ||
| APEL | | APEL | ||
| Validate integration | | Validate integration | ||
| <br> | | <br> | ||
|- valign="top" | |- valign="top" | ||
| | | 6c | ||
| EGI Accounting Portal | | EGI Accounting Portal | ||
| Display data | | Display data | ||
| <br> | | <br> | ||
|- valign="top" | |- valign="top" | ||
| colspan="4" | '''VM image Marketplace'''<br> | | colspan="4" | '''VM image Marketplace''' (Cloud management framework ONLY)<br> | ||
|- valign="top" | |- valign="top" | ||
| | | 7a | ||
| Technology Provider | | Technology Provider | ||
| Implement subscription to VM image lists from EGI MarketPlace and create documentation. | | Implement subscription to VM image lists from EGI MarketPlace and create documentation. | ||
| <br> | | <br> | ||
|- valign="top" | |- valign="top" | ||
| | | 7b | ||
| Pilot Site | | Pilot Site | ||
| Add service endpoint to GOCDB (type: eu.egi.cloud.vm-metadata.vmcatcher) | | Add service endpoint to GOCDB (type: eu.egi.cloud.vm-metadata.vmcatcher) | ||
| <br> | | <br> | ||
|- valign="top" | |- valign="top" | ||
| | | 7c | ||
| NGI/EGI Ops | | NGI/EGI Ops | ||
| Check eu.egi.cloud.vm-metadata.vmcatcher is passing OK | | Check eu.egi.cloud.vm-metadata.vmcatcher is passing OK | ||
| <br> | | <br> | ||
|- valign="top" | |- valign="top" | ||
| | | 7d | ||
| EGI Cloud VM Image Management SU | | EGI Cloud VM Image Management SU | ||
| Validate integration | | Validate integration | ||
Line 268: | Line 269: | ||
| colspan="4" | '''Documentation''' | | colspan="4" | '''Documentation''' | ||
|- valign="top" | |- valign="top" | ||
| | | 8a | ||
| EGI Ops | | EGI Ops | ||
| Update relevant documentation<br> | | Update relevant documentation<br> | ||
| <br> | | <br> | ||
|- valign="top" | |- valign="top" | ||
| | | 8b | ||
| Technology Provider | | Technology Provider | ||
| Develop documentation for users and admins where missing<br> | | Develop documentation for users and admins where missing<br> | ||
| | | | ||
|- valign="top" | |- valign="top" | ||
| | | 8c | ||
| EGI Ops | | EGI Ops | ||
| Validate Documentation | | Validate Documentation | ||
Line 285: | Line 286: | ||
| colspan="4" | '''Resource Allocation''' | | colspan="4" | '''Resource Allocation''' | ||
|- valign="top" | |- valign="top" | ||
| | | 9a<br> | ||
| Resource Allocation | | Resource Allocation | ||
| | | | ||
Add new access method in e-GRANT(if needed) | Add new access method in e-GRANT(if needed) | ||
Define if the middleware is a new way of accessing resources | Define if the middleware is a new way of accessing resources | ||
Line 294: | Line 295: | ||
| <br> | | <br> | ||
|- valign="top" | |- valign="top" | ||
| | | 9b<br> | ||
| Pilot site<br> | | Pilot site<br> | ||
| Alter the pool or create a new one | | Alter the pool or create a new one | ||
| <br> | | <br> | ||
|- valign="top" | |- valign="top" | ||
| | | 9c<br> | ||
| Resource Allocation | | Resource Allocation | ||
| Validate the new pool | | Validate the new pool | ||
Line 306: | Line 307: | ||
| colspan="4" | '''Security''' | | colspan="4" | '''Security''' | ||
|- valign="top" | |- valign="top" | ||
| | | 10a<br> | ||
| Security Team | | Security Team | ||
| <br> | | <br> | ||
Line 315: | Line 316: | ||
|- valign="top" | |- valign="top" | ||
| | | 10b<br> | ||
| Technology Provider | | Technology Provider | ||
| Implement audit recommendations | | Implement audit recommendations | ||
| <br> | | <br> | ||
|- valign="top" | |- valign="top" | ||
| | | 10c<br> | ||
| Security Team | | Security Team | ||
| Validate implementation of audit recommendations | | Validate implementation of audit recommendations | ||
Line 327: | Line 328: | ||
| colspan="4" | '''UMD''' | | colspan="4" | '''UMD''' | ||
|- valign="top" | |- valign="top" | ||
| | | 11a | ||
| Technology Provider | | Technology Provider | ||
| Ensure software developed for the integration of the new Technology Product satisfies [https://wiki.egi.eu/wiki/UMD_Provisioning#Minimal_requirements UMD Minimal Requirements] | | Ensure software developed for the integration of the new Technology Product satisfies [https://wiki.egi.eu/wiki/UMD_Provisioning#Minimal_requirements UMD Minimal Requirements] | ||
| <br> | | <br> | ||
|- valign="top" | |- valign="top" | ||
| | | 11b | ||
| EGI Ops (UMD representative) | | EGI Ops (UMD representative) | ||
| Technology Provider info is added in [https://wiki.egi.eu/wiki/Technology_Providers TechnologyProviders List] and [https://wiki.egi.eu/wiki/URT:UMD_products_ID_cards UMD Product ID card] | | Technology Provider info is added in [https://wiki.egi.eu/wiki/Technology_Providers TechnologyProviders List] and [https://wiki.egi.eu/wiki/URT:UMD_products_ID_cards UMD Product ID card] | ||
| | | | ||
|- valign="top" | |- valign="top" | ||
| | | 11c | ||
| EGI Software provisioning Team | | EGI Software provisioning Team | ||
| Applies the [https://wiki.egi.eu/wiki/EGI_Software_Provisioning UMD Software Provisioning process] to assess the quality of the new product | | Applies the [https://wiki.egi.eu/wiki/EGI_Software_Provisioning UMD Software Provisioning process] to assess the quality of the new product | ||
| <br> | | <br> | ||
|- valign="top" | |- valign="top" | ||
| | | 11d | ||
| EGI Ops (UMD representative)<br> | | EGI Ops (UMD representative)<br> | ||
| Once confirmed a successful provisioning (step 10c) includes the new product/products into an UMD release and makes it available to the production infrastricture, in the UMD repositories | | Once confirmed a successful provisioning (step 10c) includes the new product/products into an UMD release and makes it available to the production infrastricture, in the UMD repositories | ||
| <br> | | <br> | ||
|- valign="top" | |- valign="top" | ||
| | | 11e | ||
| EGI Ops | | EGI Ops | ||
| Announces the availability of new product to OMB | | Announces the availability of new product to OMB | ||
| <br> | | <br> | ||
|- valign="top" | |- valign="top" | ||
| | | 11f | ||
| EGI Ops Support | | EGI Ops Support | ||
| Includes the announcement in the monthly EGI Broadcast to communicate the availability of the new product to NGIs, VOs, RCs managers | | Includes the announcement in the monthly EGI Broadcast to communicate the availability of the new product to NGIs, VOs, RCs managers | ||
Line 362: | Line 363: | ||
<br> | <br> | ||
<br> | <br> | ||
= Revision History = | = Revision History = |
Revision as of 16:57, 22 January 2015
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 or 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 submission 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) |
Functional requirements
Functional requirements for new product to be integrated:
- support VO concept
- support X.509 certificates
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? TBD |
2b | Pilot Site | Deploy software for integration with BDII and documentation. | |
2c | EGI Ops |
Verify integration | Peter, Enol, Maria (CERN) |
Availability Monitoring | |||
3a | Technology Provider | Develop nagios probe with support from SAM team and documentation. | |
3b | ARGO/SAM EGI Support |
Check probe, verify results, add to SAM release. Add test to ROC profile . |
|
3c | NGI/EGI Ops | Deploy probe in production nagios and documentation. | |
OPS Dashboard | |||
4a | EGI Ops Support | Add test to Operations profile | |
Support | |||
5a | Technology Provider | Declare Quality of Support for Support Unite and name of SU | |
5b | GGUS | Create Support Unite under "Product Teams" category |
|
Accounting | |||
6a | Technology Provider |
Develop software for integration with APEL
|
Define integration, what data should be published. May be difficult depending on software TBD |
6b | APEL | Validate integration | |
6c | EGI Accounting Portal | Display data | |
VM image Marketplace (Cloud management framework ONLY) | |||
7a | Technology Provider | Implement subscription to VM image lists from EGI MarketPlace and create documentation. | |
7b | Pilot Site | Add service endpoint to GOCDB (type: eu.egi.cloud.vm-metadata.vmcatcher) | |
7c | NGI/EGI Ops | Check eu.egi.cloud.vm-metadata.vmcatcher is passing OK | |
7d | EGI Cloud VM Image Management SU | Validate integration | |
Documentation | |||
8a | EGI Ops | Update relevant documentation |
|
8b | Technology Provider | Develop documentation for users and admins where missing |
|
8c | EGI Ops | Validate Documentation | |
Resource Allocation | |||
9a |
Resource Allocation |
Add new access method in e-GRANT(if needed) Define if the middleware is a new way of accessing resources |
|
9b |
Pilot site |
Alter the pool or create a new one | |
9c |
Resource Allocation | Validate the new pool | |
Security | |||
10a |
Security Team |
Security Audit? Need audit rules | |
10b |
Technology Provider | Implement audit recommendations | |
10c |
Security Team | Validate implementation of audit recommendations | |
UMD | |||
11a | Technology Provider | Ensure software developed for the integration of the new Technology Product satisfies UMD Minimal Requirements | |
11b | EGI Ops (UMD representative) | Technology Provider info is added in TechnologyProviders List and UMD Product ID card | |
11c | EGI Software provisioning Team | Applies the UMD Software Provisioning process to assess the quality of the new product | |
11d | EGI Ops (UMD representative) |
Once confirmed a successful provisioning (step 10c) includes the new product/products into an UMD release and makes it available to the production infrastricture, in the UMD repositories | |
11e | EGI Ops | Announces the availability of new product to OMB | |
11f | EGI Ops Support | 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 |
---|---|---|---|