- My View
I want to populate the CMDB with VMs from vCenter, I just want to pull the VMs I don't need to procure VMs yet.
After reading the Wiki, I still don't know if at all SerivceNow Discovery and/or Orchestration is required to be enabled in order to just pull VMs.
I see that there is a related link "Discover vCenter Details" as per Wiki, does it means that it is actual Discovery feature running with a MID Server in order to "discover" the VMs?
That's right. ServiceNow uses Discovery to discover the different VMs by interacting with VMWare VCenter.
As the documentation states:
Discovery can explore the VMware vCenter process running on a Windows or Linux host.
ServiceNow Discovery supports these vCenter versions:
- vCenter versions 6.0 and earlier
- vSphere version 5.5
- vCenter appliance version 6.0 and earlier
See vCenter data collected for a description of the VMware architecture and component relationships.
When Discovery runs, a classifier called vCenter classifies the process running on a Windows or Linux machine.
After classifying vCenter, Discovery launches the VMware - vCenter Datacenters probe, which in turn launches specific probes that return information about ESX machines, virtual machines, and other vCenter objects.
If you use a domain account to access vCenter, specify the domain with the user name in the credential record in one of the supported formats such as Domain\UserName.
Here goes the links to the documentation. Please go through all of it. It will greatly expand your understanding of how discovery actually discovers VMWare WMs through VCenter.
I hope this helps and answers your question
I've developed a REST integration with vCenter 6.5 in order to populate the CMDB with VM's without the need to purchase Discovery or Orchestration. If you are interested please contact me email@example.com