Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1985506

Summary: Configure other_config:dpdk-socket-limit for OSP deployments with DPDK
Product: Red Hat OpenStack Reporter: Rosemarie O'Riorden <roriorde>
Component: tripleo-ansibleAssignee: Christophe Fontaine <cfontain>
Status: CLOSED EOL QA Contact: Joe H. Rahme <jhakimra>
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: apevec, cfields, cfontain, chrisw, dmarchan, hakhande, i.maximets, jschluet, oblaut, sbaker
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-10-10 12:23:24 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Rosemarie O'Riorden 2021-07-23 18:31:10 UTC 
Starting from the 2.17 release of OVS, a default value will no longer be provided for dpdk-socket-limit. 

This option will need to be configured if memory usage should be limited.
Comment 1 Ilya Maximets 2021-07-23 19:14:31 UTC 
Moving this to tripleo-ansible, since the implementation seems to belong there.
Feel free to change component to other modules if needed.

For the BZ itself, OpenStack will need to set dpdk-socket-limit equal to
dpdk-socket-mem in order to preserve current memory limiting behavior.
The dpdk-socket-limit configuration option is available since OVS 2.11.
See BZ 1949850 for details.
Comment 10 Steve Baker 2022-07-27 20:58:03 UTC 
Wallaby change has landed
Comment 13 Priscila Gutierres 2023-10-10 12:23:24 UTC 
Support has ended on 22 September 2023.