In the previous article we installed and configured Puppet. We have also set up puppet to write host configuration data to a PostgreSQL database using storedconfig.

Today, I’m going to show you how to install and configure:

  • Foreman
  • Foreman’s smart-proxy
  • Integrate smart-proxy with DHCP/TFTP/DNS/Puppet


Install Foreman from the latest development branch

Installing Foreman from RPM has its own advantages, but currently the situation is such that the packaged (Stable) version lags quite far behind the development branch. At the time of writing, the development branch is quite stable and comes with a lot of new features, that the stable release (0.4) is lacking.

Another advantage of installing directly from the Github repository is that you’ll get better understanding of how the system is put together and how it works.

Foreman dependencies

Foreman 0.5 uses Rails 3 and uses bundler to manage the packages, so let’s install this Gem:

# gem install bundle

We also need to install libvirt packages and their dependencies. If you are using RHEL distribution and it is subscribed to RHN, you can use official RHN RHEL Virtualisation Server 5 channel to install these packages.

Alternatively, if you’re using CentOS or do not have access to RHN for some reason, you can install CentOS RPMs directly, which works fine on RHEL distribution too:

# wget http://mirror.centos.org/centos-5/5/os/x86_64/CentOS/xen-libs-3.0.3-135.el5.x86_64.rpm
# wget http://mirror.centos.org/centos-5/5/os/x86_64/CentOS/xen-devel-3.0.3-135.el5.x86_64.rpm
# wget http://mirror.centos.org/centos-5/5/os/x86_64/CentOS/libvirt-0.8.2-25.el5.x86_64.rpm
# wget http://mirror.centos.org/centos-5/5/os/x86_64/CentOS/libvirt-devel-0.8.2-25.el5.x86_64.rpm
# yum install *rpm --nogpgcheck

Getting the latest Foreman code

Now with all prerequisites sorted, let’s get the latest Foreman build from Github:

# export GIT_SSL_NO_VERIFY=true
# export PATH=/usr/pgsql-9.1/bin/:$PATH
# cd /opt
# git clone https://github.com/theforeman/foreman.git -b develop

The next code snippet shows how to build the Foreman using bundler. You can see that I’m excluding some options, such as MySQL and SQLite support, as well as Development and Test components.

If you are using MySQL instead of PostgreSQL, you will have to modify the --without option to exclude postgresql instead of mysql.

For testing purposes you might want to leave SQLite, and remove the other two databases.

# cd foreman
# yum install libxml2 libxml2-devel libxslt libxslt-devel
# bundle install --without mysql sqlite test development --path vendor
# cp config/settings.yaml.example config/settings.yaml

Now we need to initialise the database by creating all required tables and updating them with initial data. In Rails world this is achieved by running DB migration scripts and then starting up the Foreman service, as per below:

# RAILS_ENV=production bundle exec rake db:migrate
# RAILS_ENV=production ./script/rails s

