35 lines
1.9 KiB
XML
35 lines
1.9 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<section xmlns="http://docbook.org/ns/docbook"
|
|
xmlns:xi="http://www.w3.org/2001/XInclude"
|
|
xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0"
|
|
xml:id="specify-host-to-boot-instances-on">
|
|
<title>Select a specific host to boot instances on</title>
|
|
<para>If you have the appropriate permissions, you can select the specific host where the
|
|
instance will be launched. This is done using the <literal>--availability_zone
|
|
<replaceable>zone</replaceable>:<replaceable>host</replaceable></literal>
|
|
arguments to the <command>nova boot</command> command. For example:</para>
|
|
<para>
|
|
<screen><prompt>$</prompt> <userinput>nova boot --image <uuid> --flavor m1.tiny --key_name test --availability-zone nova:server2</userinput></screen>
|
|
</para>
|
|
<para>Starting with the Grizzly release, you can specify which roles are permitted to boot
|
|
an instance to a specific host with the <literal>create:forced_host</literal> setting
|
|
within <filename>policy.json</filename> on the desired roles. By default, only the admin
|
|
role has this setting enabled.</para>
|
|
<para>You can view the list of valid compute hosts by using the <command>nova
|
|
hypervisor-list</command> command, for
|
|
example:<screen><prompt>$</prompt> <userinput>nova hypervisor-list</userinput>
|
|
<computeroutput>+----+---------------------+
|
|
| ID | Hypervisor hostname |
|
|
+----+---------------------+
|
|
| 1 | server2 |
|
|
| 2 | server3 |
|
|
| 3 | server4 |
|
|
+----+---------------------+</computeroutput></screen></para>
|
|
<note>
|
|
<para>The <literal>--availability_zone
|
|
<replaceable>zone</replaceable>:<replaceable>host</replaceable></literal>
|
|
flag replaced the <literal>--force_hosts</literal> scheduler hint for specifying a
|
|
specific host, starting with the Folsom release.</para>
|
|
</note>
|
|
</section>
|