LtspUpdateManagerIntegration

Differences between revisions 2 and 3
⇤ ← Revision 2 as of 2007-04-30 13:50:59 →
Size: 1061
Editor: p548AD2BF
Comment:
← Revision 3 as of 2007-05-06 10:30:48 → ⇥
Size: 1415
Editor: 195
Comment:
Deletions are marked like this. Additions are marked like this.
Line 37: Line 37:
We'd like to:

 * update chroots that have similar architechtures as the server
 * Mount /proc as necessary
 * look in ltsp-update-kernels, for logic to decide if something's a chroot
 * set the LTSP_HANDLE_DAEMONS="false" to avoid restarting anything in the chroot when doing updates.
 * if the kernel's been updated, run ltsp-update-kernels

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 architechtures as the server
  • Mount /proc as necessary
  • look in ltsp-update-kernels, for logic to decide if something's a chroot
  • set the LTSP_HANDLE_DAEMONS="false" to avoid restarting anything in the chroot when doing updates.
  • if the kernel's been updated, run ltsp-update-kernels

CategorySpec

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