Name of function:
Support for “Boot from Cinder Volume” for Bare Metal Instances

User story:
As an administrator I want to be able to boot a bare metal instance from an CInder volume, scale up or scale down (booting a bigger bare metal machine with different specs)  an application using bare metal nodes with different specs while keeping the persistent data.

Purpose of function:
During deployment of the bare metal nodes, the deployment process uses a volume presented from a Cinder volume as the root device disk.  The solution involves integration between Ironic, Cinder, and Nova enabling support for interacting with the SAN and the bare metal nodes.

Work required (from detail plan):
Procedural 
------
[Installed by director with Ironic]
Configure/set the cinder on the node
Enable iSCSI in the kernal
Configure/set the cinder on the node (admin case)
Adding hardware back into the pool
Set node capabilities 
Add a volume connector - info to boot the machine
------

Conceptual 
------
Need Cinder installed
Cinder back end/iSCSI
Ceph is NOT a back end that will work for this.
Parameter in the kernel to make this work
two ‘openstack baremetal’ commands
------

Reference
------
N/A
------