Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1609802

Summary:	[RFE] Support ramdisk deployment
Product:	Red Hat OpenStack	Reporter:	Julia Kreger <jkreger>
Component:	openstack-ironic	Assignee:	Julia Kreger <jkreger>
Status:	CLOSED ERRATA	QA Contact:	mlammon
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	bfournie, mburns, racedoro, sasha, srevivo
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:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-09-21 11:16:20 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:

Description Julia Kreger 2018-07-30 13:45:21 UTC

Description of problem:

Upstream ironic has merged basic support (in Rocky) for an additional deployment interface, primarily geared at large scale operators and the scientific community as their use cases of rapid turnaround and disk-less nodes, since disk are often viewed as a additional possible failure point at that scale and operating class.

This interface does have a number of limitations[1] from standard interface usage, but we should test and support basic usage for operators that seek ephemeral nodes to be deployed.

[1] https://specs.openstack.org/openstack/ironic-specs/specs/not-implemented/boot-from-ramdisk.html

Comment 1 Julia Kreger 2018-08-16 13:07:55 UTC

Discussed with Ramon and this will be treated as a TechPreview item.

Comment 4 Dmitry Tantsur 2019-01-04 15:18:39 UTC

Code complete. Can be enabled via modifying IronicEnabledDeployInterfaces. Should probably be enabled by default when leaving TechPreview.

Comment 9 errata-xmlrpc 2019-09-21 11:16:20 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