Difference between revisions of "PROC23"
Jump to navigation
Jump to search
Line 19: | Line 19: | ||
= Definitions = | = Definitions = | ||
Please refer to the [[Glossary|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 = | = Entities involved in the procedure = |
Revision as of 11:14, 23 March 2016
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 |
Title | Production tools release and deployment process |
Document link | https://wiki.egi.eu/wiki/PROC23 |
Last modified | |
Policy Group Acronym | OMB |
Policy Group Name | Operations Management Board |
Contact Group | operations at mailman.egi.eu |
Document Status | DRAFT |
Approved Date | |
Procedure Statement | The procedure describes the process of release and deployment in EGI production infrastructure for Production tools |
Owner | Owner of procedure |
Overview
The procedure describes the process of release and deployment in EGI production infrastructure for Production tools.It is applicable to all tools mentioned under https://wiki.egi.eu/wiki/Tools
Definitions
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
- Service Provider team: Team responsible for development, release and deployment of the tool
- Operations team: Oversees all the process and may provide further people for testing the tool
- Noc-Managers: they are informed regarding the release of the new tool and may provide further people for testing it
Requirements
The prerequesites are:
- Tool is used by EGI production Infrastructure
- Development team should follow https://wiki.egi.eu/wiki/Instructions_for_Production_Tools_teams#Release_and_deployment_management
Steps
Responsible | Action | Notes | |
---|---|---|---|
1 |
Service Provider team |
Once release is ready the team opens a GGUS ticket to Operations with the following information:
|
|
2 | Operations Team |
| |
3a | Operations Team / Noc-Managers | Update the ticket with the information on the performed tests and their result | |
3b | Service Provider team | Update the ticket with information about results of the overall testing phase |
|
4 |
Service Provider team | Provide in the ticket the link to updated documentation |
|
5 | Service Provider team and Operations team |
Agree on deployment date and update the ticket | |
6 | Operations team | 10 days before the upcoming deployment, inform the Noc-Managers.
Update the ticket |
|
7 | Service Provider team | Schedule a downtime of the service in case it is needed | |
8 | Service Provider team | Deploy release and update the ticket | |
9 | Operations team | Close the GGUS ticket after a week of the deployment only if the release was successful |
Revision History
Version | Authors | Date | Comments |
---|---|---|---|
Alessandro Paolini | 2016-03-22 | procedure revised and made some changes |