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
This could be solved with the custom deployment steps spec: https://review.openstack.org/412523
We plan on using the ansible deploy interface (https://bugzilla.redhat.com/show_bug.cgi?id=1479814) to enable this kind of customizations.
(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
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.
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