Document control
This procedure is meant to cover releases for which it's not necessary to go through a complete planning/testing/deployment phase, typically some low risk and low impact changes. A Jira ticket coming from CHM is used to orchestrate the complete release and deployment. Once the release will have been deployed 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. Triggers CHM1 Manage changes including emergency changes 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: This information is also meant to capture the CI baseline. Gives green light by updating the ticket. Release Owner RDM Staff Release Owner RDM Staff Service Supplier Deploy the release. Release Owner RDM Staff If the release took place, waits for a week to have more understanding about the release behaviour. Comments the Jira ticket to provide feedback about the release. Re-assigns the Jira ticket to CHM so that it can be reviewed according to CHM1.Overview
Definitions
Entities involved in the procedure
Steps
Step# Responsible Action Prerequisites, if any 1. Updates Jira ticket assigned to CHM status to mark it as accepted for a lightweight release or as a normal change. Change has been accepted by CHM as a standard change or as a normal change that should be handled via a lightweight release. 2. RDM Staff 3. 4. Informs NOC-Managers by email about the affected service or service component providing the agreed release date. 5. Informs CRM about the release by sending a mail to cst [AT] mailman.egi.eu and providing a link to the Jira ticket so that they can provide feedback if needed. 6. Register a downtime for the service in GOCDB, using 'at risk' if no downtime is expected. 7. Service Supplier 8.