Hey Phil,
As Chris mentioned, I do have another review up:
https://review.openstack.org/#/c/9402/
The goal with that one is to more completely calculate all the capacity and
resource consumption information on the compute host than the current
capacity_notifier does. So, capacity-based
Hi Folks,
I was reviewing a code change to add generic retries for build failures (
https://review.openstack.org/#/c/9540/2 ), and wanted to be sure that it
wouldn't invalidate the capacity accounting used by the scheduler.
However I've been sitting here for a while working through the Folsom
Hi Phil,
The nova.db.api.compute_node_update() call is what the individual virt
drivers call to update the compute node stats. grep for that and you'll
see where the calls to set the compute node data are called.
Best,
-jay
On 07/13/2012 09:38 AM, Day, Phil wrote:
Hi Folks,
I was
+philip.day=hp@lists.launchpad.net [mailto:
openstack-bounces+philip.day=hp@lists.launchpad.net] On Behalf Of Jay
Pipes
Sent: 13 July 2012 17:36
To: openstack@lists.launchpad.net
Subject: Re: [Openstack] Capacity based scheduling: What updated
free_ram_mb in Folsom
Hi Phil
Capacity based scheduling currently adds up all instance usage in
host_manager.py
There's another review marked as WIP that will be ready when retries go in that
cleans that and the capacity tracking up. Look for it from Brian Elliott.
On Jul 13, 2012, at 6:38 AM, Day, Phil philip@hp.com
5 matches
Mail list logo
