Difference between revisions of "EGI Change Management"
Line 26: | Line 26: | ||
|- | |- | ||
| Operations Portal<br> | | Operations Portal<br> | ||
| Cyril | | Cyril L'Orphelin<br> | ||
|- | |- | ||
| ARGO<br> | | ARGO<br> |
Revision as of 15:42, 12 December 2016
The EGI Change Management (CHM) Process
This is the homepage on the EGI Wiki of the EGI Change Management Process.
Ensuring effective change management within the EGI’s production IT environment is extremely important in ensuring high-quality delivery of IT services.
The purpose of the IT Change Management Policy is to manage changes in a planned and predictable manner in order to assess risks, assign resources, and minimize any potential negative impact to services. This is done by requiring change owners to prepare a Request for Change (RfC) where a set of standard questions regarding the change are answered and presented to the Change Advisory Board (CAB). The CAB meets to assess and approve changes and is coordinated on the egi-cab@mailman.egi.eu mailing list. Changes are tracked in RT on the change-mgmnt list, while people can submit a completed RfC to change-mgmnt@egi.eu.
Click https://documents.egi.eu/public/ShowDocument?docid=2944 for an introduction to the process.
Services that fall under Change Control
Service Title |
Person Managing the Service |
EGI DataHub |
Lukasz Dutka |
EGI AppDB |
Marios Chatziangelou |
vmcatcher |
Boris Parak |
Operations Portal |
Cyril L'Orphelin |
ARGO |
Christos Kanellopoulos |
GOCDB |
David Meredith |
GGUS |
Gunter Grein |
Accounting repository (Computing and Grid) |
Adrian Coveney |
Accounting Portal |
Iván Díaz Álvarez |
Messaging |
Christos Kanellopoulos |
Standard Changes
This is the list of standard, or pre-approved changes, listed by Service.
EGI Datahub
Title |
Description |
RT Ticket Reference |
Change 1 |
Description 1 |
RT#XXXX |
Change 2 |
Description 2 |
RT#XXXX |