Platform Team/packagekit-backend-presolve

Summary

This is a PackageKit backend which is intended to be used on restricted systems, like XO-1 laptops, where regular package management routines are too heavy for limited amounts of memory or CPU resources.

The reason

The known, for the author of these lines, current practice is:

• olpc-update
  Rsync the full system.
• sugar-client's unattended update in Dextrose
  Regular update, but only for particular, much smaller than main ones, repository(ies).

Both methods are useful for the situations they were created for. But there is a situation when they both become less useful. Having Activity Library (or its distributed version on regional or school server), XO users might download activities directly from the Internet (or a distributed server). So, it is becoming hard to use:

• olpc-update,
  Activity Library might have non-standard dependencies, and it is either hard to keep the olpc-update server up-to-date, or, impractical to install all possible dependencies on every XO.

• sugar-client,
  activity dependencies are, in most cases, from official repositories when sugar-client's 3rd party repository are useless.

In other words, there is a need to install particular packages from an official Fedora repository and using existing methods is either impractical (olpc-update) or impossible (sugar-client). The fallback to use regular methods (like yum) is also not useful, because they take too much memory (at the beginning) and CPU resources. This is a special problem on XO-1 laptops.

The packagekit-backend-presolve method is intended to solve this issue by providing a standard way (it is PackageKit backend, i.e., sugar launching code will be common for all platforms, it will always call PackageKit) to install activity dependencies and consumes as little as possible resources on XO laptops. The backend was designed to support reliable launching from services like Activity Library and/or Sugar Network when there are activities that might have non-standard dependencies. This backend might be treated as a temporary solution, i.e., when either the XO is powerful enough, or regular installation procedures take fewer resources, it will be possible to switch to the default PackageKit backend (without making changes in activity launching code).

Concept

The general idea is to pre-resolve dependencies for a limited set of top-level packages and store this information on a server. Clients need to download only a small amount of information (compared with the entire list of available packages) to reuse it as-is (and avoid reading a database into memory during the solving process).

Another important feature is that pre-resolved dependency graphs don't include packages from the base system. In other words, a particular dependency tree doesn't end with the glibc package. Instead, it ends with the sugar package. This expedient should drastically reduce the size of trees.

Finally, missing packages will be installed directly by using the rpm -i command.

Upsides

• Users download metadata on a package-by-package basis, thus avoiding the need to download the full packages database;
• After downloading, metadata will be reused as-is, i.e., after checking what packages were already installed, the system will download only missing RPMs, and install them directly by calling the rpm -i command;
• Activities on resources like Activity Library or Sugar Network will be distro-agnostic. That is, they will work unmodified on all platforms that provide PackageKit (which means all mainstream GNU/Linux distributions).

Downsides

• The project is intended to install only a limited number of top-level packages, i.e., packages that have pre-resolved dependency trees on a server; for example, it is not suitable for a full system update;
• Need to support server-side generation of dependency trees.

Implementation

Premises

The implementation is following these premises:

• Being targeted only to XO laptops (assuming that other platforms are more powerful, thus the standard PackageKit backend can be used);
• Keep less work on the XO side and more work on the server side to make the installation process on a client's side as fast and reliable as possible;
• Implement only priority functionality, and provide more complex features as required, e.g., the current implementation doesn't support updating already installed packages. Leave that to hard (and rare, e.g., yearly) full system updates (re-flashes or calling olpc-update) and incremental regular updates (sugar-client).

Overview

• Clients keep a list of packages installed by the back-end;
• After getting an install request, the back-end will check if the requested package is already installed;
• If not, it downloads a file from a known HTTP location with the requested package's name;
• Downloaded file contains the RPM url for the requested package and a list of package-name/url pairs for all dependencies (starting from some known point);
• All missing packages will be downloaded and installed by directly calling rpm -i;
• Installed packages list will be updated correspondingly.

Repositories

Sugar Network

Sugar Network API server provides presolved data for packages registered in the Sugar Network Packages project.

The url path is:

GET /packages/REPOSITORY/ARCH/PACKAGE

Where REPOSITORY and ARCH come from OBS resolve project. Package data served in JSON notation.

Sources

Clone source repository from Gitorious project:

git clone git://git.sugarlabs.org/desktop/packagekit-backend-presolve.git

Getting involved

• Subscribe to the sugar-devel mailing list and email with the subject prefixed with [PLATFORM].
• Ask your question on IRC channels, #sugar (not logged) or #sugar-newbies (logged).