On Tuesday, December 10, 2013 4:17:45 PM, Maithem Munshed 71510 wrote:
Hello, I was wondering, what is the reason behind having nova audit resources as opposed to using usage stats directly from what is reported by the compute driver. The available resources reported from the audit can be incorrect in some cases. Also, in many cases the reported usage stats from the driver are correct, so auditing periodically while having the usage stats from the driver is inefficient. One of the which result in an incorrect audit is: existing VMs on a hypervisor that are created prior to deploying nova. As a result, the scheduler will see more available resources than what actually is available. I am aware that Nova shouldn’t be managing VMs that it hasn’t created, but the reported available resources should be as accurate as possible. I have proposed the following blueprint to provide the option of using usage stats directly from the driver : https://blueprints.launchpad.net/nova/+spec/use-driver-usage-stats I would like to know what your thoughts are and would appreciate feedback. Regards, Maithem _______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
One (big) problem is the virt drivers don't follow a standard format for the usage diagnostics, which has been discussed before in the mailing list [1].
There is a nova blueprint [2] for standard auditing formats like in ceilometer which might be related to what you're looking for.
[1] http://lists.openstack.org/pipermail/openstack-dev/2013-October/016385.html [2] https://blueprints.launchpad.net/nova/+spec/support-standard-audit-formats
-- Thanks, Matt Riedemann _______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
