|
|
| (36 intermediate revisions by 6 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 egi.eu
| |
| |Doc_status = FINAL
| |
| |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 production instances of the tools mentioned in the following list:
| |
| | |
| * Operations portal
| |
| * Service Availability Monitoring
| |
| * GOCDB
| |
| * GGUS
| |
| * Accounting portal
| |
| * Metrics portal
| |
| * Gstat
| |
| * Availability Calculation Engine
| |
| * AppDB
| |
| * e-GRANT
| |
| * Network monitoring
| |
| * Security monitoring
| |
| * Catch-all services
| |
| * Software provisioning infrastructure
| |
| * Collaboration tools
| |
| * Authentication and Authorization Infrastructure (AAI)
| |
| | |
| Adding and removing tools from this list can be done by EGI central operations office, upon request, and every change is communicated to the OMB ML before being implemented. Please, open a ggus ticket to the Operations SU to request any change.
| |
| | |
| = 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 =
| |
| | |
| *'''Service Provider team''': Team responsible for development, release and deployment of the tool <br>
| |
| *'''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<br>
| |
| *Development team should follow [https://wiki.egi.eu/wiki/Instructions_for_Production_Tools_teams#Release_and_deployment_management https://wiki.egi.eu/wiki/Instructions_for_Production_Tools_teams#Release_and_deployment_management]
| |
| * In case of deployment of a major update of a tool, a contingency plan must be agreed with the team who operates the tool, to handle major disruptions caused to production activities by problems in the new version of the tool.
| |
| | |
| = Acceptance criteria =
| |
| | |
| A new release of a Tool can be deployed in production if:
| |
| * All the prerequisites are satisfied
| |
| * The results of the testing in step ''3b'' do not show any major problem:
| |
| ** The tool is usable in all its features
| |
| ** The interoperability with the other tools is not broken
| |
| | |
| = Steps =
| |
| | |
| {| width="906" height="305" class="wikitable"
| |
| |-
| |
| ! <br>
| |
| ! Responsible
| |
| ! Action
| |
| ! Notes
| |
| |- valign="top"
| |
| | 1<br>
| |
| | Service Provider team<br>
| |
| |
| |
| Once release is ready the team opens a GGUS ticket to Operations with the following information:
| |
| | |
| *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
| |
| | Operations Team
| |
| |
| |
| *Inform the Noc-Managers about the upcoming release, asking if there is anyone else interested in performing the tests
| |
| *can add further people for performing the tests
| |
| *The suggested duration of the test phase is two weeks
| |
| *Update the ticket
| |
| |-
| |
| | 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<br>
| |
| | <br>
| |
| |-
| |
| | 4<br>
| |
| | Service Provider team
| |
| | Provide in the ticket the link to updated documentation<br>
| |
| | <br>
| |
| |-
| |
| | 5
| |
| | Service Provider team and Operations team<br>
| |
| | Agree on deployment date and update the ticket
| |
| | <br>
| |
| |-
| |
| | 6
| |
| | Operations team
| |
| | 10 days before the upcoming deployment, inform the Noc-Managers.
| |
| Update the ticket
| |
| | <br>
| |
| |-
| |
| | 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
| |
| | <br>
| |
| |-
| |
| |9
| |
| |Product team or Operations team
| |
| |Link the changes (RT tickets) that are implemented to this release in the GGUS ticket.
| |
| |<br>
| |
| |-
| |
| | 10
| |
| | Operations team
| |
| | Close the GGUS ticket after a week of the deployment only if the release was successful
| |
| |<br>
| |
| |}
| |
| | |
| = Revision History =
| |
| | |
| {| class="wikitable"
| |
| |-
| |
| ! Version
| |
| ! Authors
| |
| ! Date
| |
| ! Comments
| |
| |-
| |
| | <br>
| |
| | Alessandro Paolini
| |
| | 2016-07-25
| |
| | added the new AAI in the tools list
| |
| |-
| |
| |
| |
| | Alessandro Paolini
| |
| | 2016-03-22
| |
| | procedure revised and made some changes
| |
| |}
| |
| | |
| [[Category:Operations_Procedures]]
| |
The wiki is deprecated and due to be decommissioned by the end of September 2022.