Project

General

Profile

Actions

Feature #983

closed

Need 3 state support in tftp and build management

Added by Kal McFate almost 13 years ago. Updated over 11 years ago.

Status:
Closed
Priority:
Normal
Category:
Unattended installations
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

In our current kick infrastructure the 'default' pxelinux file loads a staging environment that determines what os to build the system as and created the initial pxelinux file. Once kicked the system specific pxelinux file boots to the hd. Foreman has no current support for a pxelinux file for systems not currently undergoing a build, however for true unattended bare metal provisioning this is a requirement.

The stages would be:
bare system -> boots 'default' to register with build system
registered system -> boots build defined in system registry
built system -> boots hd

I can't have the default boot to hd, as then new systems would not be provisioned because I cannot add the tftp file for the new systems before hand as I do not know their information until they register.

Having an option for foreman to rewrite a second tftp template for a system once built would be better than just having it delete it entirely.

Actions #1

Updated by Ohad Levy almost 13 years ago

Maybe you could hack the default PXE option to achieve that?

Actions #2

Updated by Ohad Levy over 12 years ago

I would like to start promoting this ticket, how do we go ahead about the registering OS?

Actions #3

Updated by Ohad Levy over 11 years ago

  • Category set to Unattended installations
  • Status changed from New to Assigned
  • Assignee set to Greg Sutcliffe
  • Target version set to 1.1
Actions #4

Updated by Greg Sutcliffe over 11 years ago

  • Status changed from Assigned to Closed
  • % Done changed from 0 to 100
Actions

Also available in: Atom PDF