Bug 1383244

Summary:	[RFE] Mechanism to configure kernel boot parameters for the baremetal nodes
Product:	Red Hat OpenStack	Reporter:	Anil Dhingra <adhingra>
Component:	openstack-ironic	Assignee:	Yolanda Robla <yroblamo>
Status:	CLOSED WONTFIX	QA Contact:	mlammon
Severity:	high	Docs Contact:
Priority:	high
Version:	12.0 (Pike)	CC:	akarlsso, dtantsur, fbaudin, mburns, mlammon, pweeks, racedoro, srevivo, yrachman, yroblamo
Target Milestone:	---	Keywords:	FutureFeature, Triaged, ZStream
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:	2021-08-17 19:39:22 UTC	Type:	Feature Request
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:	1472360
Bug Blocks:	1235009, 1281573, 1419948

Description Anil Dhingra 2016-10-10 09:43:16 UTC

Description of problem:
The performance of the compute node is highly critical especially for hosting
VNFs. To obtain optimum performance, features like DPDK and SR-IOV are
critical. These features require CPU pinning and huge page features, which has
to be specified as kernel arguments in the bootloader, in case of local boot.
Today, enabling of these features are done manually, post the cluster
installation, by configuring CPU pinning and enabling hugepages.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
addion of pxe_append_params with parameters like - 'isolcpus=1-7', 'intel_immou=on' doesn't work 

Expected results:

A list of boot parameters shall be provided to ironic, which shall be applied
to the nodes during the node deploy process. Ironic shall store the boot
parameters in the DB. In case of local boot, the boot parameters shall be
applied to the node at the time of installing bootloader by IPA. In case of
netboot (pxe), the boot parameters shall be added to the pxe config file
generated by ironic. And the boot parameters passed during the deploy process
shall override ``pxe_append_params`` specified via ironic.conf file.

Additional info:
https://review.openstack.org/#/c/331564/11/specs/approved/boot-params.rst

Comment 1 Yolanda Robla 2017-01-11 10:19:30 UTC

This could be solved with the custom deployment steps spec:

https://review.openstack.org/412523

Comment 6 Dmitry Tantsur 2017-10-23 09:12:23 UTC

We plan on using the ansible deploy interface (https://bugzilla.redhat.com/show_bug.cgi?id=1479814) to enable this kind of customizations.

Comment 7 Yariv 2018-01-04 13:45:39 UTC

(In reply to Dmitry Tantsur from comment #6)
> We plan on using the ansible deploy interface
> (https://bugzilla.redhat.com/show_bug.cgi?id=1479814) to enable this kind of
> customizations.

But this one is for Rockie,
Real Time custom role is ready for 13, but there is a need to prepare RHEL RT for overcloud RT compute image?

Any suggestion? RT KVM will be fully supported in 13

Comment 8 Dmitry Tantsur 2018-01-04 14:25:53 UTC

Correcting the link - https://bugzilla.redhat.com/show_bug.cgi?id=1472360 is about undercloud. The alternatives are to use whole-disk images with boot parameters pre-baked or to use a firstboot script.

Comment 14 pweeks 2021-08-17 19:39:22 UTC

whole-disk images is landing in 17 which might satisfy someof these requirements.
given a significant reduction in capacity within the team and age of this RFE, closing wontfix
please open a new rfe with updated requirements should there remain a customer need for future features