Improve the baremetal PXE deploy process

Registered by aeva black on 2012-12-12

Current approach:
- crude service on the nova compute node
- baremetal/pxe.py copies image from glance, mounts it, and does file injection for hostname, network, ssh keys
- nova-baremetal-deploy-helper mounts the baremetal node's disks via iSCSI, fdisks the partitions, and dd's the updated glance image over iSCSI
- node reboots into the image

There are several concerns with this approach, especially at scale, but it is sufficient for dev/test environments.
This is implemented by: https://review.openstack.org/#/c/15830/

Desired approach:
- no new services
- glance (or bittorrent) client embedded in deploy ramdisk
- image ID supplied to deploy ramdisk
- ramdisk fdisks the local disks, pulls specified image from glance, writes to local disk, and reboot into it
- cloud-init does the rest

Blueprint information

Status:
Complete
Approver:
Vish Ishaya
Priority:
Low
Drafter:
aeva black
Direction:
Needs approval
Assignee:
None
Definition:
Obsolete
Series goal:
None
Implementation:
Deferred
Milestone target:
None
Completed by
John Garbutt on 2014-03-20

Whiteboard

Doing this "the right way" (scalable, distributed, rack aware, etc) feels like premature optimization at this point, particularly when there are a lot of other deliverables on the roadmap for H and I cycles. I'd like to leave this BP up, as the intent is to go in this direction, but wait until after baremetal is split out and the other work is done.

Unapproved - please re-submit via nova-spec --johnthetubagy (20th March 2014)Doing this "the right way" (scalable, distributed, rack aware, etc) feels like premature optimization at this point, particularly when there are a lot of other deliverables on the roadmap for H and I cycles. I'd like to leave this BP up, as the intent is to go in this direction, but wait until after baremetal is split out and the other work is done.

Unapproved - please re-submit via nova-spec --johnthetubagy (20th March 2014)

This blueprint is not complete after a good year or so, marking as Obsolete to tidy up the Nova backlog. --johnthetubaguy (20th April 2014)

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.