Change Request and Business Services

[Steve Fox1]

We have a Business Service discovered and properly defined.   Everything is looking good so far. I I

If I open a change against the Business Service, I get the right conflicts (based on blackout and maintenance schedule based on the Business Service).   My question is if I open a change request against a piece (a server for example)   of the Business Service, I thought it would take on the properties of the overall Business Service but that is not happening.

As a example:

I have a Business Service called "Ordering" and it has multiple parts including servers:   Server A, Server B and Server C         I have a maintenance window of Sunday 2:00 AM - 6:00 AM on this Business Service.

If I open a change request on the Ordering Business Service CI   outside of this maintenance window, it works fine.

If I open a change on Server A   (as an example), I do NOT get a conflict.   I thought it would show as a conflict since it is outside of the normal maintenance window of the Business Service called "Ordering"....which Server A is a member.

[Michael Fry1]

How about querying the cmdb_rel_ci table, the table that holds the relationships, and add the business service(s) to the Affected CI's related list. Conflict Properties can be configured to check against the related list.

[Steve Fox1]

Michael,

We tried that optoion but we were unsuccessful.     The issue is we see the relationship in the cmdb_rel_ci table and it is correct.

The problem is we do not see the cmdb_rel_ci table as an option to select for our maintenance schedule.     Could we be missing a parameter that will make it available to us.

[Michael Fry1]

No, you won't be able to use cmdb_rel_ci table in your maintenance schedule. . . but what I was referring to, was to query the relationships table to get the business service(s) for the CI and add those business services to the Affected CI. You said you tried this? Can you share you script so I can take a look at it?

[Michael Fry1]

Quick question, which table do you on your Maintenance Schedules? Is it cmdb_ci_service or cmdb_ci? I'm thinking if cmdb_ci is used, that should cover you for Business Services and CIs.

[sayub]

Hey Micheal and Steve,

This is a interesting post and i have been following this as well. I tried using both CMDB_CI and Business Service table for maintenance window declaration but the result is the same. I believe the confusion that i have is that even though i have a parent child relationship defined in the CMDB_REL_CI tables between the Business Service and the Child Nodes/server CI (in my case two windows servers .199 and .127), when i create a change request and reference a windows server node (e,g, .199 CI) as a configuration item (which has a child relationship in CMDB_REL_CI table with my Business

service CI), i don't see the the maintenance window conflict invoked where it will say that since i have   a maintenance window scheduled for my Business Service CI and this particular node (.199) has a child relationship or has a dependency/child relationship to the Business Service CI, therefore the maintenance schedule for the Business Service CI should also apply to this particular node CI (.199) if we were trying to create a change request against it.

Sheikh