Bug 1546400

Summary: [RFE][Deployment] Add a way to configure reserved_huge_pages in OSP 10 and above
Product: Red Hat OpenStack Reporter: Andreas Karis <akaris>
Component: puppet-novaAssignee: Ollie Walsh <owalsh>
Status: CLOSED ERRATA QA Contact: Joe H. Rahme <jhakimra>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 10.0 (Newton)CC: akaris, awaugama, eglynn, fbaudin, jjoyce, jraju, jschluet, lyarwood, markmc, mbooth, owalsh, pablo.iranzo, skramaja, slinaber, tvignaud
Target Milestone: Upstream M2Keywords: FutureFeature, Triaged, ZStream
Target Release: 14.0 (Rocky)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: puppet-nova-13.1.1-0.20180709142740.fa5ce48.el7ost Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 1571820 (view as bug list) Environment:
Last Closed: 2019-01-11 11:48:46 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:
Bug Depends On:    
Bug Blocks: 1546403, 1571820, 1571825, 1571828, 1571833, 1696711, 1732839, 1800560, 1800677    

Description Andreas Karis 2018-02-16 23:51:08 UTC 
Description of problem:
For NFV deployments, users need to be able to configure DEFAULT/reserved_huge_pages in /etc/nova/nova.conf

E.g.:
~~~
[DEFAULT]
reserved_huge_pages=node:0,size:1GB,count:4
reserved_huge_pages=node:1,size:1GB,count:4
~~~

See https://access.redhat.com/solutions/3250441 for why this is needed.

See https://access.redhat.com/solutions/3356561 for a current workaround.

Thanks and kind regards,

Andreas
Comment 1 Sven Anderson 2018-02-23 17:14:37 UTC 
Would it be enough in this case (for OSP10) to just expose the setting to be manually set from tripleO/director? Or does this setting need to be automatically synchronized with other settings, like boot parameters of the kernel? The latter would not be feasible for OSP10, I guess. However, just exposing a way to set DEFAULT/reserved_huge_pages should be feasible though.
Comment 2 Saravanan KR 2018-02-26 05:59:40 UTC 
IMO, puppet-nova should apply the settings provided by templates, which will be either set by user (via DPDK environment file), as ovs requires those to be reserved in case of DPDK enabled OVS. I don't see a need to automatic synchronize for it. 

I am not sure what happens when hugepages is not enabled in the host but nova is configured with this reservation. If this validation to be performed, puppet-nova could ensure if huge-pages are enabled before applying it, else could fail the deployment.
Comment 13 errata-xmlrpc 2019-01-11 11:48:46 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