LtspUpdateManagerIntegration

Differences between revisions 1 and 5 (spanning 4 versions)
⇤ ← Revision 1 as of 2007-04-30 13:40:48 →
Size: 520
Editor: p548AD2BF
Comment:
← Revision 5 as of 2007-05-06 10:38:50 → ⇥
Size: 1611
Editor: 195
Comment:
Deletions are marked like this. Additions are marked like this.
Line 7: Line 7:
Currently keeping an LTSP client chroot up to date or upgradint it to the next version requires commandline tasks from the adiminstrator. This spec shall define a way to integrate update management with the provided distro tools (for a start only integration with the gnome update manager will be discussed, but a kubuntu solution should be kept in mind while defining the implementation). Beyond security update management also dist-upgrader integration should take place so the client chroot gets upgraded to a new release automatically.
Line 36: Line 37:
We'd like to:

 * Update chroots that have similar architectures as the server
 * Mount /proc as necessary
 * Look in ltsp-update-kernels, for logic to decide if somethings a chroot
 * set the environment variable LTSP_HANDLE_DAEMONS="false" to avoid restarting anything in the chroot when doing updates.
 * If the kernel's been updated, run ltsp-update-kernels. If it's not easy to do this, then simply run it by default every time (wasteful, but shouldn't introduce any problems)
 * Implement using an "ltsp-chroot" wrapper script.
 

Summary

Currently keeping an LTSP client chroot up to date or upgradint it to the next version requires commandline tasks from the adiminstrator. This spec shall define a way to integrate update management with the provided distro tools (for a start only integration with the gnome update manager will be discussed, but a kubuntu solution should be kept in mind while defining the implementation). Beyond security update management also dist-upgrader integration should take place so the client chroot gets upgraded to a new release automatically.

Rationale

Use Cases

Scope

Design

Summary

Rationale

Scope and Use Cases

Implementation Plan

Implementation

Outstanding Issues

BoF agenda and discussion

We'd like to:

  • Update chroots that have similar architectures as the server
  • Mount /proc as necessary
  • Look in ltsp-update-kernels, for logic to decide if somethings a chroot
  • set the environment variable LTSP_HANDLE_DAEMONS="false" to avoid restarting anything in the chroot when doing updates.
  • If the kernel's been updated, run ltsp-update-kernels. If it's not easy to do this, then simply run it by default every time (wasteful, but shouldn't introduce any problems)
  • Implement using an "ltsp-chroot" wrapper script.

CategorySpec

LtspUpdateManagerIntegration (last edited 2009-07-24 03:07:22 by 201)