NetbootManagement

Differences between revisions 2 and 6 (spanning 4 versions)
⇤ ← Revision 2 as of 2005-10-15 12:13:52 →
Size: 2339
Editor: p5494F2A3
Comment:
← Revision 6 as of 2005-11-02 00:00:03 → ⇥
Size: 4233
Editor: 209
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
##(see the SpecSpec for an explanation)

 * Created: 15. Okt by ReinhardTartler
 * Priority: NeedsPriority
 * People: NeedsLead, NeedsSecond
 * Contributors: siretart
 * Interested:
 * Status: UbzSpecification, BrainDump (then DraftSpecification then EditedSpecification then ApprovedSpecification), DistroSpecification
 * Branch:
 * Malone bug:
 * Packages affected:
 * Depends:
 * Dependents:
 [[FullSearch()]]
 * BoF sessions: none yet 		 * '''Launchpad Entry''': https://launchpad.net/distros/ubuntu/+spec/cluster-installation
 * '''Created''': [[Date(2005-10-27T21:14:37Z)]] by JaneWeideman
 * '''Contributors''': JaneWeideman, ReinhardTartler, IvanKrstic
 * '''Packages affected''':
 * Depends: ConfigurationInfrastructure, AuthenticationInfrastructure | NetworkAuthentication
Line 19: Line 9:
Enabling users to easily setup a computer pool (cluster) with ubuntu installations. Enabling users to easily perform mass installations of Ubuntu on a pool of machines.
Line 23: Line 13:
We already have fully automated installation with d-i using preseeding (and/or kickstart). We plan to have a CentralAuthentication facility. Let's put all parts together so they work out-of-the-box We already have fully automated installation with d-i using preseeding (and/or kickstart).
Let's put all parts together so they work out-of-the-box.
Line 29: Line 20:
 * Internet cafe clusters, where anonymous users can surf
 * Educational clusters at universities and/or schools

The less obvious ones:

 * Offices, when all workstations needs to be able to install in a timely manner, but are still customizable enough for the local admin.		  * Andreas is running an Internet cafe on several thick clients. He doesn't want to use the LTSP functionality in Breezy, but wants to install Ubuntu on each machine individually, and be able to trivially reinstall any machine.
 
 * Kathrin runs HPC computing clusters at her university. She needs to be able to install Ubuntu on 300 compute nodes, and have each node register itself with the resource manager upon finishing installation. She also wants nodes to stage certain files from the central server locally. The whole pool should be trivial to reinstall by simply rebooting the nodes.
Line 38: Line 26:
To allow the admin to use both ltsp setups as well as cluster setups, we need some interface to dhcp config. We define therefore netboot modes:
 * computer netboots in ltsp mode. This is what we already have
 * computer netboots in installer mode. This time, the computer gets fully automatically installed using d-i preseeding and/or kickstart
 * The default netboot mode is user/admin definable.		 To allow the admin to use both ltsp setups as well as cluster setups, we need a graphical, easy to use interface to the dhcpd configuration files. By default, we'd want to offer several netboot options for the machines:
 * Computer netboots in thin client mode (ltsp). This is what we already have preinstalled by the edubuntu installer.
 * Computer netboots in installation mode. This time, the computer gets fully automatically installed using d-i preseeding and/or kickstart.

== GUI tool design ==

The dhcpd configuration GUI tool is instrumental for this spec in a Edubuntu setting, where we don't want the administrator to have to edit configuration files by hand. The tool's primary purpose is to keep track of known and unknown machines that request IPs on the network. It allows the selection of netboot images for known machines, and provide two configurable policies: one for known machines which aren't specially configured, and one for unknown machines.

For example, Andreas, the internet cafe owner from our first use case, will install his main Ubuntu server, and loads the GUI tool. He will set the default netboot policy for unknown machines to 'netboot the installer image' and provide a kickstart file he created with the kickstart configuration tool (already in breezy). When he saves the configuration, he can boot the rest of the computers in his internet cafe. They will fall under the default netboot policy for unknown machines, and will start the installer image, installing a standard internet cafe desktop fully unattended.

allows the administrator to select which image is booted the next time each machine netboots.
 * The GUI tool allows to define default netboot settings for both known and unknown machines.
 * The Admin has to provide either a kickstart or a d-i preseed file.
 
Line 65: Line 63:
== Notes ==

Need to send to main server: just where to locate the next bootloader to chain to
(keep in mind having to potentially translate grub syntax for locating the bootloader)
- modify grub/lilo installers to put the final install device somewhere we can read it from
- remind cjwatson
Line 66: Line 71:
----

Summary

Enabling users to easily perform mass installations of Ubuntu on a pool of machines.

Rationale

We already have fully automated installation with d-i using preseeding (and/or kickstart). Let's put all parts together so they work out-of-the-box.

Use cases

The obvious ones:

  • Andreas is running an Internet cafe on several thick clients. He doesn't want to use the LTSP functionality in Breezy, but wants to install Ubuntu on each machine individually, and be able to trivially reinstall any machine.
  • Kathrin runs HPC computing clusters at her university. She needs to be able to install Ubuntu on 300 compute nodes, and have each node register itself with the resource manager upon finishing installation. She also wants nodes to stage certain files from the central server locally. The whole pool should be trivial to reinstall by simply rebooting the nodes.

Design

To allow the admin to use both ltsp setups as well as cluster setups, we need a graphical, easy to use interface to the dhcpd configuration files. By default, we'd want to offer several netboot options for the machines:

  • Computer netboots in thin client mode (ltsp). This is what we already have preinstalled by the edubuntu installer.
  • Computer netboots in installation mode. This time, the computer gets fully automatically installed using d-i preseeding and/or kickstart.

GUI tool design

The dhcpd configuration GUI tool is instrumental for this spec in a Edubuntu setting, where we don't want the administrator to have to edit configuration files by hand. The tool's primary purpose is to keep track of known and unknown machines that request IPs on the network. It allows the selection of netboot images for known machines, and provide two configurable policies: one for known machines which aren't specially configured, and one for unknown machines.

For example, Andreas, the internet cafe owner from our first use case, will install his main Ubuntu server, and loads the GUI tool. He will set the default netboot policy for unknown machines to 'netboot the installer image' and provide a kickstart file he created with the kickstart configuration tool (already in breezy). When he saves the configuration, he can boot the rest of the computers in his internet cafe. They will fall under the default netboot policy for unknown machines, and will start the installer image, installing a standard internet cafe desktop fully unattended.

allows the administrator to select which image is booted the next time each machine netboots.

  • The GUI tool allows to define default netboot settings for both known and unknown machines.
  • The Admin has to provide either a kickstart or a d-i preseed file.

After that automated installation, a post-install script hooks up with the ConfigurationInfrastructure. This is then responsible for integration with CentralAuthentication and handling software updates.

Implementation

  • Define interface to dhcpd config to define netboot actions
  • Define interface to create/update/edit preseed configs
  • Implement a GUI Tool using these interfaces, so that a local admin can register machines and defines the netboot method. Takes kickstart or preseed files form the admin and enables fully (or semi) automated installs.

Code

Data preservation and migration

Outstanding issues

Needs integration with:

Notes

Need to send to main server: just where to locate the next bootloader to chain to (keep in mind having to potentially translate grub syntax for locating the bootloader) - modify grub/lilo installers to put the final install device somewhere we can read it from - remind cjwatson

BoF agenda and discussion

NetbootManagement (last edited 2008-08-06 16:24:21 by localhost)