|
|
| (79 intermediate revisions by 7 users not shown) |
| Line 1: |
Line 1: |
| {{Template:Op menubar}} {{Template:Doc_menubar}} {{TOC_right}} | | {{Template:Op menubar}} {{Template:Doc_menubar}} |
|
| |
|
| {{Ops_procedures | | {{DeprecatedAndMovedTo|new_location=https://confluence.egi.eu/display/EGIPP/CHM1+Manage+changes+including+emergency+changes https://confluence.egi.eu/display/EGIPP/RDM2+Regular+release+process https://confluence.egi.eu/display/EGIPP/RDM3+Lightweight+release+process}} |
| |Doc_title = Production tools release and deployment process | |
| |Doc_link = https://wiki.egi.eu/wiki/PROC23
| |
| |Version =
| |
| |Policy_acronym = OMB
| |
| |Policy_name = Operations Management Board
| |
| |Contact_group = operations at mailman.egi.eu
| |
| |Doc_status = DRAFT
| |
| |Approval_date =
| |
| |Procedure_statement = The procedure describes the process of release and deployment in EGI production infrastructure for Production tools
| |
| }}
| |
| | |
| = 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 https://wiki.egi.eu/wiki/Tools ]<br>
| |
| | |
| = 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 =
| |
| | |
| *'''Development team''': Team responsible for development, release and deployment of the tool <br>
| |
| *'''XX''''''X''':
| |
| | |
| = Requirements =
| |
| | |
| The prerequesites are:
| |
| | |
| *Tool is used by EGI production Infrastructure<br>
| |
| | |
| = Steps =
| |
| | |
| {| width="906" height="305" class="wikitable"
| |
| |-
| |
| ! <br>
| |
| ! Responsible
| |
| ! Action
| |
| ! Notes
| |
| |- valign="top"
| |
| | 1<br>
| |
| | Development team<br>
| |
| |
| |
| Once release is ready the team opens a ticket in RT to queue XXXX with following informations
| |
| | |
| *Name of the tool
| |
| *Date of release
| |
| *Release notes
| |
| *Suggested deployment date
| |
| *Testing instance url and testing instructions
| |
| *Names of testers if testing is manual (if not defined Development team may ask to appoint testers)
| |
| | |
| | <br>
| |
| |-
| |
| | 2<br>
| |
| | Development team<br>
| |
| | Update ticket with information about resutls of the testing <br>
| |
| | <br>
| |
| |-
| |
| | 3<br>
| |
| | Development team
| |
| | Provide link to updated documentation<br>
| |
| | <br>
| |
| |-
| |
| | 4<br>
| |
| | Development team and Operations team<br>
| |
| | Agree on deployment date<br>
| |
| | <br>
| |
| |-
| |
| | 5<br>
| |
| | Operations team<br>
| |
| | Inform OMB about upcoming deployment<br>
| |
| | <br>
| |
| |-
| |
| | 6<br>
| |
| | Development team
| |
| | Deploy release<br>
| |
| | <br>
| |
| |-
| |
| | 7
| |
| | Operations team
| |
| | Close RT ticket after a week after deployment only if release was successful
| |
| |
| |
| |}
| |
| | |
| = Revision History =
| |
| | |
| {| class="wikitable"
| |
| |-
| |
| ! Version
| |
| ! Authors
| |
| ! Date
| |
| ! Comments
| |
| |-
| |
| | <br>
| |
| | <br>
| |
| | <br>
| |
| | <br>
| |
| |}
| |
| | |
| [[Category:Operations_Procedures]]
| |
The wiki is deprecated and due to be decommissioned by the end of September 2022.