Kubernetes / Container Discovery and Linux Server / VM Discovery

[PG2]

I'm hoping someone in the community might have some insight.

We've recently activated container discovery using CNO. We have observed that discovery will create Linux Server CIs to reflect the compute which the container nodes are hosted on.

We also have Vcenter discovery activated which is discovering the VM instance equivalent of the Linux Server. 

It would be nice if there was a relationship between the Linux Server and the VM Instance CIs. We could use this relationship to help lifecycle the Linux Server CI.

Does anyone have any thoughts about how to handle this? And whether there is any value in creating such a relationship?

[AJ-TechTrek]

Hi @PG2 ,

Yes realtionship with Virtual Machine to Linux Server Host will be created by ServiceNow OOB, We have no need to anything.

Can you please run the Vcenter discovery on 1st Place and then run the Linux Server or Host discovery and check the result then, It must be resolve the issue of relationship.

Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.

Thanks

AJ

Linkedin Profile:- https://www.linkedin.com/in/ajay-kumar-66a91385/

ServiceNow Community Rising Star 2024

[AJ-TechTrek]

Hi @PG2 ,

Yes realtionship with Virtual Machine to Linux Server Host will be created by ServiceNow OOB, We have no need to anything.

Can you please run the Vcenter discovery on 1st Place and then run the Linux Server or Host discovery and check the result then, It must be resolve the issue of relationship.

Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.

Thanks

AJ

Linkedin Profile:- https://www.linkedin.com/in/ajay-kumar-66a91385/

ServiceNow Community Rising Star 2024

[Saptarshi7]

The Model however is getting created as Unknown. Do you have any idea as to how to fix this? This is coming from Kubernetes Pattern. I checked the pattern and the linux Server creation step doesnt have a Model Variable.

[MattSN]

After VMware discovery connects to your vCenter API and completes its discovery, there is second discovery job that should run immediately after called "Virtual Machine Discovery". It goes through the list of VM IP addresses and tries to connect to the host OS via SSH for Linux or WMI for Windows. For this to work:

1. Your MID server must have connectivity via TCP 22 for SSH connections

2. You must have a discovery credential in ServiceNow that can be used to login to the Linux server (either password or private key)