Merge "Correct host aggregate and availability zone info"
This commit is contained in:
@@ -8,18 +8,31 @@
|
|||||||
xmlns:xlink="http://www.w3.org/1999/xlink"
|
xmlns:xlink="http://www.w3.org/1999/xlink"
|
||||||
version="5.0"
|
version="5.0"
|
||||||
xml:id="host-aggregates">
|
xml:id="host-aggregates">
|
||||||
<title>Host aggregates</title>
|
<title>Host aggregates and availability zones</title>
|
||||||
<para>Host aggregates are a mechanism to further partition an
|
<para>
|
||||||
availability zone; while availability zones are visible to
|
Host aggregates are a mechanism for partitioning hosts in an OpenStack
|
||||||
users, host aggregates are only visible to administrators.
|
cloud, or a region of an OpenStack cloud, based on arbitrary
|
||||||
Host Aggregates provide a mechanism to allow administrators to
|
characteristics. Examples where an administrator may want to do this
|
||||||
assign key-value pairs to groups of machines. Each node can
|
include where a group of hosts have additional hardware or performance
|
||||||
have multiple aggregates, each aggregate can have multiple
|
characteristics.
|
||||||
key-value pairs, and the same key-value pair can be assigned
|
</para>
|
||||||
to multiple aggregates. This information can be used in the
|
<para>
|
||||||
scheduler to enable advanced scheduling, to set up hypervisor
|
Host aggregates are not explicitly exposed to users.
|
||||||
resource pools or to define logical groups for
|
Instead administrators map flavors to host aggregates. Administrators
|
||||||
migration.</para>
|
do this by setting metadata on a host aggregate, and matching flavor
|
||||||
|
extra specifications. The scheduler then endeavors to match user
|
||||||
|
requests for instance of the given flavor to a host aggregate with the
|
||||||
|
same key-value pair in its metadata. Compute nodes can be in more than
|
||||||
|
one host aggregate.
|
||||||
|
</para>
|
||||||
|
<para>
|
||||||
|
Administrators are able to optionally expose a host aggregate as an
|
||||||
|
availability zone. Availability zones are different to host aggregates
|
||||||
|
in that they are explicitly exposed to the user, and hosts can only be
|
||||||
|
in a single availability zone. Administrators can configure a default
|
||||||
|
availability zone where instances will be scheduled when the user
|
||||||
|
fails to specify one.
|
||||||
|
</para>
|
||||||
<simplesect>
|
<simplesect>
|
||||||
<title>Command-line interface</title>
|
<title>Command-line interface</title>
|
||||||
<para>The <command>nova</command> command-line tool supports
|
<para>The <command>nova</command> command-line tool supports
|
||||||
@@ -34,19 +47,18 @@
|
|||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><command>nova aggregate-create
|
<term><command>nova aggregate-create
|
||||||
<replaceable><name></replaceable>
|
<replaceable><name></replaceable>
|
||||||
<replaceable><availability-zone></replaceable></command></term>
|
<replaceable>[availability-zone]</replaceable></command></term>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>Create a new aggregate named
|
<para>Create a new aggregate named
|
||||||
<replaceable><name></replaceable>
|
<replaceable><name></replaceable>, and
|
||||||
in availability zone
|
optionally in availability zone
|
||||||
<replaceable><availability-zone></replaceable>.
|
<replaceable>[availability-zone]</replaceable>
|
||||||
Returns the ID of the newly created
|
if specified. The command returns the ID of the
|
||||||
aggregate. Hosts can be made available to
|
newly created aggregate. Hosts can be made
|
||||||
multiple availability zones, but
|
available to multiple host aggregates. Be careful
|
||||||
administrators should be careful when
|
when adding a host to an additional host
|
||||||
adding the host to a different host
|
aggregate when the host is also in an availability
|
||||||
aggregate within the same availability
|
zone. Pay attention when using the
|
||||||
zone and pay attention when using the
|
|
||||||
<command>aggregate-set-metadata</command>
|
<command>aggregate-set-metadata</command>
|
||||||
and <command>aggregate-update</command>
|
and <command>aggregate-update</command>
|
||||||
commands to avoid user confusion when they
|
commands to avoid user confusion when they
|
||||||
|
Reference in New Issue
Block a user