Anaconda

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
m (Reverted edits by Alberto783 (talk) to last revision by Dcantrel)
(19 intermediate revisions by 8 users not shown)
Line 22: Line 22:
 
If you are an advanced user of anaconda, you should check out [[Anaconda/Options|  our reference to anaconda command line options]],[[Anaconda/Kickstart| our kickstart file format documentation]]  and [[Anaconda/Logging| our reference to logging capabilities of anaconda]].
 
If you are an advanced user of anaconda, you should check out [[Anaconda/Options|  our reference to anaconda command line options]],[[Anaconda/Kickstart| our kickstart file format documentation]]  and [[Anaconda/Logging| our reference to logging capabilities of anaconda]].
  
There is a mailing list devoted to the use of kickstart.  You can find the list signup and archive information at [http://www.redhat.com/mailman/listinfo/kickstart-list] .  This is the best place to share tips and tricks about kickstart.
+
There is a mailing list devoted to the use of kickstart.  You can find the list signup and archive information at [http://www.redhat.com/mailman/listinfo/kickstart-list kickstart list] .  This is the best place to share tips and tricks about kickstart.
  
 
== Distribution Builders ==
 
== Distribution Builders ==
Line 36: Line 36:
 
== Mailing Lists ==
 
== Mailing Lists ==
  
There are two mailing lists for Anaconda.  The first is the development mailing list.  This list is used to discuss development issues, submit patches, and other activities related to extending anaconda.  The sign up for the development list is located at [https://listman.redhat.com/mailman/listinfo/anaconda-devel-list anaconda development list site] .  Past discussions can be found in the [https://www.redhat.com/archives/anaconda-devel-list anaconda development archives] .
+
There are three mailing lists for Anaconda.  The first is the development mailing list.  This list is used to discuss development issues, submit patches, and other activities related to extending anaconda.  The sign up for the development list is located at [https://listman.redhat.com/mailman/listinfo/anaconda-devel-list anaconda development list site] .  Past discussions can be found in the [https://www.redhat.com/archives/anaconda-devel-list anaconda development archives] .
  
The second list is a user oriented list on how to create kickstart filesThe kickstart list is the place to discuss automated installation issues.  The sign up for the kickstart list is located at [https://www.redhat.com/mailman/listinfo/kickstart-list anaconda kickstart list site] .  Past discussions can be found in the [https://www.redhat.com/archives/kickstart-list anaconda kickstart archives] .
+
The second list is the anaconda patch review list.  This is a high traffic developer oriented list.  The sign up for the anaconda-patches list is located at [https://fedorahosted.org/mailman/listinfo/anaconda-patches anaconda-patches list site] .  Past discussions can be found in the [https://lists.fedorahosted.org/pipermail/anaconda-patches/ anaconda-patches archives] .
  
There is also the #anaconda IRC channel on irc.freenode.org.  This resource is for discussion of anaconda development, not for distribution customization questions.
+
The third list is a user oriented list on how to create kickstart files.  The kickstart list is the place to discuss automated installation issues.  The sign up for the kickstart list is located at [https://www.redhat.com/mailman/listinfo/kickstart-list anaconda kickstart list site] .  Past discussions can be found in the [https://www.redhat.com/archives/kickstart-list anaconda kickstart archives] .
 +
 
 +
== IRC ==
 +
 
 +
There is also an {{fpchat|#anaconda}} IRC channel on http://freenode.net.  This resource is for discussion of anaconda development, not for distribution customization questions.
  
 
== Developers' Guide ==
 
== Developers' Guide ==
Line 56: Line 60:
 
There's also some tips on the [[Anaconda/Building|  building anaconda]]  page describing how to compile and create a new version of the anaconda package.
 
There's also some tips on the [[Anaconda/Building|  building anaconda]]  page describing how to compile and create a new version of the anaconda package.
  
The [http://dcantrel.fedorapeople.org/anaconda/API/devel/ anaconda API reference] is an ongoing effort to document the anaconda source code.  This is far from complete, but getting better all the time.
+
The [http://dcantrel.fedorapeople.org/anaconda/API/ anaconda API reference] is an ongoing effort to document the anaconda source code by branch.  This is far from complete, but getting better all the time.
  
 
== Getting the Source ==
 
== Getting the Source ==
  
The primary methods of distributing the anaconda source are source RPMs in the [http://download.fedora.redhat.com/pub/fedora/linux/development/source/SRPMS/ Fedora development tree]  and git.  To access the current source code in in non-rpm format, you'll need to install git.
+
The primary methods of distributing the anaconda source are source RPMs in the [http://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/source/SRPMS/ Fedora development tree]  and git.  To access the current source code in in non-rpm format, you'll need to install git.
  
 
  yum install git
 
  yum install git
Line 100: Line 104:
 
http://git.fedorahosted.org/git/?p=anaconda.git;a=summary
 
http://git.fedorahosted.org/git/?p=anaconda.git;a=summary
  
To contribute you should read our [[Anaconda/Branches|Branching policy]] first.
+
To contribute you should read our [[Anaconda/Branches|Branching policy]] first and then follow the [[Anaconda/ReviewProcess|Patch review process]].
  
 
== Reporting Problems ==
 
== Reporting Problems ==
Line 119: Line 123:
  
 
* [[User:Clumens|Chris Lumens]] (clumens):  Kickstart, thinking up new stuff.
 
* [[User:Clumens|Chris Lumens]] (clumens):  Kickstart, thinking up new stuff.
* [[User:Mgracik|Martin Gracik]] (mgracik): firstboot, UI elements, lorax.
 
 
* [[User:Msivak|Martin Sivak]] (msivak):  FirstAidKit, driver disks.
 
* [[User:Msivak|Martin Sivak]] (msivak):  FirstAidKit, driver disks.
 
* [[User:Pjones|Peter Jones]] (pjones):  EFI.
 
* [[User:Pjones|Peter Jones]] (pjones):  EFI.
 
* [[User:Bcl|Brian Lane]] (bcl): LiveCD.
 
* [[User:Bcl|Brian Lane]] (bcl): LiveCD.
* [[User:Dcantrel|David Cantrell]] (dcantrell):  Manager, s390x.
+
* [[User:Dcantrel|David Cantrell]] (dcantrell):  Manager.
 
* [[User:Wwoods|Will Woods]] (wwoods): Stuff.
 
* [[User:Wwoods|Will Woods]] (wwoods): Stuff.
 
* [[User:Rvykydal|Radek Vykydal]] (rvykydal):  Networking.
 
* [[User:Rvykydal|Radek Vykydal]] (rvykydal):  Networking.
 
* [[User:Dlehman|Dave Lehman]] (dlehman):  Storage.
 
* [[User:Dlehman|Dave Lehman]] (dlehman):  Storage.
 +
* (not pictured) [[User:sbueno|Samantha N. Bueno]] (sbueno): s390x, text ui.
 +
* (not pictured) [[User:vpodzime|Vratislav Podzimek]] (vpodzime): keyboard layouts, date&time settings, exception handling
  
 
== Anaconda Team Emeritus ==
 
== Anaconda Team Emeritus ==
Line 134: Line 139:
 
* Hans de Goede (hansg)
 
* Hans de Goede (hansg)
 
* [[User:Akozumpl|Ales Kozumplik]] (akozumpl)
 
* [[User:Akozumpl|Ales Kozumplik]] (akozumpl)
 +
* [[User:Mgracik|Martin Gracik]] (mgracik)
 +
* [[User:jkeating|Jesse Keating]] (jlk)
  
 
== Design ==
 
== Design ==

Revision as of 12:43, 21 March 2013

Anaconda.png


Entering Anaconda, Montana.  A city probably named after this installation program.

Anaconda is the installation program used by Fedora, Red Hat Enterprise Linux and some other distributions.

During installation, a target computer's hardware is identified and configured and the appropriate file systems for the system's architecture are created. Finally, anaconda allows the user to install the operating system software on the target computer. anaconda can also upgrade existing installations of earlier versions of the same distribution. After the installation is complete, you can reboot into your installed system and continue doing customization using firstboot .

anaconda is a fairly sophisticated installer. It supports installation from local and remote sources such as CDs and DVDs, images stored on a hard drive, NFS, HTTP, and FTP. Installation can be scripted with kickstart to provide a fully unattended installation that can be duplicated on scores of machines. It can also be run over VNC on headless machines. A variety of advanced storage devices including LVM, RAID, iSCSI, and multipath are supported from the partitioning program. anaconda provides advanced debugging features such as remote logging, access to the python interactive debugger, and remote saving of exception dumps.

Contents

Users

If you are a user having problems with anaconda, please use the user support forum for your distribution such as Fedora Forum . There are a few useful documents for users under UserTips , but generally, this is dedicated to developers and advanced users of anaconda.

From time to time, we may distribute updates for anaconda to fix problems in Fedora releases. The updates wiki page explains how to use these updates images.

Need to see what's changed from release to release? See our migration guide which summarizes changes for users, rebuilders, and contributors.

Advanced Users

If you are an advanced user of anaconda, you should check out our reference to anaconda command line options, our kickstart file format documentation and our reference to logging capabilities of anaconda.

There is a mailing list devoted to the use of kickstart. You can find the list signup and archive information at kickstart list . This is the best place to share tips and tricks about kickstart.

Distribution Builders

For information on how to customize anaconda and trees created with it, please see BuildDocProject and Customization .

Developers

Anaconda is primarily written in the Python language . The graphical front-end of anaconda is written with pyGtk library and glade interface description files . Using Python for the majority of the installer code allows for easy distribution of updates and the quick development of new features. The loader, which handles loading the large main portion of anaconda, module loading, and other boot up tasks, is written in the C programming language. Some other minor hardware-specific portions of anaconda are also written in C. In addition, bash and python scripts are used for some administrative scripting duties.

The entire Anaconda package is distributed under the GPLv2.

Mailing Lists

There are three mailing lists for Anaconda. The first is the development mailing list. This list is used to discuss development issues, submit patches, and other activities related to extending anaconda. The sign up for the development list is located at anaconda development list site . Past discussions can be found in the anaconda development archives .

The second list is the anaconda patch review list. This is a high traffic developer oriented list. The sign up for the anaconda-patches list is located at anaconda-patches list site . Past discussions can be found in the anaconda-patches archives .

The third list is a user oriented list on how to create kickstart files. The kickstart list is the place to discuss automated installation issues. The sign up for the kickstart list is located at anaconda kickstart list site . Past discussions can be found in the anaconda kickstart archives .

IRC

There is also an #anaconda[?] IRC channel on http://freenode.net. This resource is for discussion of anaconda development, not for distribution customization questions.

Developers' Guide

If you want to work on Anaconda, you should start with the Source Overview , which contains a high level discussion of the source files and what they do. Then look at the stage1 development guide and the stage2 development guide for information on how to test, debug, and develop for these two parts of anaconda.

Familiarize yourself with the tools that anaconda uses. Check out the following external reference documents:

Once you're up and running, you should check out future work items for anaconda to see what we'd like to have done.

There's also some tips on the building anaconda page describing how to compile and create a new version of the anaconda package.

The anaconda API reference is an ongoing effort to document the anaconda source code by branch. This is far from complete, but getting better all the time.

Getting the Source

The primary methods of distributing the anaconda source are source RPMs in the Fedora development tree and git. To access the current source code in in non-rpm format, you'll need to install git.

yum install git

Note that several related packages will be installed as well. After the git source code management tool has been installed, then you use anonymous git access to the Anaconda repository.

git clone git://git.fedorahosted.org/git/anaconda.git

The output may look similar to the following:

Initialized empty Git repository in /home/drkludge/anacondatest/anaconda/.git/
remote: Generating pack...
remote: Counting objects: 10861
remote: Done counting 91222 objects.
remote: Deltifying 91222 objects...
remote:  100% (91222/91222) done
Indexing 91222 objects...
100% (91222/91222) done
remote: Total 91222 (delta 68785), reused 90187 (delta 68059)
Resolving 68785 deltas...
100% (68785/68785) done
Checking 543 files out...
100% (543/543) done


If you have committer access to anaconda, then you will want to use the git+ssh access url.

git clone git+ssh://git.fedorahosted.org/git/anaconda.git


Once you've committed changes locally, you can push them with

git push

If you would just like to browse the Anaconda git repository via the web, then please use one of the following two Anaconda git URLs .

http://git.fedorahosted.org/git/anaconda.git

http://git.fedorahosted.org/git/?p=anaconda.git;a=summary

To contribute you should read our Branching policy first and then follow the Patch review process.

Reporting Problems

If you are having difficulty installing, please file the problem report with your distribution vendor.

Before filing a bug, please read up on How to debug installation problems, which will tell you how to fill out useful bug reports that will help us quickly solve your problem. Also try searching bugzilla for other reports about your problem, as some bugs are often filed by several people.

CommonBugs is a list of common anaconda bug reports you may wish you check before filing a duplicate.

AnacondaBugWorkflow is a guideline to how Fedora anaconda bugs pass through bugzilla, and what all the various statuses really mean. This is only for Fedora.

Anaconda Team

Anaconda-team-fudcon-tempe-2011.png

From left to right, the following people are the anaconda team and are responsible for the majority of commits. Of course, we get help from other people both from Red Hat and from the volunteer community as well.

Anaconda Team Emeritus

Design