UUID matching can be complicated, depending on the virtualization system
- vmware => no problem it seems
- virtualbox & libvirt and Parallels Desktop => http://forge.fusioninventory.org/issues/665
- maybe other systems that we haven't tested yet...
UUID matching needs to be done on the server side (ie on GLPI).
One thing that we can do it to detect the virtualization type (Virtualbox, libvirt, etc) and do processing (at display time)
- Physical (default) : default value. Indicates that a computer is a physical computer, not a virtual machine
- Virtual Machine : cannot tell what kind of virtualisation it is
Other matching systems¶
On some systems, it won't be possible to use uuid to link vm on a host and vm in glpi.
Matching can be done using name + ip
- AIX_LPAR :
FusionInventory 0.83+3.0 will support this virtualmachine type.
The serialnumber is shared between host and slave partitions.
we have this additional informations :
- VMNAME -> glpi_computervirtualmachines.name
- VMID -> missing field
- VMSYSTEM (AIX_LPAR) glpi_computervirtualmachines->virtualmachinesystems_id
We don't have the uuid in this system so we use the serial for matching.
So a new 'serialnumber' field in glpi_computervirtualmachines is needed. The display in computer form must be updated for show relations between host and slaves.
- add comment field in glpi_computervirtualmachines : can be automatically filled (for example by FusionInventory ESX/ESXI/vCenter agent in case of VMWare vCenter remote inventory)
- store vm mac addresses
- aix_lpar : add serialnumber (for linking vm to a host) and vmid