Bug 1154485

Summary:	[RFE][ironic]: Support for UEFI secure boot
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	openstack-ironic	Assignee:	Lucas Alvares Gomes <lmartins>
Status:	CLOSED ERRATA	QA Contact:	Toure Dunnon <tdunnon>
Severity:	low	Docs Contact:
Priority:	high
Version:	unspecified	CC:	ddomingo, markmc, sgordon, yeylon
Target Milestone:	ga	Keywords:	FutureFeature
Target Release:	7.0 (Kilo)
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/ironic/+spec/uefi-secure-boot
Whiteboard:	upstream_milestone_kilo-rc1 upstream_definition_approved upstream_status_implemented
Fixed In Version:	openstack-ironic-2015.1.0-2.el7ost	Doc Type:	Enhancement
Doc Text:	The Bare Metal service can now deploy nodes using the Secure Boot feature of the UEFI (http://www.uefi.org). Secure Boot helps ensure that nodes boot only trusted software. With this, the whole boot chain can be verified at boot time. You can then configure nodes to only boot authorized images, thereby enhancing security.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-05 13:15:07 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description RHOS Integration 2014-10-20 04:02:59 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/ironic/+spec/uefi-secure-boot.

Description:

Some of the Ironic drivers supports UEFI deploy. It would be useful to the security sensitive customers to deploy baremetal using 'Secure Boot' supported by the UEFI.

Specification URL (additional information):

None

Comment 6 errata-xmlrpc 2015-08-05 13:15:07 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-2015:1548