Difference between revisions of "PROC23"

From EGIWiki
Jump to: navigation, search
(Steps)
(Steps)
Line 132: Line 132:
 
|9
 
|9
 
|Product team or Operations team
 
|Product team or Operations team
|Link the changes (RT tickets) that are implemented to this release in the GGUS ticket.
+
|Link the changes (RT tickets) that are implemented to this release in the GGUS ticket. ''Added on Nov 15th 2017''
 
|<br>
 
|<br>
 
|-
 
|-

Revision as of 15:42, 15 November 2017

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 egi.eu
Document Status FINAL
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 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 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
  • 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:

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


Responsible Action Notes
1
Service Provider team

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)

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

4
Service Provider team Provide in the ticket the link to updated documentation

5 Service Provider team and Operations team
Agree on deployment date and update the ticket
6 Operations team 10 days before the upcoming deployment, inform the Noc-Managers.

Update the ticket


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
9 Product team or Operations team Link the changes (RT tickets) that are implemented to this release in the GGUS ticket. Added on Nov 15th 2017
10 Operations team Close the GGUS ticket after a week of the deployment only if the release was successful

Revision History

Version Authors Date Comments

Alessandro Paolini 2016-07-25 added the new AAI in the tools list
Alessandro Paolini 2016-03-22 procedure revised and made some changes