Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1030172

Summary:	Document bare metal provisioning process in the architecture guide
Product:	[Retired] Beaker	Reporter:	Nick Coghlan <ncoghlan>
Component:	Doc	Assignee:	Dan Callaghan <dcallagh>
Status:	CLOSED CURRENTRELEASE	QA Contact:	tools-bugs <tools-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	0.14	CC:	aigao, asaha, dcallagh, llim, qwan, rmancy, xjia
Target Milestone:	0.14.4	Keywords:	Documentation
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-12-19 05:09:12 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Nick Coghlan 2013-11-14 04:41:18 UTC

The architecture guide should provide an overview of the provisioning process for a system:

- kickstart generation
- tftp configuration
- power commands to trigger DHCP (and hence network boot from tftp)
- installation progress reporting back to the lab controller
- ensuring network boot remains first in the boot order
- clearing the tftp config (allowing local boot)
- cleaning up at system return/recipe completion

Comment 1 Nick Coghlan 2013-11-14 04:42:17 UTC

"tftp configuration" means "bootloader configuration via tftp" rather than configuring the tftp server itself.

Comment 2 Dan Callaghan 2013-11-21 22:35:37 UTC

http://gerrit.beaker-project.org/2517

Comment 3 Dan Callaghan 2013-11-24 23:57:11 UTC

This is now included in the development version of Beaker's documentation:

http://beaker-project.org/docs-develop/architecture-guide/provisioning-process.html

Comment 4 xjia 2013-11-25 05:40:45 UTC

Verify this bug. This doc makes sense.

Comment 5 Nick Coghlan 2013-11-29 05:40:32 UTC

We backported this to the 0.14.4, as it's relevant to the 0.14.4 EFI boot order fixes.