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

Bug 1153875

Summary: [RFE][ironic]: Expose configdrive to instances
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: openstack-ironicAssignee: Lucas Alvares Gomes <lmartins>
Status: CLOSED ERRATA QA Contact: Toure Dunnon <tdunnon>
Severity: high Docs Contact:
Priority: medium    
Version: unspecifiedCC: ddomingo, markmc, sgordon, yeylon
Target Milestone: Upstream M2Keywords: FutureFeature, OtherQA
Target Release: 7.0 (Kilo)   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/ironic/+spec/expose-configdrive
Whiteboard: upstream_milestone_kilo-2 upstream_definition_approved upstream_status_implemented
Fixed In Version: openstack-ironic-2015.1.0-4.el7ost Doc Type: Enhancement
Doc Text:
The Bare Metal service can now use cloud-init and similar early-initialization tools to insert user data on instances. Previously, doing so would have required setting up a metadata service to perform this function. With this new update, Bare Metal can insert instance metadata onto local disk upon deployment -- specifically, to a device labeled 'config-2'. Afterwards, you can configure the early-initialization tool to find this device and extract the data from there.
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-08-05 13:14:57 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:
Bug Depends On:    
Bug Blocks: 1273254    

Description RHOS Integration 2014-10-17 04:02:36 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/ironic/+spec/expose-configdrive.

Description:

This blueprint adds support for exposing a configdrive image to instances deployed by Ironic.

Specification URL (additional information):

https://review.openstack.org/#/c/99235/

Comment 8 errata-xmlrpc 2015-08-05 13:14:57 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