
This is reverted according to updated documentation contributor guide. For reference http://docs.openstack.org/contributor-guide/rst-conv/source-code.html This reverts commit 2c69f6f387b2f59c4199fae7b70bc691e1793bdf. Change-Id: Ied74704fe4ff36497039a01b8a140930fd209d60
1.1 KiB
1.1 KiB
Select hosts where instances are launched
With the appropriate permissions, you can select which host instances are launched on and which roles can boot instances on this host.
To select the host where instances are launched, use the
--availability_zone ZONE:HOST
parameter on thenova boot
command.For example:
$ nova boot --image <uuid> --flavor m1.tiny --key_name test --availability-zone nova:server2
To specify which roles can launch an instance on a specified host, enable the
create:forced_host
option in thepolicy.json
file. By default, this option is enabled for only the admin role.To view the list of valid compute hosts, use the
nova hypervisor-list
command.$ nova hypervisor-list +----+---------------------+ | ID | Hypervisor hostname | +----+---------------------+ | 1 | server2 | | 2 | server3 | | 3 | server4 | +----+---------------------+