Operations Change Management Procedures
This is an attempt to formalize the Operations Change Management Procedures in an official document. These procedures will be loosely based on the ITIL Incident Priority scheme.
- This is a measure of how critical the service is to the work being done. Impact is normally directly proportional to the number of users affected. This can also be dependent on the production level work being done at the time of the change.
- This is the need to react quickly to resolving the issue. Urgency should be determined by the level of service agreed to in the SLAs. For services not yet functioning under as SLA Urgency will be determined by the Operations Coordinator with guidance from the Production Coordinator.
- Is a function of Impact and Urgency of a giving incident or change.
Using the follow table each change will be given an Priority:
5 = Routine
4 = Normal
3 = Minor
2 = Major
1 = Emergency
- Everyday continuous maintenance events. This includes but is not limited to routine scheduled maintenance events. Approval of the Routine events will be given by the Operations Coordinator.
- This includes common changes. Approval of Normal changes will be given by the Operations Coordinator.
- Minor changes that affect users of Operations Services. This includes changes to Operations Services that have a low Impact or Urgency. Approval will be given by the Operations Coordinator after consultation and review with the Production Coordinator. These changes will occur within the scheduled release periods
- Major changes that affect users of Operations Services. This includes all items with high Impact or Urgency. Approval will be given by the Operations Coordinator after consultation and review with the Production Coordinator and a member of the Executive Team. These changes will occur within the scheduled release periods
- Events with high impact and urgency. These incidents will be handled as defined in the SLA for the Operations Service in question. The Executive Team and the Production Coordinator will be alerted of any changes classified as Emergency.
The following section maps some known changes as well as attempts to classify some potential changes into their Priority. The following list is provide to show examples of priorities and is not all-inclusive. Items not listed will have the priority determined by the table above.
- CA/CRLs Updates
- Daily Backup
- Munin and Nagios Monitoring Probes
- Updates to Software Cache
- Updates to VO-Package and CA distribution
- Bug fixes to Production Services
- New Feature Requests for Existing Services
- Reformatting of Data Provided by Services
- Minor Functionality Change of a Service
- Installing New Service
- Changing Service Levels (As defined in SLA)
- Deprecating an Existing Service
- Major Functionality Change of a Service
- BDII Downtime
- Security Incident
- WLCG Tier 1 ALARM Ticket Submitted
- Any changes that have known potential security implications will be sent to the OSG Security team for review.
- 03 Mar 2010
Topic revision: r16 - 06 Dec 2016 - 18:12:52 - KyleGross