[openstack-dev] [nova][scheduler][metrics] Additional metrics

Murray, Paul (HP Cloud Services) pmurray at hp.com
Fri Nov 29 16:34:32 UTC 2013

Hi Abbass, 

I am in the process of coding some of this now - take a look at 

https://blueprints.launchpad.net/nova/+spec/extensible-resource-tracking - now has a specification document attached 
https://etherpad.openstack.org/p/IcehouseNovaExtensibleSchedulerMetrics - the design summit session on this topic

see what you think and feel free to comment - I think it covers exactly what you describe.


Paul Murray
HP Cloud Services
+44 117 312 9309

Hewlett-Packard Limited registered Office: Cain Road, Bracknell, Berks RG12 1HN Registered No: 690597 England. The contents of this message and any attachments to it are confidential and may be legally privileged. If you have received this message in error, you should delete it from your system immediately and advise the sender. To any recipient of this message within HP, unless otherwise stated you should consider this message and attachments as "HP CONFIDENTIAL".

-----Original Message-----
From: Lu, Lianhao [mailto:lianhao.lu at intel.com] 
Sent: 22 November 2013 02:03
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova][scheduler][metrics] Additional metrics

Abbass MAROUNI wrote on 2013-11-21:
> Hello,
> I'm in the process of writing a new scheduling algorithm for openstack nova.
> I have a set of compute nodes that I'm going to filter and weigh according to some metrics collected from these compute nodes.
> I saw nova.compute.resource_tracker and metrics (ram, disk and cpu) 
> that it collects from compute nodes and updates the rows corresponding to compute nodes in the database.
> I'm planning to write some modules that will collect the new metrics 
> but I'm wondering if I need to modify the database schema by adding 
> more columns in the 'compute_nodes' table for my new metrics. Will 
> this require some modification to the compute model ? Then how can I use these metrics during the scheduling process, do I fetch each compute node row from the database ? Is there any easier way around this problem ?
> Best Regards,

There are currently some effort on this:

- Lianhao

OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org

More information about the OpenStack-dev mailing list