[openstack-dev] [nova] Configure overcommit policy

Alex Glikson GLIKSON at il.ibm.com
Tue Nov 12 14:54:02 UTC 2013

You can consider having a separate host aggregate for Hadoop, and use a 
combination of AggregateInstanceExtraSpecFilter (with a special flavor 
mapped to this host aggregate) and AggregateCoreFilter (overriding 
cpu_allocation_ratio for this host aggregate to be 1).


From:   John Garbutt <john at johngarbutt.com>
To:     "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev at lists.openstack.org>, 
Date:   12/11/2013 04:41 PM
Subject:        Re: [openstack-dev] [nova] Configure overcommit policy

On 11 November 2013 12:04, Alexander Kuznetsov <akuznetsov at mirantis.com> 
> Hi all,
> While studying Hadoop performance in a virtual environment, I found an
> interesting problem with Nova scheduling. In OpenStack cluster, we have
> overcommit policy, allowing to put on one compute more vms than 
> available for them. While it might be suitable for general types of
> workload, this is definitely not the case for Hadoop clusters, which 
> consume 100% of system resources.
> Is there any way to tell Nova to schedule specific instances (the ones 
> consume 100% of system resources) without overcommitting resources on
> compute node?

You could have a flavor with "no-overcommit" extra spec, and modify
the over-commit calculation in the scheduler on that case, but I don't
remember seeing that in there.


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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131112/684a03d0/attachment.html>

More information about the OpenStack-dev mailing list