ChaRDM Procedures

Procedure documenting how an emergency change is registered and approved before deployment of the emergency release and reviewed after implementation.

An emergency release consists in the releasing of one product, or a set of products, with the targeted goal of solving a specific problem that affects the EGI infrastructure. To qualify for an emergency release the problem should be classified in at least one of the following categories:

• A critical security patch
• A critical bug affecting multiple resource centres

Emergency releases are deployed by the services providers and apply to the services listed in the EGI Service Portfolios that are owned by the EGI Foundation.

Procedure documenting how a normal change is registered and approved before release deployment and reviewed after implementation.

This procedure applies to normal releases of the centrally-provided production services that need to be fully built, tested and deployed.

This may be either:

• a high risk/impact change needing careful testing
• a set of linked changes to test and deploy together
• lower priority changes bundled together to reduce downtime.

Procedure documenting how a standard change is registered and approved before release deployment and reviewed after implementation.

This procedure applies to individual low risk/impact change and provides steps for service updates and releases of the centrally-provided production services.

The procedure oversees how standard changes list should be maintained