Bug 1478782

Summary:	[CMCC][RFE] [ironic] automation of BIOS configuration
Product:	Red Hat OpenStack	Reporter:	zenghui.shi <zshi>
Component:	openstack-ironic	Assignee:	zenghui.shi <zshi>
Status:	CLOSED DUPLICATE	QA Contact:	mlammon
Severity:	high	Docs Contact:
Priority:	high
Version:	13.0 (Queens)	CC:	arkady_kanevsky, athomas, bfournie, dtantsur, fbaudin, ietingof, jniu, mburns, racedo, racedoro, rhel-osp-director-maint, sclewis, srevivo, yroblamo, zshi
Target Milestone:	Upstream M2	Keywords:	FutureFeature, Triaged
Target Release:	15.0 (Stein)
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-09-25 15:03:29 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:	1339072, 1419948, 1476902, 1577362

Description zenghui.shi 2017-08-07 04:53:13 UTC

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):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Dmitry Tantsur 2017-08-16 10:20:29 UTC

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.

Comment 2 zenghui.shi 2017-08-19 09:46:53 UTC

(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.

Comment 3 Dmitry Tantsur 2017-08-21 11:26:07 UTC

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!

Comment 4 zenghui.shi 2017-08-21 11:36:21 UTC

RFE: https://bugs.launchpad.net/ironic/+bug/1712032

Comment 5 zenghui.shi 2017-08-22 14:37:40 UTC

(In reply to zenghui.shi from comment #4)
> RFE: https://bugs.launchpad.net/ironic/+bug/1712032

working on the spec file.

Comment 6 zenghui.shi 2017-08-23 04:56:43 UTC

(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/

Comment 10 Dmitry Tantsur 2017-10-02 11:00:51 UTC

Moving to you, as you've been working on it so far. Also status -> ASSIGNED as the code is not fully up yet.

Comment 15 Bob Fournier 2018-01-17 18:17:09 UTC

Can we retarget this for OSP-14 as it seems unlikely to make OSP-13 at this point?

Comment 16 zenghui.shi 2018-01-20 02:07:41 UTC

(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
> point?

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.

Comment 17 Bob Fournier 2018-01-22 14:05:44 UTC

Thanks Zenghui.  Retargeting this to OSP-14.

Comment 22 Dmitry Tantsur 2018-06-14 08:22:38 UTC

Hi, do we have TripleO integration bits proposed already? If not, this RFE is at risk for 14 and will probably be pushed out.

Comment 23 Ramon Acedo 2018-06-18 12:44:15 UTC

The last gerrit patch seems to be the TripleO integration, which as of this comment is not merged yet. Moving to OSP 15 based on the M2 deadline was the 15th June

Comment 27 Ilya Etingof 2018-06-21 13:48:40 UTC

*** Bug 1593727 has been marked as a duplicate of this bug. ***

Comment 28 zenghui.shi 2018-06-21 14:04:56 UTC

(In reply to Dmitry Tantsur from comment #22)
> Hi, do we have TripleO integration bits proposed already? If not, this RFE
> is at risk for 14 and will probably be pushed out.

BP proposed in tripleo for integrating BIOS workflow:
https://blueprints.launchpad.net/tripleo/+spec/bios-workflow

the patch reviews: 
https://review.openstack.org/#/c/576449/
https://review.openstack.org/#/c/576471/

Comment 29 Ilya Etingof 2018-08-17 08:39:53 UTC

*** Bug 1396292 has been marked as a duplicate of this bug. ***

Comment 31 Bob Fournier 2018-09-25 15:03:29 UTC

Making this a duplicate to the RFE where testing will be done for this feature.

*** This bug has been marked as a duplicate of bug 1593758 ***