cadd25e9bc
Import the following documents from the admin guide [1]: - cli-manage-flavors.rst - cli-nova-evacuate.rst - cli-nova-manage-projects-security.rst - cli-nova-manage-services.rst - cli-nova-numa-libvirt.rst - cli-nova-specify-host.rst - cli-set-quotas.rst - cli-set-compute-quotas.rst - cli-os-migrate.rst - cli-os-migrate-cfg-ssh.rst - ts-no-emulator-x86-64.rst - ts-multipath-warn.rst - ts-failed-connect-vol-FC-SAN.rst - ts-failed-attach-vol-no-sysfsutils.rst - ts-failed-attach-vol-after-detach.rst - ts-vol-attach-miss-sg-scan.rst These were missed in the original import [2]. All 'ts-' files are merged into a single 'support-compute' document, which is already in-tree. [1] https://github.com/openstack/openstack-manuals/tree/stable/ocata/doc/admin-guide/source [2] https://review.openstack.org/#/c/477497/ Change-Id: Ifa0039e270e54ea2fb58ab18ce6724e5e8e061a1 Closes-Bug: #1708666
27 lines
1.3 KiB
ReStructuredText
27 lines
1.3 KiB
ReStructuredText
=============================================
|
|
Consider NUMA topology when booting instances
|
|
=============================================
|
|
|
|
.. todo:: Merge this into 'cpu-topologies.rst'
|
|
|
|
NUMA topology can exist on both the physical hardware of the host, and the
|
|
virtual hardware of the instance. OpenStack Compute uses libvirt to tune
|
|
instances to take advantage of NUMA topologies. The libvirt driver boot
|
|
process looks at the NUMA topology field of both the instance and the host it
|
|
is being booted on, and uses that information to generate an appropriate
|
|
configuration.
|
|
|
|
If the host is NUMA capable, but the instance has not requested a NUMA
|
|
topology, Compute attempts to pack the instance into a single cell.
|
|
If this fails, though, Compute will not continue to try.
|
|
|
|
If the host is NUMA capable, and the instance has requested a specific NUMA
|
|
topology, Compute will try to pin the vCPUs of different NUMA cells
|
|
on the instance to the corresponding NUMA cells on the host. It will also
|
|
expose the NUMA topology of the instance to the guest OS.
|
|
|
|
If you want Compute to pin a particular vCPU as part of this process,
|
|
set the ``vcpu_pin_set`` parameter in the ``nova.conf`` configuration
|
|
file. For more information about the ``vcpu_pin_set`` parameter, see the
|
|
Configuration Reference Guide.
|