Alert.png 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.

PROC23

From EGIWiki
Revision as of 17:47, 28 January 2016 by Krakow (talk | contribs) (Created page with "{{Template:Op menubar}} {{Template:Doc_menubar}} {{TOC_right}} {{Ops_procedures |Doc_title = Production tools release and deployment process |Doc_link = https://wiki.egi.eu/wik...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
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
  • 'XX'X:

Requirements

The prerequesites are:

  • Tool is used by EGI production Infrastructure

Steps


Responsible Action Notes
1
Development team

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)

2
Development team
Update ticket with information about resutls of the testing

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