- Created by Baptiste Grenier, last modified on 2021 Sep 23
Document control
Area | RDM |
---|---|
Procedure status | FINALISED |
Owner | |
Approval status | APPROVED |
Approved version and date | v13 |
Statement | This procedure applies to regular releases of the centrally-provided production services that need to be fully built, tested and deployed. This may be either:
|
Dissemination Level | TLP:WHITE - Public |
This procedure is meant to cover releases for which it is required to go through a complete planning/testing/deployment phase. A Jira ticket coming from CHM is used to orchestrate the release and deployment, but in order to allow any participant to test and provide feedback during the testing phase a dedicated GGUS ticket is created. Once the release will have been deployed the GGUS ticket will be closed, feedback will be added to the Jira ticket and re-assigned to CHM so that they can review it. 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. Service Supplier: Team responsible for the actual development, release and deployment of the service or service component. NOC-Managers: Are informed regarding the release of the new service or service component and may provide further people for testing it. CHM1 Manage changes including emergency changes 1. Change Owner Appoint a Release owner, that will coordinating the release with the support of the RDM Staff. The ticket is assigned to the Release Owner. Release Owner RDM Staff Ensures that the ticket contains the following information, and interacts with Service Provider to collect it: The suggested duration of the test phase is usually two weeks. This information is also meant to capture the CI baseline. Service Supplier Creates a GGUS ticket against Operations SU, using release ticket type and to be used to collect and address feedback from NOC-Managers and external testers, containing the following information: Records the link to the GGUS ticket into the Jira ticket. Release Owner RDM Staff Release Owner RDM Staff Validates that the release planning and preparation is appropriate, interacts with Service Supplier as needed and gives green light on the suitable deployment date by updating the GGUS ticket. Release Owner RDM Staff Release Owner RDM Staff Service Supplier Release Owner RDM Staff If the release took place, waits for a week to have more understanding about the release behaviour. Closes the GGUS ticket. Comments the Jira ticket to provide feedback about the release. Re-assigns the Jira ticket to Change Owner so that it can be reviewed according to CHM1.Overview
Definitions
Entities involved in the procedure
Triggers
Steps
Step# Responsible Action Prerequisites, if any Updates Jira ticket assigned to CHM status to mark it as accepted for a regular release. Change has been accepted by CHM as a normal change that should be handled via a regular release. 2. RDM Staff 3. 4. 5. 6. Testers Update the GGUS ticket with performed tests and their results. 7. Service Supplier Once the test phase is over updates the GGUS ticket with information about results of the overall testing phase. 8. 9. Informs CRM about the release by sending a mail to ucst [AT] egi.eu and providing a link to the Jira ticket so that they can provide feedback if needed. 10. Informs NOC-Managers by email 10 days before the deployment. There is more than 10 days between the validation of the deployment from step 7 and the deployment in step 12. 11. Registers a downtime for the service in GOCDB, using 'at risk' if no downtime is expected. 12. Service Supplier Deploys the release. 13.