Flavor based ramdisk/kernel ID is deprecated in Ironic since Juno

[Clint Byrum]

We currently set the ramdisk and kernel ID in the baremetal flavor, but that has been deprecated since Juno. Each node needs to have this ID set.

[Clint Byrum (clint-fewbar)]

We need to start setting the IDs in os-cloud-config's register-nodes, and we need to stop setting it in the flavor in setup-baremetal which is still in tripleo-incubator.

[OpenStack Infra (hudson-openstack)]

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

[James Slagle (james-slagle)]

i'll take this one. i dont think it's a critical though

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/141217
Committed: https://git.openstack.org/cgit/openstack/os-cloud-config/commit/?id=2cb8d584c7eeb90f2f2f59e090cf0b607a20945f
Submitter: Jenkins
Branch: master

commit 2cb8d584c7eeb90f2f2f59e090cf0b607a20945f
Author: Clint Byrum <email address hidden>
Date: Thu Dec 11 15:46:34 2014 -0800

    Set kernel and ramdisk ID for ironic nodes

    Ironic has deprecated per-flavor ramdisk and kernel image IDs in favor
    of setting them per-node. These parameters are optional to preserve
    backward compatibility. For ease of use, the command line client takes
    the kernel and ramdisk name and looks up the ID via glance. Also, they
    are completely ignored on nova-bm since it does not have a per-node
    setting for these ids.

    Co-Authored-By: Steve Kowalik <email address hidden>

    Change-Id: I702afe81038b6f962ce383edb58227a6015c2a75
    Partial-Bug: #1401617