Oversubscription of cores in compute nodes

Asked by Diego Parrilla

Hi all openstackers,

I have been playing a bit with the information stored in the 'compute_nodes' table, trying to cheat Nova about the number of virtual cores available in the compute nodes. It seems that this table is not read by the scheduler, instead, the scheduler only computes the values retrieved from the compute nodes directly.

Basically my goal is to oversubscribe the number of cores of the compute nodes. I'm using KVM and I would like to decide how many virtual cores are available in each node. I have read about the get_hosts_stats() and the periodic_tasks(), but I was wondering if there is a way to manually configure the number of virtual cores per node and avoid rewriting this function.

Example: My server says it has 16 cores, but I want to implement an oversubscription ratio of 1:4, obtaining 64 virtual cores that will operate in a range of Mhz depending on how busy the real cores are.

Regards
Diego

Question information

Language:
English Edit question
Status:
Answered
For:
OpenStack Compute (nova) Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Vish Ishaya (vishvananda) said :
#1

If you are using simple scheduler, you can just up the --max_cores flag on the scheduler host.

Vish

On May 31, 2011, at 3:45 AM, Diego Parrilla wrote:

> New question #159723 on OpenStack Compute (nova):
> https://answers.launchpad.net/nova/+question/159723
>
> Hi all openstackers,
>
> I have been playing a bit with the information stored in the 'compute_nodes' table, trying to cheat Nova about the number of virtual cores available in the compute nodes. It seems that this table is not read by the scheduler, instead, the scheduler only computes the values retrieved from the compute nodes directly.
>
> Basically my goal is to oversubscribe the number of cores of the compute nodes. I'm using KVM and I would like to decide how many virtual cores are available in each node. I have read about the get_hosts_stats() and the periodic_tasks(), but I was wondering if there is a way to manually configure the number of virtual cores per node and about rewriting this function.
>
> Example: My server says it has 16 cores, but I want to implement an oversubscription ratio of 1:4, obtaining 64 virtual cores that will operate in a range of Mhz depending on how busy the real cores are.
>
> Regards
> Diego
>
> --
> You received this question notification because you are a member of Nova
> Core, which is an answer contact for OpenStack Compute (nova).

Can you help with this problem?

Provide an answer of your own, or ask Diego Parrilla for more information if necessary.

To post a message you must log in.