LtspUpdateManagerIntegration

Differences between revisions 3 and 4
⇤ ← Revision 3 as of 2007-05-06 10:30:48 →
Size: 1415
Editor: 195
Comment:
← Revision 4 as of 2007-05-06 10:35:47 → ⇥
Size: 1555
Editor: 195
Comment:
Deletions are marked like this. Additions are marked like this.
Line 39: Line 39:
 * update chroots that have similar architechtures as the server  * Update chroots that have similar architectures as the server
Line 41: Line 41:
 * 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		  * 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)

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)

CategorySpec

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