From Fedora Project Wiki
(Fixing number list)
No edit summary
Line 1: Line 1:
<!-- All fields on this form are required to be accepted by FESCo.
<!-- All fields on this form are required to be accepted by FESCo.
  We also request that you maintain the same order of sections so that all of the feature pages are uniform.  -->
  We also request that you maintain the same order of sections so that all of the feature pages are uniform.  -->
Line 82: Line 81:
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this feature depends?  In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel feature)? -->
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this feature depends?  In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel feature)? -->


Just gpxe.
* May require changes to the ks scripts that build our isos to include some additional modules:
** nfsv4
** iscsi
** httpfs


== Contingency Plan ==
== Contingency Plan ==

Revision as of 21:29, 8 January 2010


Feature Name

Summary

http://boot.fedoraproject.org/ is a boot method similar to pxeboot. It uses very small images (iso, floppy, disk) to bootstrap a machine that then contacts a remote server for boot information. This is a Fedora branded version of http://boot.kernel.org/.

Long term it is our hope this method will completely replace DVD downloads. The Fedora specific version is to raise awareness of the technology. gpxe (the technology that makes this possible) can even be written to nic roms or BIOS's.

Owner

  • Email: mmcgrath@redhat.com

Current status

  • Targeted release: Fedora 40
  • Last updated: 2010-01-08
  • Percentage of completion: 70%


Detailed Description

After booting from the boot media, users will be prompted with a fully available install menu for all currently supported versions of Fedora (i386 and x86_64). I'm also hoping to get rescue options as well as all of our available live media. This is obviously targeting reliable high-speed networks. The technology will be more compelling as internet speeds get faster.

Technical Steps

  1. Boot from downloaded gpxe image (be it floppy image, ISO or disk image)
  2. GPXE configures network dhcp or static (includes wireless!)
  3. User is prompted with a pxe menu to select various boot options
  4. Depending on boot option selected, the host then boots vmlinuz and initrd into anaconda and installs / rescues / boots as normal.

Benefit to Fedora

  1. Only need to download one very tiny image to get started with Fedora almost immedlately
  2. Only one image to boot all of Fedora's current options including live media.
  3. Might actually replace iso images one day

Scope

  1. Get gpxe package into Fedora
  2. Get branded screens for the menus - https://fedorahosted.org/design-team/ticket/115
  3. Finish configuration
  4. Decide how viable the live image boot is (relies on httpfs or iscsi)
  5. Create the boot.fedoraproject.org website with directions, etc.
  6. Along with 5) we'll have proper documentation.

How To Test

The test site is currently at http://publictest8.fedoraproject.org/boot/. To test for yourself via iso, download http://publictest8.fedoraproject.org/boot/gpxe.iso

User Experience

Users will see something very similar to a grub boot screen with options to boot from. They can use this often (as in booting live media) but users who chose to install will only see it once while installing.

They will notice it takes longer to boot the initrd and kernel images because it has to download them instead of booting them from an iso. Once booted though their experience should be identical to a normal network install.

Dependencies

  • May require changes to the ks scripts that build our isos to include some additional modules:
    • nfsv4
    • iscsi
    • httpfs

Contingency Plan

Documentation

  • Not done yet but will be completed.

Release Notes

  • TODO

Comments and Discussion