openstack/training-guides
Code Issues Proposed changes

Merge "cleaned up training docs module001-ch009-vm-placement"

Browse Source
This commit is contained in:
Jenkins 2014-01-22 09:01:51 +00:00 committed by Gerrit Code Review
commit 5e539fbae6
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
module001-ch009-vm-placement.xml
View File

@ -8,7 +8,7 @@
<para>Compute uses the nova-scheduler service to determine how to
dispatch compute and volume requests. For example, the
nova-scheduler service determines which host a VM should launch
on. The term hostin the context of filters means a physical node
on. The term host in the context of filters means a physical node
that has a nova-compute service running on it. You can configure
the scheduler through a variety of options.</para>
<figure>
@ -59,7 +59,7 @@
</imageobject>
</mediaobject>
</figure>
<para>During its work Filter Scheduler firstly makes dictionary
<para>During its work, Filter Scheduler first makes a dictionary
of unfiltered hosts, then filters them using filter properties
and finally chooses hosts for the requested number of
instances (each time it chooses the most weighed host and
@ -102,7 +102,7 @@
format is scope:key and can be nested, i.e. key_string :=
scope:key_string. Example like capabilities:cpu_info:
features is valid scope format. A key string without any :
is non-scope format. Each filter defines it’s valid scope,
is non-scope format. Each filter defines its valid scope,
and not all filters accept non-scope format.</para>
</listitem>
<listitem>
@ -178,7 +178,7 @@
same that the host has.</para>
<para><guilabel>Weights</guilabel></para>
<para>Filter Scheduler uses so-called weightsduring its
<para>Filter Scheduler uses so-called weights during its
work.</para>
<para>The Filter Scheduler weights hosts based on the config
option scheduler_weight_classes, this defaults to
@ -189,7 +189,7 @@
repeated filtering and weighing. Each time it chooses a host, it
virtually consumes resources on it, so subsequent selections can
adjust accordingly. It is useful if the customer asks for the
some large amount of instances, because weight is computed for
same large amount of instances, because weight is computed for
each instance requested.</para>
<figure>
<title>Weights</title>