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.
Difference between revisions of "EGI Change Management"
| Line 5: | Line 5: | ||
Ensuring effective change management within the EGI’s production IT environment is extremely important in ensuring high-quality delivery of IT services. | 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 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) [[File:Request+for+change+template.doc]] 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. It consists of employees of the EGI Foundation including the Technical Director and members of the senior operations and management team. | The CAB meets to assess and approve changes and is coordinated on the '''egi-cab@mailman.egi.eu''' mailing list. It consists of employees of the EGI Foundation including the Technical Director and members of the senior operations and management team. | ||
Changes are tracked as [https://rt.egi.eu/rt/index.html RT] tickets on the '''change-mgmnt''' queue, while people can submit a completed [[File:Request+for+change+template.doc]] to change-mgmnt@egi.eu. The change risk (likelihood X impact) should then be evaluated by the Service Owner and recorded as custom fields on the ticket in preparation for the CAB review. Further details about evaluating risk may be found here: [[File:IMS-RMGuideline-060117-1020-4791.pdf]]. | Changes are tracked as [https://rt.egi.eu/rt/index.html RT] tickets on the '''change-mgmnt''' queue, while people can submit a completed RfC [[File:Request+for+change+template.doc]] to change-mgmnt@egi.eu. The change risk (likelihood X impact) should then be evaluated by the Service Owner and recorded as custom fields on the ticket in preparation for the CAB review. Further details about evaluating risk may be found here: [[File:IMS-RMGuideline-060117-1020-4791.pdf]]. | ||
Click https://documents.egi.eu/public/ShowDocument?docid=2944 for an introduction to the process. | Click https://documents.egi.eu/public/ShowDocument?docid=2944 for an introduction to the process. | ||
Revision as of 11:49, 6 January 2017
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) File:Request+for+change+template.doc 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. It consists of employees of the EGI Foundation including the Technical Director and members of the senior operations and management team.
Changes are tracked as RT tickets on the change-mgmnt queue, while people can submit a completed RfC File:Request+for+change+template.doc to change-mgmnt@egi.eu. The change risk (likelihood X impact) should then be evaluated by the Service Owner and recorded as custom fields on the ticket in preparation for the CAB review. Further details about evaluating risk may be found here: File:IMS-RMGuideline-060117-1020-4791.pdf.
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 |
| Operations Portal |
Cyril L'Orphelin |
| Service Monitoring - ARGO |
Christos Kanellopoulos |
| Configuration Database - GOCDB |
David Meredith |
| Helpdesk - GGUS |
Gunter Grein |
| Accounting - Accounting repository (Computing and Grid) |
Adrian Coveney |
| Accounting - Accounting Portal |
Iván Díaz Álvarez |
| Messaging |
Christos Kanellopoulos |
| Training Infrastructure |
Gergely Sipos |
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 |