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.
Difference between revisions of "PROC23"
(→Steps) |
(→Steps) |
||
| Line 65: | Line 65: | ||
| '''NEW''' | | '''NEW''' | ||
|- | |- | ||
| | | 2b | ||
| Development team<br> | | Development team<br> | ||
| Update ticket with information about results of the testing <br> | | Update ticket with information about results of the overall testing phase<br> | ||
| | | '''Modified''' | ||
|- | |- | ||
| 3<br> | | 3<br> | ||
Revision as of 13:31, 22 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
- Development team: Team responsible for development, release and deployment of the tool
- Operations team:
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 |
Development team |
Once release is ready the team opens a ticket in RT to queue XXXX with following informations
|
Since the Operations team has to be informed about it, shall we open a GGUS ticket to Operations instead?
|
| 2a | Operations Team | Update the ticket with the information on the performed tests and their result | NEW |
| 2b | Development team |
Update ticket with information about results of the overall testing phase |
Modified |
| 3 |
Development team | Provide link to updated documentation |
|
| 4 |
Development team and Operations team |
Agree on deployment date |
|
| 5 |
Operations team |
Inform OMB about upcoming deployment |
|
| 6 |
Development team | Deploy release |
|
| 7 | Operations team | Close RT ticket after a week after deployment only if release was successful |
Revision History
| Version | Authors | Date | Comments |
|---|---|---|---|
| 0.2 | Alessandro Paolini | making some changes... |