XS LiveCD: Difference between revisions
(New page: {{OLPC}} Category:Software Category:Developers Category:SchoolServer This page describes the Live CD component build and distribution mechanism used by the [[XS_Server_Softwar...) |
(No difference)
|
Revision as of 09:52, 12 August 2007
This page describes the Live CD component build and distribution mechanism used by the School server software. It is not a guide to downloading and installing from the Live CD.
LiveCD
Live-Installer CD
The XS/XSX live CD is built by the Pilgrim-based livecd-creator tool, which builds a kickstart script into a live CD image. This is the same tool used to build the Fedora 7 live-installer CD. Currently, there are two branches of kickstart development. Holger Levsen's work on automating the live install process, and FAI configuration management, is located in a git repository at git://dev.laptop.org/projects/fai-config/fedora/live-installer/ , and his live CD image is available here (updates at 8AM BST daily). Because automating the live install has proved somewhat of a blocker, we currently maintain a second branch of build process, for development purposes. Scripts and data about this branch are located in a git repository at git://dev.laptop.org/projects/livecd-data , and a live CD image is available here. It is the latter process that is described below.
The basic live CD contains the following components:
Packages
Additional RPM packages of relevance to the XS/XSX are specified under the %packages header in the kickstart script. In general, these packages should come from the OLPC stable repository, a collection of packages that have been tested for compatibility with the school server. The current live CD mirrors the packages of our existing school server, schoolserver.laptop.org .
OLPC Configuration
Beyond Fedora 7's defaults, the live CD requires additional configurations to function as a real XS/XSX school server. In general, these configurations fall into one of three categories:
Package Configuration ("Alternative Defaults")
Default Fedora 7 packages often require special, OLPC-specific configurations. The typical solution to this problem is to perform the configuration in live-install postscript (hard to maintain and verify), or to use a configuration manager such as FAI (Holger's work). We have created an alternate, blunt-but-easy-to-develop solution using an RPM configuration package. This package contains a tree (starting at root) of configuration files. Installing the package links those files into place at the root of the file system. RPM's database is used to protect user's configuration changes while bashing RPM's defaults. This project is located in a git repository at git:/dev.laptop.org/projects/xs-config, and the package itself is available in a repository here. There are many scripts to help analyze and build configuration trees, in the livecd-data and xs-config git repositories.
OLPC Packages
Some of the XS/XSX's functionality is the product of OLPC development and, as such, has its own packaging. These packages are installed just like any other, by the live CD kickstart script. An example of such a package is the XS callhome scripts. The project is in a git repository at git://dev.laptop.org/projects/xs-callhome , and the package itself is available in a repository here.
Site-Specific Configuration
Site-specific configuration can be done either at OLPC build time ("early"), or after the school server reaches the field ("late"). Early configuration will probably involve country-specific content and localization, and may be thought of as branches off the main configuration tree. Late configuration will probably be done via a web interface published by the school server. Once the school server is plugged in and turned on, local installation techs will use the web interface to configure connectivity (which interface(s) are connected to the outside world, and possibly static network information) as well as having the server "phone home" with its geographic location, IP address, and hostname. The "phone home" step should also serve to connect the school server to the Content Distribution Network.
It may be worthwhile to have all configuration either early or late. The benefits of late configuration are more apparent, but will require a potentially-lengthy initial download while country-specific content and packages are installed onto the new school server.