NetbootManagement

Differences between revisions 1 and 4 (spanning 3 versions)
⇤ ← Revision 1 as of 2005-10-15 12:01:16 →
Size: 2158
Editor: p5494F2A3
Comment:
← Revision 4 as of 2005-10-16 20:26:40 → ⇥
Size: 2440
Editor: p5494C202
Comment: updated dependents
Deletions are marked like this. Additions are marked like this.
Line 12: Line 12:
 * Depends:  * Depends: ConfigurationInfrastructure, AuthenticationInfrastructure | NetworkAuthentication
Line 43: Line 43:
The installed system needs to be integrated into the local CentralAuthentication infrastructure. Furthermore we need facilities for keeping the installations uptodate and install extra software packages. 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.
Line 49: Line 50:
 * Implement managment facilities using cfengine.
 * 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.
Line 58: Line 61:
 * CentralAuthentication  * ConfigurationInfrastructure
Line 63: Line 66:
----
CategorySpec

Summary

Enabling users to easily setup a computer pool (cluster) with ubuntu installations.

Rationale

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

Use cases

The obvious ones:

  • 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.

Design

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.

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:

BoF agenda and discussion

CategorySpec

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