Foreman

{{toc}}

h1. How do I use unattended installations (Kickstart, jumpstart, preseed)?

Foreman manages the host creation process by controlling a host's DHCP, DNS, TFTP boot files, Puppet CA and node classification. This is whole process is handled in the core foreman program and in several satellite proxies running at various locations within the organization. More details can be found on the [[Foreman_Architecture]] page. 

Foreman automates network boot processes using PXEboot, gPXE, (or native Solaris net:dhcp).

You probably want to look into installing the [[Smart-Proxy:Wiki|Smart Proxy]] (which could be on the same machine as well).

h2. Whats inside the provisioning templates (Kickstart / jumpstart /preseed, pxelinux etc) ?

These files are all generated dynamically based on the setting of each host in Foreman, things like partition tables and root password can be unique per server.

if you want to see the kickstart/preseed etc you may use the spoof parameter, just point your browser to:

<pre>http://foreman/unattended/provision?spoof=123.321.123.321</pre>

* 123.321.123.321 is the hosts IP Address (the one you want to build).

* usually you want to see the page source, the browser might display the file in html which will result in hard to read output.

h2. Modifying/Creating the template

See [[TemplateWriting]]

h3. Template association to hosts

The guiding principle within Foreman is that we don't want to associate templates with hosts directly.

There are 4 ways to associate a template with a host

# Though a host group.

# Though an environment.

# Though a combination of a host group and an environment (such as web servers in development mode).

# Though an operating system.

Therefore, there are few steps which are required in order to relate hosts and templates.

# Make sure you define at least one operating systems.

# Create each template and associate the valid operating systems to it.

# Optionally, associate the template with hostgroups and/or environments.

# Edit the relevant operating system and define a default/fallback template for each relevant template type.

A special type of a template is called "PXE Default File" which is the default PXE template.

The included example will setup PXE menus for each configured host group (allowing you to deploy hosts without puppet if you require that functionality).

h3. Dynamic disk partitioning

It is possible to use a script (e.g a kickstart post script) instead of a static partition table.

see [[Dynamic disk partioning]]

*Note* Kickstart requires that Foreman port would be 80, therefor you should probably configure foreman using passenger or alternative technologies.

(Examples could be found in our reference "Foreman Puppet module":http://github.com/ohadlevy/puppet-foreman

h2. Specific distribution unattended installation details 

* [[Kickstart based unattended installation]]

* [[Preseed based unattended installation]]

* [[Solaris Unattended installation]]

* [[Yast based unattended installation]]

h2. [[gPXE]]

h2. Desactivation

Edit config/settings.yaml and add this line:

<pre>

:unattended: false

</pre>

and restart your foreman instance.

h2. See also :

see [[Provision KVM VM without DHCP]]

h2. Troubleshooting Flowchart

"Flowchart":http://www.gliffy.com/publish/3047598/