openstack/openstack-manuals
Code Issues Proposed changes

Merge "Clarify effect of cpu_allocation_ratio setting"

Browse Source
This commit is contained in:
Jenkins 2014-03-04 14:37:05 +00:00 committed by Gerrit Code Review
commit b8a94b3efa
1 changed files with 12 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
doc/config-reference/compute/section_compute-scheduler.xml
View File

@ -199,7 +199,7 @@ scheduler_available_filters=myfilter.MyFilter</programlisting>
instance may exceed the physical cores).</para> instance may exceed the physical cores).</para>
<para>This filter can be configured to allow a fixed <para>This filter can be configured to allow a fixed
amount of vCPU overcommitment by using the amount of vCPU overcommitment by using the
<literal>cpu_allocation_ratio</literal> <option>cpu_allocation_ratio</option>
Configuration option in Configuration option in
<filename>nova.conf</filename>. The default setting <filename>nova.conf</filename>. The default setting
is:</para> is:</para>
@ -209,6 +209,17 @@ scheduler_available_filters=myfilter.MyFilter</programlisting>
that node.</para> that node.</para>
<para>To disallow vCPU overcommitment set:</para> <para>To disallow vCPU overcommitment set:</para>
<programlisting language="ini">cpu_allocation_ratio=1.0</programlisting> <programlisting language="ini">cpu_allocation_ratio=1.0</programlisting>
<note>
<para>
The Compute API will always return the actual number of CPU
cores available on a compute node regardless of the value of
the <option>cpu_allocation_ratio</option> configuration key. As
a result changes to the <option>cpu_allocation_ratio</option>
are not reflected via the command line clients or the
dashboard. Changes to this configuration key are only taken
into account internally in the scheduler.
</para>
</note>
</section> </section>
<section xml:id="differenthostfilter"> <section xml:id="differenthostfilter">
<title>DifferentHostFilter</title> <title>DifferentHostFilter</title>