Project

General

Profile

Actions

Feature #9278

open

Copy required files for iPXE booting

Added by Ohad Levy about 9 years ago. Updated almost 6 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Foreman modules
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

it is possible to use IPXE to chainload boot files and to boot over HTTP
see background at Fetch_boot_files_via_http_instead_of_TFTP

I would like the installer to be able to pull in the IPXE boot files out of the box (as its already available in the ipxe-bootimgs rpm).

Actions #1

Updated by Ohad Levy about 9 years ago

  • Description updated (diff)
Actions #2

Updated by Bryan Kearney about 9 years ago

  • Bugzilla link set to 1190478
Actions #3

Updated by Lukas Zapletal about 9 years ago

I've verified it is being shipped in both RHEL 6 and 7:

[root@fsix ~]# rpm -ql ipxe-bootimgs
/usr/share/doc/ipxe-bootimgs-20130517
/usr/share/doc/ipxe-bootimgs-20130517/COPYING
/usr/share/doc/ipxe-bootimgs-20130517/COPYRIGHTS
/usr/share/doc/ipxe-bootimgs-20130517/USAGE
/usr/share/ipxe
/usr/share/ipxe/ipxe.dsk
/usr/share/ipxe/ipxe.iso
/usr/share/ipxe/ipxe.lkrn
/usr/share/ipxe/ipxe.usb
/usr/share/ipxe/undionly.kpxe

Do we also want to create appropriate symlinks in TFTP directory so they are kept up-to-date? In this case, we should test it with SELinux (might need extra symlink rule). But I am afraid symlink won't work and we need a copy/hardlink because of the chroot environment.

Actions #4

Updated by Dominic Cleal about 9 years ago

iPXE isn't shipped in EL6, we provide it in the plugins repo. My experiences with hardware compatibility in bootdisk haven't been good, so I wouldn't recommend it as a default.

Actions #5

Updated by Ohad Levy about 9 years ago

Dominic Cleal wrote:

iPXE isn't shipped in EL6, we provide it in the plugins repo. My experiences with hardware compatibility in bootdisk haven't been good, so I wouldn't recommend it as a default.

I didn't mean it should be the default provisioning means, but rather have the ability for the installer (aligned with community templates) to use it, so overall simplify it for those who wants to use it.

Actions #6

Updated by Lukas Zapletal almost 6 years ago

  • Subject changed from Support IPXE chainloading out of the box to Copy required files for iPXE booting

We added required templates into Foreman 1.11 and the document mentions this as "recent version". So everything is ready in Foreman and this installer RFE can be implemented. The goal of this ticket is to install necessary files for iPXE, see

https://projects.theforeman.org/projects/foreman/wiki/Fetch_boot_files_via_http_instead_of_TFTP

  • cp /usr/share/ipxe/ipxe.lkrn /var/lib/tftpboot/
  • cp /usr/share/ipxe/undionly.kpxe /var/lib/tftpboot/undionly-ipxe.0
  • cp /usr/share/syslinux/gpxelinuxk.0 /var/lib/tftpboot/
  • change in dhcpd.conf:
if exists user-class and option user-class = "iPXE" {
  filename "http://foreman:443/unattended/iPXE";
} else {
  filename "pxelinux.0";
}

When templates plugin is enabled, the URL should be http://proxy:8000/unattended/iPXE then. The if statement already contains some lines, this needs to be incorporated into it.

Actions

Also available in: Atom PDF