Bug 1617927 - [OSP14] RX/TX Queue Size is missing THT parameters
Summary: [OSP14] RX/TX Queue Size is missing THT parameters
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 14.0 (Rocky)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: beta
: 14.0 (Rocky)
Assignee: Martin Schuppert
QA Contact: Gurenko Alex
URL:
Whiteboard:
Depends On:
Blocks: 1619104 1623553 1623554
TreeView+ depends on / blocked
 
Reported: 2018-08-16 07:31 UTC by Maxim Babushkin
Modified: 2019-01-11 11:51 UTC (History)
13 users (show)

Fixed In Version: openstack-tripleo-heat-templates-9.0.0-0.20180919080946.0rc1.0rc1.el7ost
Doc Type: Bug Fix
Doc Text:
In prior releases, you could set RX/TX queue size via nova::compute::libvirt::rx_queue_size/nova::compute::libvirt::tx_queue_size. However, there was no dedicated TripleO heat template parameter. With this release, the RX/TX queue size can be set on a role base like this: parameter_defaults: ComputeParameters: NovaLibvirtRxQueueSize: 1024 NovaLibvirtTxQueueSize: 1024 The result is rx_queue_size/tx_queue_size is set using new parameters.
Clone Of:
: 1619104 (view as bug list)
Environment:
Last Closed: 2019-01-11 11:51:21 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 592458 0 None MERGED Add role parameter for rx/tx virtio-net queue size 2020-12-14 17:53:51 UTC
Red Hat Product Errata RHEA-2019:0045 0 None None None 2019-01-11 11:51:42 UTC

Description Maxim Babushkin 2018-08-16 07:31:32 UTC
Description of problem:
RX/TX Queue size implemented in RHOSP 14 according to the following BZ [1] [2], missing THT parameters.

[1] - https://bugzilla.redhat.com/show_bug.cgi?id=1553088
[2] - https://bugzilla.redhat.com/show_bug.cgi?id=1512941

THT parameters should configure rx_queue_size and tx_queue_size in nova.conf
[libvirt]
rx_queue_size=1024
tx_queue_size=1024

Comment 2 Martin Schuppert 2018-08-20 10:48:02 UTC
With https://review.openstack.org/#/c/592458/ we now have the following role parameters, e.g.:

parameter_defaults:
  ComputeParameters:
    NovaLibvirtRxQueueSize: 1024
    NovaLibvirtTxQueueSize: 1024

Comment 5 Yariv 2018-08-21 20:26:38 UTC
We expect THT parameters as all DPDK/NOVA parameters
such as:

NovaRxQueueSize: 1024
NovaTxQueueSize: 1024


ComputeOvsDpdkParameters:
    KernelArgs: "default_hugepagesz=1GB hugepagesz=1G hugepages=32 iommu=pt intel_iommu=on isolcpus=2-19,22-39"
    TunedProfileName: "cpu-partitioning"
    IsolCpusList: "2-19,22-39"
    NovaVcpuPinSet: ['4-19,24-39']
    NovaReservedHostMemory: 4096
    OvsDpdkSocketMemory: "4096,4096"
    OvsDpdkMemoryChannels: "4"
    OvsDpdkCoreList: "0,20,1,21"
    OvsPmdCoreList: "2,22,3,23"
    NovaComputeCpuSharedSet: [0,20,1,21]

ComputeSriovParameters:
    KernelArgs: "default_hugepagesz=1GB hugepagesz=1G hugepages=32 iommu=pt intel_iommu=on isolcpus=2-19,22-39"
    TunedProfileName: "cpu-partitioning"
    IsolCpusList: "2-19,22-39"
    NovaVcpuPinSet: ['4-19,24-39']
    NovaReservedHostMemory: 4096

Comment 6 Maxim Babushkin 2018-08-22 07:38:11 UTC
Chris, please, ignore Yariv's need info.

Comment 10 Joe H. Rahme 2018-10-17 13:55:18 UTC
Verified with the following THT parameters:


parameter_defaults:
  ComputeParameters:
    NovaLibvirtRxQueueSize: 1024
    NovaLibvirtTxQueueSize: 1024

Deployed successfully with the correct info in nova.conf:

[heat-admin@compute-0 ~]$ sudo docker exec nova_libvirt grep -i rx /etc/nova/nova.conf
# Configure virtio rx queue size.
#rx_queue_size=<None>
rx_queue_size=1024

Comment 14 errata-xmlrpc 2019-01-11 11:51:21 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2019:0045


Note You need to log in before you can comment on or make changes to this bug.