nova-bm keeps a copy of baremetal image after deployment

[Robert Collins]

this is unneeded, it would be equivalent to nova vm keeping a pristine copy of every image deployed - glance is the right place to do that. This pushes the disk requirements for bare metal hypervisors waaaay up.

[Openstack Gerrit (openstack-gerrit)]

Fix proposed to branch: master
Review: https://review.openstack.org/92340

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/92340
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=e5985a0e988ad16b085e72159ebb02aa3fa68acb
Submitter: Jenkins
Branch: master

commit e5985a0e988ad16b085e72159ebb02aa3fa68acb
Author: Imre Farkas <email address hidden>
Date: Tue May 6 12:20:47 2014 +0200

    Cleanup images after deployment

    Ironic does not require local copies of instance images to be present in
    cache after deploy. This patch unlinks instance images after deployment
    finished, so that they can be deleted by cache clean up procedure and it
    triggers the clean up procedure.

    The patch also separates the fetching of tftp and instance images as the
    tftp image should be handled during the preparation of the environment,
    while the latter is only needed for the actual deployment.

    Change-Id: I4b975c06e60ab0f854749c8d18fd743fe770c7b0
    Closes-Bug: #1231351

[Robert Collins (lifeless)]

This is fixed for Ironic but we won't be trying to fix it for nova-bm - thats deprecated.

[Joe Gordon (jogo)]

nova baremetal is gone