Bug 1593758

Summary:	[RFE][ironic] Redfish driver to manage BIOS configuration
Product:	Red Hat OpenStack	Reporter:	Ilya Etingof <ietingof>
Component:	openstack-ironic	Assignee:	Ilya Etingof <ietingof>
Status:	CLOSED ERRATA	QA Contact:	mlammon
Severity:	medium	Docs Contact:
Priority:	medium
Version:	15.0 (Stein)	CC:	bfournie, brault, dtantsur, gregraka, ietingof, jamsmith, mburns, racedoro, sasha, srevivo, yroblamo, zshi
Target Milestone:	Upstream M2	Keywords:	FutureFeature, TechPreview, Triaged
Target Release:	15.0 (Stein)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-ironic-12.1.2-0.20190615000404.c3cbdb5.el8ost	Doc Type:	Technology Preview
Doc Text:	Red Hat OpenStack Platform Bare Metal service (ironic) now has a BIOS management interface, with which you can inspect and modify a device’s BIOS configuration. In Red Hat OpenStack Platform 15, the Bare Metal service supports BIOS management capabilities for data center devices that are Redfish API compliant. The Bare Metal service implements Redfish calls through the Python library, Sushy.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-09-21 11:16:01 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, 1476902, 1577362

Description Ilya Etingof 2018-06-21 14:26:27 UTC

With the introduction of the BIOS management interface in ironic [1] it is now possible to inspect and modify BIOS configuration through BMCs that support system BIOS access.

Redfish protocol features BIOS management [2] capabilities. This bug is to implement BIOS management interface at the ironic Redfish hardware type.

1. https://specs.openstack.org/openstack/ironic-specs/specs/not-implemented/generic-bios-config.html
2. https://www.dmtf.org/sites/default/files/standards/documents/DSP2046_2017.0a.pdf  (p. 20)

Comment 1 Dmitry Tantsur 2018-06-21 15:15:56 UTC

Assigning you Ilya simply because we need someone to track it, and you're on this topic right now.

Comment 2 Dmitry Tantsur 2018-09-25 09:36:21 UTC

Purging patches a bit. Ilya, do we need to track message registry in the same RFE? It may take substantially more time than getting some BIOS support done.

Comment 3 Ilya Etingof 2018-09-25 10:14:41 UTC

I'd propose to track message registry separately because:

1) In simple cases, BIOS management should be reasonably operational without message registries
2) In discussions with DMTF those registries proved to be a non-trivial matter from both technical and legal perspectives

Once we get message registries feature resolved, we could update our BIOS implementation to leverage them.

Comment 4 Dmitry Tantsur 2018-09-25 10:21:08 UTC

That's my thinking as well. Let's then create a separate RFE and move the related patches there. The patches list here is scary :)

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

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

Comment 8 Bob Fournier 2019-01-04 19:38:09 UTC

It looks like this can move to POST as all patches have landed correct?

Do we also plan on landing the Message Registry RFE in OSP-15?  Also as TechPreview?

Comment 9 Dmitry Tantsur 2019-01-05 20:09:13 UTC

I think we need TripleO integration for BIOS, at least https://review.openstack.org/#/c/628681/

Comment 15 Ilya Etingof 2019-06-19 17:00:39 UTC

Please, review doctext.

Comment 17 Ilya Etingof 2019-06-25 07:29:16 UTC

The new doctext seems correct to me.

Comment 22 errata-xmlrpc 2019-09-21 11:16:01 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2019:2811