Bug 1041020

Summary:	[RFE][nova]: Improve the baremetal PXE deploy process
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	RFEs	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	markmc, yeylon
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/nova/+spec/improve-baremetal-pxe-deploy
Whiteboard:	upstream_milestone_none upstream_status_deferred upstream_definition_obsolete
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-19 17:16:49 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description RHOS Integration 2013-12-12 13:25:56 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/nova/+spec/improve-baremetal-pxe-deploy.

Description:

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

Specification URL (additional information):

None