starlingx/docs
Code Issues Proposed changes

Merge "Add additional config info for vswitch"

Browse Source
This commit is contained in:
Zuul 2020-01-10 18:14:45 +00:00 committed by Gerrit Code Review
commit 70e0f89220
2 changed files with 66 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

36
doc/source/deploy_install_guides/r3_release/bare_metal/aio_simplex_install_kubernetes.rst
View File

@ -268,7 +268,9 @@ OpenStack-specific host configuration
manifest. manifest.
* Shares the core(s) assigned to the platform. * Shares the core(s) assigned to the platform.
If you require better performance, OVS-DPDK should be used: If you require better performance, OVS-DPDK (OVS with the Data Plane
Development Kit, which is supported only on bare metal hardware) should be
used:
* Runs directly on the host (it is not containerized). * Runs directly on the host (it is not containerized).
* Requires that at least 1 core be assigned/dedicated to the vSwitch function. * Requires that at least 1 core be assigned/dedicated to the vSwitch function.
@ -282,8 +284,7 @@ OpenStack-specific host configuration
Do not run any vSwitch directly on the host, instead, use the containerized Do not run any vSwitch directly on the host, instead, use the containerized
OVS defined in the helm charts of stx-openstack manifest. OVS defined in the helm charts of stx-openstack manifest.
To deploy OVS-DPDK (OVS with the Data Plane Development Kit, which is To deploy OVS-DPDK, run the following command:
supported only on bare metal hardware), run the following command:
:: ::
@ -294,8 +295,33 @@ OpenStack-specific host configuration
default to automatically assigning 1 vSwitch core for AIO controllers and 2 default to automatically assigning 1 vSwitch core for AIO controllers and 2
vSwitch cores for computes. vSwitch cores for computes.
When using OVS-DPDK, virtual machines must be configured to use a flavor with When using OVS-DPDK, configure vSwitch memory per NUMA node with the following
property: hw:mem_page_size=large command:
::
system host-memory-modify -f <function> -1G <1G hugepages number> <hostname or id> <processor>
For example:
::
system host-memory-modify -f vswitch -1G 1 compute-0 0
VMs created in an OVS-DPDK environment must be configured to use huge pages
to enable networking and must use a flavor with property: hw:mem_page_size=large
Configure the huge pages for VMs in an OVS-DPDK environment with the command:
::
system host-memory-modify -1G <1G hugepages number> <hostname or id> <processor>
For example:
::
system host-memory-modify compute-0 0 -1G 10
.. note:: .. note::

44
doc/source/deploy_install_guides/r3_release/bare_metal/controller_storage_install_kubernetes.rst
View File

@ -217,7 +217,9 @@ OpenStack-specific host configuration
manifest. manifest.
* Shares the core(s) assigned to the platform. * Shares the core(s) assigned to the platform.
If you require better performance, OVS-DPDK should be used: If you require better performance, OVS-DPDK (OVS with the Data Plane
Development Kit, which is supported only on bare metal hardware) should be
used:
* Runs directly on the host (it is not containerized). * Runs directly on the host (it is not containerized).
* Requires that at least 1 core be assigned/dedicated to the vSwitch function. * Requires that at least 1 core be assigned/dedicated to the vSwitch function.
@ -231,26 +233,50 @@ OpenStack-specific host configuration
Do not run any vSwitch directly on the host, instead, use the containerized Do not run any vSwitch directly on the host, instead, use the containerized
OVS defined in the helm charts of stx-openstack manifest. OVS defined in the helm charts of stx-openstack manifest.
To deploy OVS-DPDK (OVS with the Data Plane Development Kit, which is To deploy OVS-DPDK, run the following command:
supported only on bare metal hardware), run the following command:
:: ::
system modify --vswitch_type ovs-dpdk system modify --vswitch_type ovs-dpdk
system host-cpu-modify -f vswitch -p0 1 controller-0 system host-cpu-modify -f vswitch -p0 1 controller-0
Once vswitch_type is set to OVS-DPDK, any subsequent nodes created will Once vswitch_type is set to OVS-DPDK, any subsequent nodes created will
default to automatically assigning 1 vSwitch core for AIO controllers and 2 default to automatically assigning 1 vSwitch core for AIO controllers and 2
vSwitch cores for computes. vSwitch cores for computes.
When using OVS-DPDK, Virtual Machines must be configured to use a flavor with When using OVS-DPDK, configure vSwitch memory per NUMA node with the following
property: hw:mem_page_size=large. command:
::
system host-memory-modify -f <function> -1G <1G hugepages number> <hostname or id> <processor>
For example:
::
system host-memory-modify -f vswitch -1G 1 compute-0 0
VMs created in an OVS-DPDK environment must be configured to use huge pages
to enable networking and must use a flavor with property: hw:mem_page_size=large
Configure the huge pages for VMs in an OVS-DPDK environment with the command:
::
system host-memory-modify -1G <1G hugepages number> <hostname or id> <processor>
For example:
::
system host-memory-modify compute-0 0 -1G 10
.. note:: .. note::
After controller-0 is unlocked, changing vswitch_type requires After controller-0 is unlocked, changing vswitch_type requires
locking and unlocking all computes (and/or AIO controllers) to locking and unlocking all computes (and/or AIO Controllers) to
apply the change. apply the change.
.. incl-config-controller-0-storage-end: .. incl-config-controller-0-storage-end: