A no-op deploy driver for PXE boot
Towards the goal of "diskless" boot, but different than boot-from-volume, this blueprint proposes to create in a new deploy driver following the code pattern of the iscsi_deploy driver. However, instead of using the deploy ramdisk to for facilitating the iSCSI image transfer while the conductor is waiting for a call-back, the no-op driver will simply boot the node directly to the pxe target "boot", skipping "deploy". In effect, it will skip the deploy ramdisk boot cycle and will not automatically populate the "root=" field in the pxe config. In order to have a useful deployment, the feature "Override PXE options via Glance property" [1] is used to specify the root device in the glance image properties or the node's instance_info. t will then be up to the operator to configure the method of boot that they specify in the PXE cmdline. For example: kernel_
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Low
- Drafter:
- Blake Caldwell
- Direction:
- Needs approval
- Assignee:
- Blake Caldwell
- Definition:
- Drafting
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Sprints
Whiteboard
Hi Blake, thanks for the proposal. We're moving from using blueprints to track features to rfe bugs. I've filed one for your change - https:/
Please track further work there using Closes-Bug, Partial-Bug or Related-Bug in commit messages and use RFE bug link in the proposed spec.
//vdrok 2015-12-15