Last week I wrote about the Change Management conflict checking.
The example I showed was the Conflict checker ensuring that the Change is scheduled to start and finish within the Maintenance Window.
I should have pointed out that this functionality is only available in the demo instance at the moment, and will hopefully be included in the upcoming October 2011 release. Sorry for any confusion there.
As a reminder the conflict checker my mark a Change record as conflicted based on a few different reasons:
- The change window occurs outside of a Maintenance Window. "Not in Maintenance Window"
- The change window overlaps with another Change Record against the same component of the Infrastructure (The same Configuration Item) "CI already scheduled"
- The change occurs during a defined Blackout Window, where no changes should occur to this CI "Blackout"
- A relationship exists with a parent/child CI and the Change occurs when that CI isn't available for Change. "Parent/Child CI already scheduled
In this post we are going to look at the conflict checker detecting issues where a CI has overlapping Change Windows.
CI already scheduled
Using the same example Maintenance Window as in the first post, today there are two Request For Change records needing approval.
| Change number | Description | CIs | Change Window |
|---|---|---|---|
| CHG0030001 | Increase memory to 4GB |
| 2011-09-24 from 10:00 to 12:00 |
| CHG0030002 | Apply Security Patches to Domain Controllers |
| 2011-09-24 from 11:00 to 15:00 |
As you can see CHG0030002 is going to overlap CHG0030001 for an hour because it includes LON1DC01 as an affected CI.
The Change Records look like this:
So, obviously there would be a problem with approving both of these Change records, as we would have concurrent activity on LON1DC01.
Clicking the Check Conflict related link will show us the conflict status....
One important point here is that LON1DC01 wasn't the Primary CI for CHG0030002 - it was added as an Affected CI at the bottom of the form.
Change conflict detection has 2 modes - Basic and Advanced. To check the conflict status of related CIs requires that you set the mode to Advanced, which can be done in the Conflict Properties.
I'll roll up the last 2 conflict conditions into the last blog post.
Read also:
3 Comments