Now that we have a running Foreman instance, try connecting to it (http://your-foreman-server:8140/) and see if you get a response from a working Rails application. You should see a Foreman dashboard, similar to the below:

Configure Passenger

It is OK to use default WEBrick web server for quick tests, but you don’t really want to do that in the production environment. So just as we did with Puppet, let’s run Foreman from within Passenger.

The configuration is very similar to Puppet configuration. Assuming that you are using Apache, create /etc/httpd/conf.d/foreman.conf with the following contents:

<VirtualHost *:80>
    DocumentRoot /opt/foreman/public
    RailsAutodetect On
    AddDefaultCharset UTF-8
</VirtualHost>

<VirtualHost *:443>
    RailsAutoDetect On
    RailsEnv production
    DocumentRoot /opt/foreman/public

    # Use puppet certificates for SSL
    SSLEngine On
    SSLCertificateFile /var/lib/puppet/ssl/certs/__your_servername__.pem
    SSLCertificateKeyFile /var/lib/puppet/ssl/private_keys/__your_servername__.pem
    SSLCertificateChainFile /var/lib/puppet/ssl/ca/ca_crt.pem
    SSLCACertificateFile /var/lib/puppet/ssl/ca/ca_crt.pem
    SSLVerifyClient optional
    SSLOptions +StdEnvVars
    SSLVerifyDepth 3
</VirtualHost>

Note! Make sure you point to the existing certificate and certificate key files. We created those in the previous post, while installing and setting up Puppet server.

Integrate Puppet and Foreman

There are couple of steps needed to integrate Puppet and Foreman, so that each could see and use others information.

Sending Puppet reports to Foreman

Once a Puppet client finishes its run, it will report back to Puppet master with the status. Puppet allows you to define hooks, so that every time when a report comes back, a custom script is fired. We are going to create and register a script that’ll put the information into the Foreman’s DB.

The source of this script can be found on Foreman Github repository, so check for an updated version.

Add the following code to a file called /usr/lib/ruby/site_ruby/1.8/puppet/reports/foreman.rb. You will have to create this file, as it wouldn’t exist:

$foreman_url='http://__foreman_host__'

require 'puppet'
require 'net/http'
require 'net/https'
require 'uri'

Puppet::Reports.register_report(:foreman) do
    Puppet.settings.use(:reporting)
    desc "Sends reports directly to Foreman"

    def process
      begin
        uri = URI.parse($foreman_url)
        http = Net::HTTP.new(uri.host, uri.port)
        if uri.scheme == 'https' then
          http.use_ssl = true
          http.verify_mode = OpenSSL::SSL::VERIFY_NONE
        end
        req = Net::HTTP::Post.new("#{uri.path}/reports/create?format=yml")
        req.set_form_data({'report' => to_yaml})
        response = http.request(req)
      rescue Exception => e
        raise Puppet::Error, "Could not send report to Foreman at #{$foreman_url}/reports/create?format=yml: #{e}"
      end
    end
end

Now tell Puppet to run this script by modifying /etc/puppet/puppet.conf:

[main]
    reports=log, foreman

Telling Puppet to use Foreman as ENC

ENC means External Node Classifier, and it is a way to provide information about a node to Puppet. The information provided includes Puppet classes that need to be applied to a node, and Puppet configuration parameters.

One way to manage node configuration is by using nodes.pp Puppet configuration file, but Foreman is already holding all that information in its data structures, so we’ll make use of it.

To do so, we need to create a script that Puppet would call to get the node information. It can be any script as long as it returns valid configuration in YAML format. The script should accept a hostname as parameter.

Create /etc/puppet/node.rb with this code in it:

#!/usr/bin/env ruby
# a simple script which fetches external nodes from Foreman
# you can basically use anything that knows how to get http data, e.g. wget/curl
 etc.

# Foreman url
foreman_url="http://__foreman_host__" 

require 'net/http'

foreman_url += "/node/#{ARGV[0]}?format=yml" 
url = URI.parse(foreman_url)
req = Net::HTTP::Get.new(foreman_url)
res = Net::HTTP.start(url.host, url.port) { |http|
  http.request(req)
}

case res
when Net::HTTPOK
  puts res.body
else
  $stderr.puts "Error retrieving node %s: %s" % [ARGV[0], res.class]
end

Next step is to tell Puppet what script it needs to call when it needs to get information about a node. We can do this by adding the following configuration to /etc/puppet/puppet.conf:

[master]
  external_nodes = /etc/puppet/node.rb
  node_terminus  = exec

Install Foreman Proxy (smart-proxy)

So we have a running and configured instance of Foreman, but the system is not ready yet for host provisioning. Most of the operation that Foreman performs, like adding hosts to DHCP, creating PXEboot files and managing DNS, are done using smart-proxy components, also referred to as foreman-proxy. I’ll use these terms interchangeably.

Installing the latest Foreman-Proxy code is very simple, just follow the steps below:

# cd /opt
# git clone git://github.com/theforeman/smart-proxy.git
# useradd -r foreman-proxy
# usermod -G puppet foreman-proxy
# usermod -G foreman-proxy puppet
# chown -R foreman-proxy smart-proxy
# chown -R foreman-proxy.root /var/log/foreman-proxy
# gem install sinatra -v 1.0
# gem install json
# cp /opt/smart-proxy/config/settings.yml.example /opt/smart-proxy/config/settings.yml
# mkdir /var/run/foreman-proxy/
# su - foreman-proxy
$ /opt/smart-proxy/bin/smart-proxy

You should have a working smart-proxy, albeit without any capabilities. You can test it with your browser by going to http://__your_host__:8443/features URL. You should see an empty ‘Supported features’ list.

In this example I’m starting smart proxy directly running the script. Although it does ‘daemonise’ itself properly, you might want to create a proper init.d script.

Configure Smart-Proxy to control Puppet

Foreman Proxy needs to be able to run Puppet certificate management commands. While we’re at it, we also enable remote Puppet run for the Foreman user.

Run visudo as root user and add the following configuration:

Defaults:foreman !requiretty
Defaults:foreman-proxy !requiretty
foreman ALL=(ALL) NOPASSWD:/usr/sbin/puppetrun
foreman-proxy ALL=(ALL) NOPASSWD:/usr/sbin/puppetca*

You also need to tell smart proxy that it is supposed to manage Puppet by making these changes to /opt/smart-proxy/config/settings.yml:

:puppetca: true
:puppet: true
:puppet_conf: /etc/puppet/puppet.conf

Adding support for TFTP and DHCP management

Obviously, you can separate TFTP and DHCP services, but they typically are not resource hungry and because they are both involved in PXE boot process it makes sense to run these two services on the same host. So I will deal with their configuration in one section.

TFTP configuration

Install TFTP server and SysLinux package, which will provide PXELinux boot image:

# yum install -y tftp-server syslinux
# cp /usr/lib/syslinux/pxelinux.0 /tftpboot

Make sure you enable TFTP server in xinetd configuration by modifying /etc/xinetd.d/tftp and restarting xinetd service:

server_args             = -s /tftpboot
disable                 = no

Finally, tell Foreman Proxy that it is now in charge for TFTP management by changing /opt/smart-proxy/config/settings.yml:

:tftp: true
:tftproot: /tftpboot

Add DHCP support

The steps needed to get DHCP working and controlled by the smart-proxy are:

  • Generate shared key for DHCP management via OMAPI protocol
  • Create DHCP configuration that allows remote subnet management
  • Enable DHCP support in smart-proxy configuration and provide the key details

Let’s install some required packages, including a Ruby Gem:

# yum install -y libffi libffi-devel bind
# gem install net-ping

Generate a key (this will create a couple of files, you can delete them):

# dnssec-keygen -r /dev/urandom -a HMAC-MD5 -b 512 -n HOST omapi_key
# cat Komapi_key.+*.private |grep ^Key|cut -d ' ' -f2-
[..key..]

Create a DHCP configuration filei /etc/dhcpd.conf. Make sure you put the details representing your network configuration, ie subnet, netmask, router IPs, etc:

omapi-port 7911;
key omapi_key {
  algorithm HMAC-MD5;
  secret "[..key..]";
};
omapi-key omapi_key;

allow booting;
allow bootp;

subnet 192.168.0.0 netmask 255.255.255.0 {
    range 192.168.0.100 192.168.0.200;
    option domain-name-servers 192.168.0.1;
    option domain-name "my.domain";
    option routers 192.168.0.254;
    filename "/pxelinux.0";
    next-server 192.168.0.10;
}

And finally, tell smart-proxy that it now manages DHCP daemon (in /opt/smart-proxy/config/settings.yml):

:dhcp: true
:dhcp_vendor: isc
:dhcp_config: /etc/dhcpd.conf
:dhcp_leases: /var/lib/dhcpd/dhcpd.leases
:dhcp_key_name: omapi_key
:dhcp_key_secret: [..key..]

Restart the foreman-proxy process, and you should see DHCP enabled if you go to http://__your_host__:8443/features.

Add DNS support (Bind)

Now, when you add a new host, Foreman will contact the smart-proxy and do two things: firstly it will get the next available IP, which will be suggested for you. Secondly, when you click on save button, it will instruct smart-proxy to add the IP to DHCP leases file.

Let’s go even further, and use smart-proxy to create an entry in DNS zone file.

The process is very similar to DHCP configuration:

  • Generate a secret key which is shared between smart-proxy and DNS server
  • Instruct DNS server to allow remote management
  • Configure smart-proxy by telling it that it is now responsible for DNS management

Install Bind and configure it (you will have to refer to Bind configuration guide for the exact details):

# yum install -y bind bind-utils bind-chroot bind-libs

Create shared keys. Unlike with DHCP, you will have to keep the generated files in the directories they were created. I’m also showing what the result files may look like:

# cd /var/named/chroot/etc
# dnssec-keygen -a HMAC-MD5 -b 128 -n HOST foreman

# cat Kforeman.+157+51238.key
foreman. IN KEY 512 3 157 [..key..]
# cat Kforeman.+157+51238.private
Private-key-format: v1.2
Algorithm: 157 (HMAC_MD5)
Key: [..key..]

Create a new DNS key file (called /var/named/chroot/etc/foreman.key), which will be included in the main configuration:

key "foreman" {
        algorithm hmac-md5;
        secret "[..key..]";
};

Make it readable by the foreman user:

# chmod o+r /var/named/chroot/etc/foreman.key

Modify DNS zone configuration (/var/named/chroot/etc/named.conf), so that remote management is allowed:

include "/etc/foreman.key";
zone "0.168.192.in-addr.arpa." IN {
        type master;
        file "192.168.0.db";
        allow-update { key "foreman"; };
};

zone "my.domain." IN {
        type master;
        file "my.domain.db";
        allow-update { key foreman; };
};

And tell Foreman-proxy to manage DNS by modifying /opt/smart-proxy/config/settings.yml:

:dns: true
:dns_key: /var/named/chroot/etc/Kforeman.+157+51238.private

Restart the foreman-proxy process and test if you can create a new node.

Troubleshooting

As you can see, the installation process although pretty straight forward, but has a lot of steps. So there are a lot of points where things could go wrong. But fear not, it’s not that difficult and scary as it may seem at first.

Some of the things to look at if things do not work the first time:

  • Gem file permissions. Some systems have very restrictive umask settings, and all gems installed by root user will not be available to other users (foreman, puppet, foreman-proxy). Check files in /usr/lib/ruby/site_ruby/1.8/.
  • Other file permissions. Check that other users that are involved in the process can read (and write where appropriate) all required files, in particular: /tftpboot/*, /var/named/chroot/etc/*, /etc/dhcpd.conf, and /var/lib/dhcpd/dhcpd.leases.
  • When you make any changes, don’t forget to restart all processes that are involved: httpd, smart-proxy, dhcpd, named.

If still stuck, hop on to #theforeman IRC channel on freenode.net, the bunch there is really friendly and helpful (I know, I’ve been asking a lot of stupid questions, and they still tolerate me :) )

Further reading

Visit these websites for more information:



comments powered by Disqus

Published

05 April 2012

Tags