Re: [openstack-dev] [nova] Resource tracker

2014-10-07 Thread Daniel P. Berrange
On Mon, Oct 06, 2014 at 02:55:20PM -0700, Joe Gordon wrote: On Mon, Oct 6, 2014 at 6:03 AM, Gary Kotton gkot...@vmware.com wrote: Hi, At the moment the resource tracker in Nova ignores that statistics that are returned by the hypervisor and it calculates the values on its own. Not only

Re: [openstack-dev] [nova] Resource tracker

2014-10-07 Thread Vishvananda Ishaya
On Oct 7, 2014, at 6:21 AM, Daniel P. Berrange berra...@redhat.com wrote: On Mon, Oct 06, 2014 at 02:55:20PM -0700, Joe Gordon wrote: On Mon, Oct 6, 2014 at 6:03 AM, Gary Kotton gkot...@vmware.com wrote: Hi, At the moment the resource tracker in Nova ignores that statistics that are

Re: [openstack-dev] [nova] Resource tracker

2014-10-07 Thread Joe Gordon
On Tue, Oct 7, 2014 at 10:56 AM, Vishvananda Ishaya vishvana...@gmail.com wrote: On Oct 7, 2014, at 6:21 AM, Daniel P. Berrange berra...@redhat.com wrote: On Mon, Oct 06, 2014 at 02:55:20PM -0700, Joe Gordon wrote: On Mon, Oct 6, 2014 at 6:03 AM, Gary Kotton gkot...@vmware.com wrote:

[openstack-dev] [nova] Resource tracker

2014-10-06 Thread Gary Kotton
Hi, At the moment the resource tracker in Nova ignores that statistics that are returned by the hypervisor and it calculates the values on its own. Not only is this highly error prone but it is also very costly - all of the resources on the host are read from the database. Not only the fact

Re: [openstack-dev] [nova] Resource tracker

2014-10-06 Thread Daniel P. Berrange
On Mon, Oct 06, 2014 at 01:03:01PM +, Gary Kotton wrote: Hi, At the moment the resource tracker in Nova ignores that statistics that are returned by the hypervisor and it calculates the values on its own. Not only is this highly error prone but it is also very costly - all of the

Re: [openstack-dev] [nova] Resource tracker

2014-10-06 Thread Joe Gordon
On Mon, Oct 6, 2014 at 6:03 AM, Gary Kotton gkot...@vmware.com wrote: Hi, At the moment the resource tracker in Nova ignores that statistics that are returned by the hypervisor and it calculates the values on its own. Not only is this highly error prone but it is also very costly – all of