Merge "Documentation for bandwidth support"
This commit is contained in:
Zuul
Gerrit Code Review
commit
acbbc3eb8b
|
|
@ -286,4 +286,6 @@ pdf_documents = [
|
|||
|
||||
openstack_projects = [
|
||||
'nova',
|
||||
'neutron',
|
||||
'placement',
|
||||
]
|
||||
|
|
|
|||
|
|
@ -86,6 +86,7 @@ Contents
|
|||
polling_changes
|
||||
request_and_response_formats
|
||||
down_cells
|
||||
port_with_resource_request
|
||||
|
||||
.. toctree::
|
||||
:hidden:
|
||||
|
|
|
|||
|
|
@ -0,0 +1,26 @@
|
|||
=================================
|
||||
Using ports with resource request
|
||||
=================================
|
||||
|
||||
Starting from microversion 2.72 nova supports creating servers with neutron
|
||||
ports having resource request visible as a admin-only port attribute
|
||||
``resource_request``. For example a neutron port has resource request if it has
|
||||
a QoS minimum bandwidth rule attached. Deleting such servers or detaching such
|
||||
ports works since Stein version of nova without requiring any specific
|
||||
microversion.
|
||||
|
||||
However the following API operations are still not supported in nova:
|
||||
|
||||
* Creating servers with neutron networks having QoS minimum bandwidth rule is
|
||||
not supported. The user needs to pre-create the port in that neutron network
|
||||
and create the server with the pre-created port.
|
||||
|
||||
* Attaching Neutron ports and networks having QoS minimum bandwidth rule is not
|
||||
supported.
|
||||
|
||||
* Moving (resizing, migrating, live-migrating, evacuating, unshelving after
|
||||
shelve offload) servers with ports having resource request is not yet
|
||||
supported.
|
||||
|
||||
See :nova-doc:`the admin guide <admin/port_with_resource_request.html>` for
|
||||
administrative details.
|
||||
|
|
@ -30,3 +30,4 @@ instance for these kind of workloads.
|
|||
huge-pages
|
||||
virtual-gpu
|
||||
file-backed-memory
|
||||
port_with_resource_request
|
||||
|
|
|
|||
|
|
@ -0,0 +1,65 @@
|
|||
=================================
|
||||
Using ports with resource request
|
||||
=================================
|
||||
|
||||
Starting from microversion 2.72 nova supports creating servers with neutron
|
||||
ports having resource request visible as a admin-only port attribute
|
||||
``resource_request``. For example a neutron port has resource request if it has
|
||||
a QoS minimum bandwidth rule attached.
|
||||
|
||||
The :neutron-doc:`Quality of Service (QoS): Guaranteed Bandwidth <admin/config-qos-min-bw.html>`
|
||||
document describes how to configure neutron to use this feature.
|
||||
|
||||
Resource allocation
|
||||
~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Nova collects and combines the resource request from each port in a boot
|
||||
request and sends one allocation candidate request to placement during
|
||||
scheduling so placement will make sure that the resource request of the ports
|
||||
are fulfilled. At the end of the scheduling nova allocates one candidate in
|
||||
placement. Therefore the requested resources for each port from a single boot
|
||||
request will be allocated under the server's allocation in placement.
|
||||
|
||||
|
||||
Resource Group policy
|
||||
~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Nova represents the resource request of each neutron port as a separate
|
||||
:placement-doc:`Granular Resource Request group <usage/provider-tree.html#granular-resource-requests>`
|
||||
when querying placement for allocation candidates. When a server create request
|
||||
includes more than one port with resource requests then more than one group
|
||||
will be used in the allocation candidate query. In this case placement requires
|
||||
to define the ``group_policy``. Today it is only possible via the
|
||||
``group_policy`` key of the :nova-doc:`flavor extra_spec <user/flavors.html>`.
|
||||
The possible values are ``isolate`` and ``none``.
|
||||
|
||||
When the policy is set to ``isolate`` then each request group and therefore the
|
||||
resource request of each neutron port will be fulfilled from separate resource
|
||||
providers. In case of neutron ports with ``vnic_type=direct`` or
|
||||
``vnic_type=macvtap`` this means that each port will use a virtual function
|
||||
from different physical functions.
|
||||
|
||||
When the policy is set to ``none`` then the resource request of the neutron
|
||||
ports can be fulfilled from overlapping resource providers. In case of neutron
|
||||
ports with ``vnic_type=direct`` or ``vnic_type=macvtap`` this means the ports
|
||||
may use virtual functions from the same physical function.
|
||||
|
||||
For neutron ports with ``vnic_type=normal`` the group policy defines the
|
||||
collocation policy on OVS bridge level so ``group_policy=none`` is a reasonable
|
||||
default value in this case.
|
||||
|
||||
If the ``group_policy`` is missing from the flavor then the server create
|
||||
request will fail with 'No valid host was found' and a warning describing the
|
||||
missing policy will be logged.
|
||||
|
||||
Virt driver support
|
||||
~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Supporting neutron ports with ``vnic_type=direct`` or ``vnic_type=macvtap``
|
||||
depends on the capability of the virt driver. For the supported virt drivers
|
||||
see the :nova-doc:`Support matrix <user/support-matrix.html#operation_port_with_resource_request>`
|
||||
|
||||
If the virt driver on the compute host does not support the needed capability
|
||||
then the PCI claim will fail on the host and re-schedule will be triggered. It
|
||||
is suggested not to configure bandwidth inventory in the neutron agents on
|
||||
these compute hosts to avoid unnecessary reschedule.
|
||||
|
|
@ -1639,3 +1639,28 @@ driver.libvirt-vz-vm=missing
|
|||
driver.libvirt-vz-ct=missing
|
||||
driver.powervm=missing
|
||||
driver.zvm=missing
|
||||
|
||||
[operation.port-with-resource-request]
|
||||
title=SR-IOV ports with resource request
|
||||
status=optional
|
||||
notes=To support neutron SR-IOV ports (vnic_type=direct or vnic_type=macvtap)
|
||||
with resource request the virt driver needs to include the 'parent_ifname'
|
||||
key in each subdict which represents a VF under the 'pci_passthrough_devices'
|
||||
key in the dict returned from the ComputeDriver.get_available_resource()
|
||||
call.
|
||||
cli=nova boot --nic port-id <neutron port with resource request> ...
|
||||
driver.xenserver=missing
|
||||
driver.libvirt-kvm-x86=complete
|
||||
driver.libvirt-kvm-aarch64=missing
|
||||
driver.libvirt-kvm-ppc64=missing
|
||||
driver.libvirt-kvm-s390x=missing
|
||||
driver.libvirt-qemu-x86=complete
|
||||
driver.libvirt-lxc=missing
|
||||
driver.libvirt-xen=missing
|
||||
driver.vmware=missing
|
||||
driver.hyperv=missing
|
||||
driver.ironic=missing
|
||||
driver.libvirt-vz-vm=missing
|
||||
driver.libvirt-vz-ct=missing
|
||||
driver.powervm=missing
|
||||
driver.zvm=missing
|
||||
|
|
|
|||
Loading…
Reference in New Issue