From ArchWiki
Jump to: navigation, search

Gnome-colors-add-files-to-archive.pngThis article is being considered for archiving.Gnome-colors-add-files-to-archive.png

Reason: Vaporware (Discuss in Talk:AIF-NG#)
Note: The previous AIF is dead and gone. This is not a fork of that project. This is a means for unattended installs (like Kickstart), and an entirely new codebase.

The full upstream documentation is available here. It is currently in development/review stages in preparation for proposal for inclusion on the official Arch installation media.

What it Is

AIF(-NG) (Arch Install Framework, "Next-Generation") is a means to automatically install Arch Linux. Think of it as something akin to Kickstart.

It is written in Python 3 and uses an XML configuration file that is remotely fetched and supports "hook scripts" for modular functionality. It can be useful as a tool to quickly turn up new Arch Linux installs.

AIF-NG is not an official Arch Linux project (though this will hopefully change when the project reaches a level of maturity ready for inclusion). Support information is available in the original documentation (bugs | feature requests | patches). It is highly unadvised that you go to the Arch Linux forums for support for this while its status is unofficial, and instead contact the author directly. This is to ensure possible bugs are dealt with.

What it Isn't

Note the use of the word "quickly", not "easily"- it isn't for the faint of heart, and it is not designed to make the Arch install process any easier. It is recommended that the user run through several Arch installs by hand before attempting to use this tool.

It also is not intended to be a complete turnup solution. Through the use of packages you specify and various hook scripts, you could get there 100% but if you're looking for something to just pop in, run, and go, this is not the tool you're looking for - there are other outside projects that attempt to do this. It is most powerful when combined with a configuration management software (such as Ansible, Chef, Puppet, Salt(stack), and others) - in other words, one would use AIF-NG to turn up the new machine from "baremetal" and install the configuration management agent, if necessary, and then complete the process on boot through the use of the configuration management system.

Getting Started

In order for AIF-NG to be useful, you must first have a configuration file. It then must be accessible from the installer ISO. It is highly recommended that it be served from a webserver in the LAN via HTTPS with basic authentication and properly firewalled, but there are several options for pointing to an AIF configuration (including a path on the local filesystem- though this would need to be present on the live/install system to work).

The documentation, as a temporary convenience while this project is under community review, offers ways to enable AIF-NG automatically. Take heed, however- it will write over whatever is on the disk that this live image is booted from, and the default configuration file most likely will not suit your needs. It is easy and recommended instead to build your own live image.

AIF-NG will then run silently in the background, logging to /root/aif.log.<TIMESTAMP>.


The official Arch Linux installer currently does not provide AIF-NG functionality out of the box. However, one can install either the aifAUR or aif-gitAUR packages. These will also handle the necessary dependencies. Once this is done, we will need to configure manual override enabling:

export DEBUG=true
cp /proc/cmdline /tmp/cmdline
sed -i -re 's/^(.*$)/\1 aif aif_url=YOUR_AIF-NG_CONFIGURATION_URI_HERE/g' /tmp/cmdline
aif &

AIF-NG will then run silently in the background, logging to /root/aif.log.<TIMESTAMP>.


Please see AIF-NG/Configuration file.