Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Document control
| Page properties | ||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| Excerpt | |||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
OverviewThe EGI Change Management is a centralized process for the EGI Federation. If organisations are providing EGI branded services and are already running their own internal Change Management process, they may continue to do so if their process meets the essential requirements of ISO20k with respect to change management:
In addition to the above, if any changes are planned that have the potential to impact other EGI branded services, then the EGI Change Management process should be informed in advance by submission of a ticket following CHM1. EGI Foundation should keep track of organizations running their own internal Change Management process and should periodically run a lightweight audit described in this procedure to ensure that the above requirements are being met. DefinitionsPlease 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
TriggersThe CHM Process Manager becomes aware that an organisation running an EGI branded service is running its own internal Change Management process Steps
Organisation | Date | Auditor | Auditee | Notes | IASA |
Marios Chatziangelou <mhaggel@iasa.gr> | All three essential requirements are currently being met. Changes are discussed within a bi-weekly internal team meeting. In addition, ad-hoc meetings are run during the week to evaluating changes. The team currently uses GitLab as a tool for recording changes https://gitlab.iasa.gr which are partially synchronized with the public (https://github.com/IASA-GR . For each change, the team collectively discusses what could go wrong and tests on their development environment in the days/weeks running up to the change. Although there is no formal Post Implementation Review, if there are problems following a change, these are recorded in the weekly meeting minutes. If appropriate, issues are tracked on GitLab. Everything is recorded, including who did the changes, when the changes were done, in GitLab. It was re-iterated that IASA are free to choose to use the central CHM if they wish, and they are obliged to if changes are done which directly affects other EGI services. AppDB (provided by IASA) has now moved under the scope of the EOSC-hub CHM and so IASA no longer provides any services under EGI CHM. As such, CHM within IASA needs no longer be considered within EGI CHM, until and unless they provide services within the scope in the future. | ||||||||||||||||||||||||||||||||
Table of contents
| Table of Contents | ||||
|---|---|---|---|---|
|