Description: The vm_disk_configuration table in the DWH database has a vm_disk_interface column, but it is never populated. The column is always NULL.
To reproduce
Look at the vm_disk_interface column in the vm_disk_configuration table. It will always be null even though the data exists in the engine database
Expected behavior
It vm_disk_interface should be populated with a number corresponding to the disk interface enum?
myhost # SELECT * FROM v4_5_enum_translator WHERE enum_type IN ('VM_INTERFACE_TYPE', 'DISK_INTERFACE', 'DISK_TYPE', 'VM_DISK_INTERFACE') ORDER BY enum_type, enum_key;
enum_type | enum_key | value
-------------------+----------+---------
VM_DISK_INTERFACE | 0 | IDE
VM_DISK_INTERFACE | 1 | SCSI
VM_DISK_INTERFACE | 2 | Virt IO
However those values appear to be outdated and don't match current engine db values in its disk_vm_element table
(VirtIO, VirtIO_SCSI, SATA, IDE).
While the Grafana reports don't currently seem to use that column, a report showing which systems do or don't use VirtIO (and therefore run less efficiently) would be useful. An attempt to create such a report identified this gap. The dwh_vm_disk_configuration_history_view in the engine database doesn't include this data either and would need to be changed to include it.
Description: The vm_disk_configuration table in the DWH database has a vm_disk_interface column, but it is never populated. The column is always NULL.
To reproduce
Look at the vm_disk_interface column in the vm_disk_configuration table. It will always be null even though the data exists in the engine database
Expected behavior
It vm_disk_interface should be populated with a number corresponding to the disk interface enum?
myhost # SELECT * FROM v4_5_enum_translator WHERE enum_type IN ('VM_INTERFACE_TYPE', 'DISK_INTERFACE', 'DISK_TYPE', 'VM_DISK_INTERFACE') ORDER BY enum_type, enum_key;
enum_type | enum_key | value
-------------------+----------+---------
VM_DISK_INTERFACE | 0 | IDE
VM_DISK_INTERFACE | 1 | SCSI
VM_DISK_INTERFACE | 2 | Virt IO
However those values appear to be outdated and don't match current engine db values in its disk_vm_element table
(VirtIO, VirtIO_SCSI, SATA, IDE).
While the Grafana reports don't currently seem to use that column, a report showing which systems do or don't use VirtIO (and therefore run less efficiently) would be useful. An attempt to create such a report identified this gap. The dwh_vm_disk_configuration_history_view in the engine database doesn't include this data either and would need to be changed to include it.