From Fedora Project Wiki

< Anaconda

Revision as of 19:17, 16 May 2013 by Clumens (talk | contribs)

Source Overview

anaconda has a lot of source, and this can be a little intimidating at first. It can be difficult to figure out where to even start looking when you're trying to track a problem down. This guide is meant as a very high level overview of the various groups of source files and what sorts of things they cover. It's not incredibly detailed, and some source files don't want to fit into categories. Lots of pieces of functionality are spread out across multiple files.


pyanaconda/ui/gui/ pyanaconda/ui/tui/

These are the primary UI files for the interfaces supported by anaconda: graphical, text, and command line (which is really just a special form of text). Each is implemented by its own directory. For the graphical installer, the glade interface files are in the same location. For the text installer, this also includes the code required to do line-oriented input/output. There is a well-defined API here allowing for both adding additional interfaces and extending the existing interfaces with new screens.

pyanaconda/ui/ pyanaconda/ui/ pyanaconda/ui/ pyanaconda/ui/lib/

These files and directories contain code common to all supported interfaces. The first two files contain mostly base classes with code common to both the GUI and TUI. is a small file containing constants and methods for communicating between objects within the UI.


This file controls setting up VNC for when it is requested during installation. Afterwards, installs proceed in graphical mode.


All partitioning code is now contained in the python-blivet package, which we also work on.



This file controls configuring and writing out the bootloader to the installed system. Each type of machine has its own bootloader quirks (what types of devices and filesystems are supported by the bootloader, the syntax of the config file, etc). and therefore has its own class. This file additionally handles pulling together kernel command line arguments.


pyanaconda/ pyanaconda/ pyanaconda/ pyanaconda/ pyanaconda/ pyanaconda/ pyanaconda/

These files hold the configuration settings that are either entered through the interface or through kickstart. To some extent they affect the installation (for instance, the language and keyboard settings are used in anaconda). However, the main purpose is to write these out to the installed system at the end of installation.

Package Installation


These files control the installation of files in some format to the system. anaconda allows for multiple installation backends, though the most commonly used are and Each backend provides methods for selecting and removing environments, groups, and packages; configuring repos for use during and after installation; reporting progress; and so forth. There is a well-defined API here allowing for adding additional backends.

Installation Classes

pyanaconda/ pyanaconda/installclasses/ pyanaconda/

Installation classes define settings that form a sort of installation profile. This includes steps to show and skip, product names, installation method, enabled repositories, configuration settings, and so forth. We primarily use it to create a difference between Fedora and RHEL installs. Other projects or ISVs could define their own installation classes for their own defaults.

Special Modes


Kickstart is a way of automating installations by providing anaconda with a file that contains all the data that the user would have to provide via the UI. This file is an interface between the parser in the pykickstart package and the anaconda internals. Now that the UI now constructs a kickstart data object in memory, this file also handles certain execution tasks as well.

data/icons/ data/liveinst/

These files implement installation from the live CD. They provide some files needed to launch the installer from the live CD's desktop. The actual live installation is handled by the appropriate packaging backend.

pyanaconda/ pyanaconda/ pyanaconda/ pyanaconda/

These files provide the rescue mode.

Error Handling

pyanaconda/ pyanaconda/

These files control all the error reporting for anaconda., in combination with the UI, controls displaying errors that the user can do something about or at least that anaconda can anticipate. This is the central location for error messages. controls display of errors that anaconda cannot anticipate - basically, this is where unhandled exceptions get handled. This is also where anaconda interfaces with libreport to report issues to bugzilla.

Installation Control Library

pyanaconda/ pyanaconda/ pyanaconda/ pyanaconda/

This is a loose collection of important files. actually performs the installation steps, which just consists of calling out to methods throughout kickstart, anaconda, and python-blivet. provides a way for and the packaging backends to communicate with the UI for moving the progress bar and displaying messages. is a support file that constructs communications queues, like those used in and Finally, handles creating and managing threads, which anaconda now extensively uses for running tasks in the background while still allowing the UI to update.


pyanaconda/ pyanaconda/ pyanaconda/ pyanaconda/ pyanaconda/ pyanaconda/ pyanaconda/ pyanaconda/ pyanaconda/ pyanaconda/ pyanaconda/isys/ pyanaconda/ pyanaconda/ pyanaconda/ pyanaconda/ pyanaconda/

These files provide a variety of miscellaneous methods that are used throughout the installer. These functions include the logging framework, finding the user's location via geolocation, looking up information about attached optical installation media, communicating with NetworkManager, and many other tasks. They also contain methods that just don't fit anywhere else.

The Main Program


This is the main anaconda program that gets called via systemd at the end of system bootup. It handles lots of environment setup, enables updates if they exist, reads any kickstart file, sets up VNC, and other tasks. When all this is done, it hands control over to the UI which in turn drives the rest of installation.