- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Scheduling your Change Request there are 10 different types you may encounter.
1. Inside Blackout Window
value: [blackout]
Description: Check against blackout windows
Schedule: cmn_schedule_blackout
Condition: cmn_schedule_blackout.source=cmdb_ci & cmn_schedule_blackout.source=applies_to=cmdb_ci & cmn_schedule_blackout.condition (if empty applies to all)
2. Child Inside Blackout Window
value: [child_blackout]
Description: Check whether the change falls within child CIs' blackout windows
Schedule: cmn_schedule_blackout
Condition: cmn_schedule_blackout.source=cmdb_ci & cmn_schedule_blackout.source=applies_to=cmdb_ci & cmn_schedule_blackout.condition (if empty applies to all)
3. Parent Inside Blackout Window
value: [parent_blackout]
Description: Check whether the change falls within parent CIs' blackout
Schedule: cmn_schedule_blackout
Condition: cmn_schedule_blackout.source=cmdb_ci & cmn_schedule_blackout.source=applies_to=cmdb_ci & cmn_schedule_blackout.condition (if empty applies to all)
4. CI Already Scheduled
value: [ci_already_scheduled]
Description: Checking against changes already scheduled for the same CI. A change_request.cmdb_ci (basic mode) and/or Affected CIs (advanced mode) must reference/share a CI and
change_request.start/end_date overlaps with another change_request.start/end_date
5. Parent CI Already Scheduled
value: [parent_ci_already_scheduled]
Description: Check against changes already scheduled for a parent of the CI associated to your Change Request. A change_request.cmdb_ci (basic mode) and/or Affected CIs (advanced mode) must reference/share a CI and
change_request.start/end_date overlaps with another change_request.start/end_date
6. Child CI Already Scheduled
value: [child_ci_already_scheduled]
Description: Check against changes already scheduled for a child of the CI associated to your Change Request. A change_request.cmdb_ci (basic mode) and/or Affected CIs (advanced mode) must reference/share a CI and
change_request.start/end_date overlaps with another change_request.start/end_date
7. Not in Maintenance Window
value: [not_in_maintenance_window]
Description: Check whether the change falls outside the CIs' maintenance window
Schedule: cmn_schedule_maintenance
Condition: cmn_schedule_maintenance.source=cmdb_ci & cmn_schedule_maintenance.source=applies_to=cmdb_ci & cmn_schedule_maintenance.condition (if empty applies to all)
8. Child Not in Maintenance Window
value: [child_not_in_maintenance_window]
Description: Check whether the change falls outside the child CIs' maintenance window
Schedule: cmn_schedule_maintenance
Condition: cmn_schedule_maintenance.source=cmdb_ci & cmn_schedule_maintenance.source=applies_to=cmdb_ci & cmn_schedule_maintenance.condition (if empty applies to all)
9. Parent Not in Maintenance Window
value: [parent_not_in_maintenance_window]
Description: Check whether the change falls outside the parent CIs' maintenance window
Schedule: cmn_schedule_maintenance
Condition: cmn_schedule_maintenance.source=cmdb_ci & cmn_schedule_maintenance.source=applies_to=cmdb_ci & cmn_schedule_maintenance.condition (if empty applies to all)
10. Assigned To Already Scheduled
value: [assigned_to_already_scheduled]
Description: Checking against changes already scheduled for the same assigned to person. A change_request.assigned_to must reference/share an assigned to person and change_request.start/end_date overlaps with another change_request.start/end_date
But you said there were 10 types!
Strictly that is true there are 10 types of conflict, however it is possible to encounter the #7 Not In Maintenance Window, via another type of configuration setup. Also this configuration setup often contains a mistake, so I add it here as number 11.
11. Not in Maintenance Window
value: [not_in_maintenance_window]
Description: Check whether the change falls outside the schedule of the maintenance schedule reference field on the CI.
Schedule: cmdb_ci.maintenance_schedule & cmn_schedule.type=maintenance
DO NOT point cmdb_ci.maintenance_schedule to cmn_schedule_maintenance (also a schedule resulting in double processing)
There is NO equivalent for blackout, at the time of writing this post.
- 2,763 Views
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.