Add support for deploying for ironic from baremetal node

Bug #1326319 reported by Ramakrishnan G (rameshg87) on 2014-06-04
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
diskimage-builder
Wishlist
Unassigned

Bug Description

The Openstack Baremteal Provisioning project Ironic expects the images and the deploy kernel/ramdisk to be built using diskimage-builder. For building the kernel/ramdisk for Ironic, the deployer needs to use the deploy-ironic element. This method exposes the baremetal node's local disk using iSCSI to the conductor node, and makes a vendor passthru call to the conductor for
completing the image deployment.

Using this method, all the image deployments happen from the ironic conductor node. This hogs the ironic conductor's resource such as CPU and Network I/O resources. Instead of this, the image deployment can be done from the baremetal node itself.

Ben Nemec (bnemec) wrote :

This kind of sounds like feature work. Depending on how complicated a change it is you might need a spec.

Changed in diskimage-builder:
status: New → Triaged
importance: Undecided → Wishlist
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers