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

Bug 1100535

Summary: [RFE][nova]: Add a virt driver for Ironic
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: openstack-novaAssignee: Russell Bryant <rbryant>
Status: CLOSED ERRATA QA Contact: Toure Dunnon <tdunnon>
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedCC: ddomingo, markmc, ndipanov, sgordon, slong, yeylon
Target Milestone: z2Keywords: FutureFeature, TechPreview, TestOnly, ZStream
Target Release: 6.0 (Juno)   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/nova/+spec/add-ironic-driver
Whiteboard: upstream_milestone_juno-rc1 upstream_definition_approved upstream_status_implemented
Fixed In Version: openstack-nova-2014.2.2-2.el7ost Doc Type: Technology Preview
Doc Text:
OpenStack Bare Metal Provisioning (ironic) is now included in this release as a Technology Preview. This service provisions bare-metal machines using common technologies (such as PXE boot and IPMI) to cover a wide range of hardware, while supporting pluggable drivers to allow the addition of vendor-specific functionality.
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-04-07 15:09:16 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: 1162407    

Description RHOS Integration 2014-05-23 04:02:17 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/nova/+spec/add-ironic-driver.

Description:

This specification proposes to add a virt driver to enable Nova to deploy
images to bare metal resources by using the OpenStack Bare Metal Provisioning
Service ("Ironic").


Specification URL (additional information):

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

Comment 6 errata-xmlrpc 2015-04-07 15:09:16 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://rhn.redhat.com/errata/RHSA-2015-0790.html