Difference between revisions of "EGI Change Management"
Jump to navigation
Jump to search
The EGI Change Management (CHM) Process
Standard Changes
Line 31: | Line 31: | ||
=== EGI Datahub === | === EGI Datahub === | ||
{| width="776" cellspacing="1" cellpadding="1" border="1" height="78" | {| width="776" cellspacing="1" cellpadding="1" border="1" height="78" |
Revision as of 11:15, 14 November 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 assign resources, assess risk and minimize any potential negative impact to services.
Click https://documents.egi.eu/public/ShowDocument?docid=2944 for an introduction to the process.
Services that fall under Change Control
Service Title |
Service Owner |
EGI DataHub |
Lukasz Dutka |
EGI AppDB |
Marios Chatziangelou |
vmcatcher/CloudKeeper |
Boris Parak |
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 |