Red Hat Bugzilla – Bug 1478782
[CMCC][RFE] [ironic] automation of BIOS configuration
Last modified: 2018-04-16 15:17:31 EDT
Description of problem:
There are several NFV Use cases that need to configure BIOS settings to enable certain functionality or gain performance optimization(latency and throughput) on compute nodes.
For example, C-RAN (Cloud Radio Access Network) is one of the use cases that require many BIOS options be configured to achieve deterministic low packet latency. The most important configuration is to disable all options related to Power Management, CPU sleep states, etc. Also, disable any options related to hyper threading or logical processor.
Another example is that when using SR-IOV or DPDK technologies, 'Virtualization Technology' shall be enabled, for SR-IOV particularly, 'SR-IOV Global Enable' option shall be set to 'Enabled'.
Instead of configuring these settings manually on all the nodes which would be time consuming and error prone, an automation method for BIOS configuration is required in openstack ironic.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
I think it should be treated similar to RAID. Create a way to accept a blob with BIOS attributes (maybe a node field, maybe a new API), then allow vendors to create a clean step to apply them. Then we can create a workflow in TripleO to set parameters based on profile assigned to a node, again, similar to the RAID workflow.
This will need an ironic RFE/spec and a TripleO blueprint.
(In reply to Dmitry Tantsur from comment #1)
> I think it should be treated similar to RAID. Create a way to accept a blob
> with BIOS attributes (maybe a node field, maybe a new API), then allow
> vendors to create a clean step to apply them. Then we can create a workflow
> in TripleO to set parameters based on profile assigned to a node, again,
> similar to the RAID workflow.
> This will need an ironic RFE/spec and a TripleO blueprint.
thanks for review, Dmitry. do you have plan to write the spec for ironic and tripleo or you prefer to have volunteer to work on that. let me know if anything I could help.
Hi! We could use any help, as the team is quite overloaded right now. Please go ahead with the spec, if you have free cycles for it. Thanks!
(In reply to zenghui.shi from comment #4)
> RFE: https://bugs.launchpad.net/ironic/+bug/1712032
working on the spec file.
(In reply to zenghui.shi from comment #5)
> (In reply to zenghui.shi from comment #4)
> > RFE: https://bugs.launchpad.net/ironic/+bug/1712032
> working on the spec file.
spec review: https://review.openstack.org/#/c/496481/
Moving to you, as you've been working on it so far. Also status -> ASSIGNED as the code is not fully up yet.
Can we retarget this for OSP-14 as it seems unlikely to make OSP-13 at this point?
(In reply to Bob Fournier from comment #15)
> Can we retarget this for OSP-14 as it seems unlikely to make OSP-13 at this
I believe so, the spec is still under review and not be able to finalized; coding is just in the early stage, I'd say targeting it for osp-14 is more realistic.
Thanks Zenghui. Retargeting this to OSP-14.