Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Invalid
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Events
-
Labels:None
Description
The id columns on the metering table are not populated for any of the idColumns (and specifically idEnterprise, idVirtualDataCenter, idVirtualApp, and idAppliance.
This means that it is not possible to correctly associate messages with an Enterprise/VDC/VApp or VM.
Why is this a problem? Currently, we are looking into a test fix for Interoute, and need to link a deploying VApp to entries in the metering table. As the id columns are not populated, we cannot go from the id straight to the VApp. This means that to uniquely identify the VApp we need the unique combination of Enterprise/VDC/VAPP names- which itself is not 100% reliable - but as some metering entries are written as 'Abiquo System' rather than the real Enterprise name we currently have no way of doing that, either :-( This means that metering entries for VDC/VApp names which are duplicated across Enterprises cannot be distinguished.
Finally, adding the ID columns may also help to fix the outstanding issue where metering entries are incorrectly reported against the wrong Enterprise/VDC. This is because the log filtering code could be altered to use the IDs to filter instead of the names...just a thought...
This means that it is not possible to correctly associate messages with an Enterprise/VDC/VApp or VM.
Why is this a problem? Currently, we are looking into a test fix for Interoute, and need to link a deploying VApp to entries in the metering table. As the id columns are not populated, we cannot go from the id straight to the VApp. This means that to uniquely identify the VApp we need the unique combination of Enterprise/VDC/VAPP names- which itself is not 100% reliable - but as some metering entries are written as 'Abiquo System' rather than the real Enterprise name we currently have no way of doing that, either :-( This means that metering entries for VDC/VApp names which are duplicated across Enterprises cannot be distinguished.
Finally, adding the ID columns may also help to fix the outstanding issue where metering entries are incorrectly reported against the wrong Enterprise/VDC. This is because the log filtering code could be altered to use the IDs to filter instead of the names...just a thought...