Best Practice in handling relationships when retiring a CI

Jacques Panchar
Giga Contributor

‎05-06-2020 06:51 AM

Dear all,

I am working in an organization that has been using manual Configuration Management for years, and that is incrementally moving towards an automated process through discovery.

In this context, I have a question regarding the best practice when you retire a CI (or move it from an "active" state to an "inactive" state) regarding all the relationships that are defined for this CI.

My first guess would be to say that what you should do when you retire a CI is to remove all its relationships, provided :

  • Deactivate the links only when the CI goes from an "Active" to an "Inactive" state.
  • Configure Discovery correctly :
    • A priori, Discovery cannot switch a CI from an Active state to an Inactive state.
    • In general, Discovery can only remove links it is able to detect and recreate.
  • For other possible mechanisms, prevent any automatic disabling of links

Does anybody have any suggestion regarding this?

Best regards,

Jacques

Labels:
0 Helpfuls
  • 1,578 Views
2 REPLIES 2

Rahul Priyadars
Giga Sage
Giga Sage

‎05-06-2020 07:40 AM

Hi ,

My first guess would be to say that what you should do when you retire a CI is to remove all its relationships, provided : --  its scenario based.

Let say i have an app and one of the server is retired but app is still active. Here we must remove relationship as it may give wrong info in impact graph etc.

when whole app is gone then we can remove remove relationships or can keep . Make sure these retired CIs are not visible in ITIL module like IM/CM/PM etc.

Discovery will not automatically remove these Relationships. 

Regards

RP

 

 

Jacques Panchar
Giga Contributor
In response to Rahul Priyadars

‎05-08-2020 03:03 AM

Thank you Rahul.

Best,

Jacques

0 Helpfuls