netbox platform not matching the VM host platform

[cbrassel]

Hi,
the syncing process maps the vsphere "Guest Info" to the netbox "platform" field. But the Guest Info does not reflect the real operating system installed on the VM, but (I think) only the Os choice made at the creation of the VM.
Looking into vsphere vm settings They are some interesting setting like guestInfo.detailed.data that contains for linux hosts :
architecture='X86' bitness='64' distroAddlVersion='24.04.1 LTS (Noble Numbat)' distroName='Ubuntu' distroVersion='24.04' familyName='Linux' kernelVersion='6.8.0-49-generic' prettyName='Ubuntu 24.04.1 LTS'
or for a windows host :
architecture='X86' bitness='64' buildNumber='20348' distroName='Windows' distroVersion='10.0' familyName='Windows' kernelVersion='20348.2849' prettyName='Windows Server 2022, 64-bit (Build 20348.2849)'
What would be nice is to extract at least the prettyName from this setting and inject it into the platform field of netbox.

is it feasible to set this up?

Regard's
Claude

[bb-Ricardo]

Hi,

This is very interesting and I need to have a look into it. This is exposed to vCenter via the guest tools?

[cbrassel]

Hi,
yes, from my understanding by default open-vm-tools pass the details of the operating system to vcenter.
But it seem's to be only the case for recent open-vm-tools, when I say recent I mean that ubuntu 12 open-vm-tools or windows 2008 vmtools return the null value.
To give you a better idea I have extracted all the guestInfo.detailed.data from our vcenter in the following list.
guest_info_data.txt
Regard's
Claude

[bb-Ricardo]

great, thank you

[bb-Ricardo]

Hi @cbrassel ,

I just pushed a new commit to the development branch. This is more a quest as I can see any detailed info in my test setup.

Would you be able to test this? If it does not work, can you run the script with -l DEBUG3 and add here the example output for the guest data of one VM which contains this attribute?

Thank you

[bb-Ricardo]

Hi, I implemented it and it works pretty neat. Thank you for this suggestion again. Will close this issue.