Project

General

Profile

Actions

Feature #14288

closed

Lock discovered host into discovery via PXE configuration

Added by Imri Zvik over 8 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Discovery plugin
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Usecase:
In our network, and probably in other networks with legacy hosts, the default PXE entry is bootlocal. The idea is that we don't want legacy hosts to accidentally go into discovery without explicit decision. So our racking procedure includes selecting the discovery mode via a PXE menu. After that, we want the host to stick to discovery, even if rebooted, until provisioned.
We patched our local installation to lock a host into discovery when it boots in discovery mode, by generating a PXE configuration.
We think this might be useful for others too. I am opening this ticket for discussion, and if accepted, I will open a PR for it.

Actions #1

Updated by Lukas Zapletal over 8 years ago

Hello, that's indeed useful feature. So a moment when a host is discovered for the first time, a PXELinux template gets rendered for the particular host on the TFTP proxy associated with the subnet the discovered host is found. The same template (snippet?) could be used in the global template as well: https://github.com/theforeman/community-templates/blob/develop/pxe/PXELinux_default.erb

Actions #2

Updated by Imri Zvik over 8 years ago

Lukas Zapletal wrote:

Hello, that's indeed useful feature. So a moment when a host is discovered for the first time, a PXELinux template gets rendered for the particular host on the TFTP proxy associated with the subnet the discovered host is found. The same template (snippet?) could be used in the global template as well: https://github.com/theforeman/community-templates/blob/develop/pxe/PXELinux_default.erb

OK, so I'll start working on a PR for it :)

Actions #3

Updated by Lukas Zapletal over 8 years ago

  • Assignee set to Imri Zvik

I'd like to avoid copying, so if you can create common snippet to use in both PXELinux templates, that would be useful. But that's detail. Thanks!

Actions #4

Updated by The Foreman Bot over 8 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman_discovery/pull/265 added
Actions #5

Updated by Imri Zvik over 8 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions

Also available in: Atom PDF