[RFE] provide a mechanism to configure kernel boot parameters

[Saravanan KR]

On deploying a cluster using tripleo, for using features like, DPDK and SR-IOV, it is required to enable CPU pinning and configure huge pages on the overcloud nodes to provide better performance. The boot loader for the overcloud nodes are configured via ironic-python-agent. Ironic should provide the given parameters to ironic-python-client to configure the boot parameters.

Nova has a spec [1] approved, to add boot parameters as part of the nova boot command. This spec is specific to virt, it has to be enhanced to pass on this parameter to ironic in case of baremetal.

The changes proposed are,
* ironic pythonclient to take the boot parameters from nova
* ironic to obtain the boot parameters
* ironic has to pass the parameters to ironic-python-agent at install bootloader step
* ironic-python-agent to write the passed boot params in the boot loader

[1] https://blueprints.launchpad.net/nova/+spec/virt-image-props-boot-override

[Dmitry Tantsur (divius)]

So as far as I understand the Nova spec, we should start reading the hw_os_command_line property from Nova image properties. Note that this work in Ironic does NOT depend on the Nova spec in question.

[Saravanan KR (skramaja)]

Agreed that, the ironic work does not depend on nova spec.

The nova spec is about adding a new parameter "image_props_override" for nova boot API/command, which provides a mechanism to override the image properties dynamically. Nova spec is specific for virt images. We are also looking on how to provide boot parameters for baremetal in nova.

[Jim Rollenhagen (jim-rollenhagen)]

This will need a spec, as it affects deploy options, agent communication, bootloader install, etc.

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: master
Review: https://review.openstack.org/331564

[Saravanan KR (skramaja)]

IPA Review: https://review.openstack.org/#/c/335052/
Ironic Review: https://review.openstack.org/#/c/339977/

[OpenStack Infra (hudson-openstack)]

Change abandoned by Saravanan KR (<email address hidden>) on branch: master
Review: https://review.openstack.org/339977
Reason: Spec not approved

[OpenStack Infra (hudson-openstack)]

Change abandoned by Saravanan KR (<email address hidden>) on branch: master
Review: https://review.openstack.org/331564
Reason: Dropping the proposal, because we are not able to find a better solution other that editing a file, which fits all use cases. For now, DPDK and SR-IOV features will use the userdata, with the assumption that all compute nodes will be of exactly same hardware specs.

Thanks all for the support.