Collaboration with GLPI-technical changes¶

CPU core/thread¶

FusionInventory and OCS Inventory can report the number of cores and threads of a CPU. Today, GLPI only display the number of logical CPUs.

For an asset management software, the number of real physical CPUs is probably more important and a machine can have different CPUs, that's why we suggest to import the same CPU structure in GLPI (machine 1<>n CPUs).

This is the information we wish to see integrated in GLPI.

• number of cores (CORE)
• number of threads per cores (virtual CPU in a CORE) (THREAD)
• manufacturer, eg AMD/Intel/Transmeta/Cyrix/VIA (MANUFACTURER)
• name, e.g: Intel(R) Core(TM)2 Duo CPU P8600 @ 2.40GHz (NAME)
• ID (ID)
• serial number (SERIAL)
• frequency in MHz (SPEED)

The CPU ID is shared between all the same CPU and can be useful to identify the same CPU with different name ( http://en.wikipedia.org/wiki/CPUID )

PCIIDS¶

FusionInventory collect hardware PCIID. This information is used to identify the manufacturer, the product and the product family ( http://pciids.sourceforge.net/ ) even if the driver gives a wrong information. We wish to see this information available in the glpi_devicepcis table.

• PCI ID, e.g: 8086:2a40
• PCI class ID
• PCI subsystem ID, e.g: 8086:2a40
• PCI location, e.g: 00:02.1

Actually, we think the inventory agent should not collect the name and the manufacturer of a device.

More serial numbers¶

Serial number are useful to help identify computers during the inventory and can improve GLPI support of other inventory solutions. We do extract serial numbers for various devices and wish to see these informations added in GLPI.

• Hard drive
• Motherboard (ENCLOSURESERIAL, BASEBOARDSERIAL, BIOSSERIAL, ASSETTAG)
• Memory
• Partition

Battery¶

FusionInventory collects laptop battery information. We believe this information is generic enough to be integrated in GLPI. This what we retrieve:

• capacity in mWh (CAPACITY)
• voltage in mV (VOLTAGE)
• manufacturer (MANUFACTURER)
• manufacturing date in DD/MM/YYYY format (DATE)
• name (NAME)
• serial number (SERIAL)

USB device¶

USB devices are identified by an ID number much like PCI. We collect them and think the information can be useful in GLPI. For example, to identify a barcode scanner plugged in a computer.

• vendor ID. 4 hexa char (VENDORID)
• product ID. 4 hexa char (PRODUCTID)
• serial number (SERIAL)
• USB Class, e.g: 8 for Mass Storage (CLASS)
• USB Sub Class (SUBCLASS)
• name (optional) (NAME)

Virtual Machine MAC addresses¶

Sometime the UUID is not enough to identify a virtual machine. That's the reason why we also collect their MAC addresses. We think this information is important to reduce the number of badly associated host/VM.