How to handle vm being discovered by vcenter discovery and IP discovery (WMI/SSH)

[Gregory Gribben]

Hey guys, 
I am wondering if anyone is currently using vcenter discovery in conjunction with IP discovery (OS level discovery via winrm/wmi/ssh).

How are you guys handling the CIs that are created under each respective class? I am running into a scenario where if the VM is deleted from disk in vcenter, the VM CI is retired in cmdb, which is expected. However, if there is also an OS level CI (Linux Server, Windows Server). That CI remains as installed/operational, and will eventually go stale due to the inability to discover the device as its no longer available. 

-Greg

[Gregory Gribben]

There does not appear to be any relationship built between the Virtual Machine Instance and the Server classes. 

[johnfw2 · Accepted solution]

Hi Greg,

There should be an instatiates::instantiated by relationship between the VM Instance and the Server CIs. This is created during horizontal discovery of the Server by a Business Rule 'Virtual computer check'. Any action that needs transferring to the server, or vice-versa, should follow that instantiation relationship.

You could use a business rule to set the server to Retired when the VMI gets a 'terminated' state or Retired install_status.

Using cloud event would make that update in near-time, when the VM terminate event is processed.

[Gregory Gribben]

Bingo, that's what I was looking for. I don't know why I didn't see the relationship before.  Thank you so much!