ITOM Licenseable CI Count Increase

[Brian43]

In the last few months, we have begun to transition our persistent VDI's to Azure.  This appears to have caused a rise in the number of servers that are counted in the ITOM License count by around 800.

In my review, it appears to me that when our VDI's were built and maintained in VMWare.  They all were contained in Virtual Machine Instances (VMIs) and those VMIs were attached to ESX Servers.  So, in this case, there were not duplication around the servers and the VMIs based on the following excerpt from the T&C.

“For cmdb_ci_vm_instance (and child class) CIs, we filter out those with Instantiates::Instantiated By or Virtualizes::Virtualized By relationships with cmdb_ci_server (or child class) CIs (which also meet the above criteria), to avoid duplicate counting of logical virtual servers that are represented by CIs of both classes”

Now that the VDI's are in Azure, they are all contained in their separate VMIs.  These VMIs are not associated with an ESX or Xen Server or any server ci class at all.  So, based on the T&C excerpt above, each of the VMIs would be counted individually.

I guess my question here is; have I analyzed this correctly?  Due to the fact that the Virtual Machine Instances that house the VDIs are not tied to any class of server, they too are being counted as servers in the ITOM License count?  This is not a duplication in count but just an increase due to the locale of the VDI's and their associated Virtual Machine Instances?

Any input or feedback would be great to hear.

[SiD2 · Accepted solution]

Hi @Brian43 

Yes, it's just the new licensable CI count increased and hence your license count too. The T&C excerpt just talks about how VMs and its resp servers wouldn't be counted as duplicate and right now this doesn't relate to your use case.

In future, if you happen to discover the physical servers behind these VMIs then also your count would remain same per above excerpt as those are considered as duplicate.

[Brian43]

SiD2,

I appreciate the response here.  This exactly what I have conveyed to my ServiceNow Director.

That issue is, in Azure, there are no servers associated with these Virtual Machine Instances.  There will not be.  The VDI's are built and are connected through the Virtual Machine Instances directly.  From there, its related items shows provisioned from the image, hosted on the Azure Datacenter, and connections to the virtual nic and disk via a Use End Point To connection.

There will not be a server associated that will house the Virtual Machine Instances for these VDI's as they do in VMWare.

Again, thank you for your view.