Installing Enterprise 25 Free

These instructions describe how to install the latest version of CFEngine Enterprise 25 Free. This is the full version of CFEngine Enterprise, but the number of Hosts (clients) is limited to 25.

Note the following requirements:

To install this version of CFEngine Enterprise, your machine must be running a recent version of Linux. This installation script has been tested on RHEL 5 and 6, SLES 11, CentOS 5 and 6, and Debian 6 and 7.
You need a minimum of 2 GB of available memory and a modern 64 bit processor.
Plan for approximately 100MB of disk space per host. Due to MongoDB's pre-allocation strategy, always provide an extra 2G to 4G of disk space if you plan to bootstrap more hosts later.
You need a least two VMs/servers, one for the Policy Server and one for a Host (client).
Clients need to be able to comunicate with the server (port 5308 by default) in order to pull policy.
Policy server needs to be able to communicate with clients (port 5308 by default) in order to collect reports. If this is not possible because of NAT or firewall restrictions please see collect_calls under resource_type in body server access_rules.

Installation Overview

During the course of the instructions outlined in this guide, you will perform the following tasks:

Install CFEngine Enterprise onto a Policy Server and onto Hosts. A Policy Server (hub) is a CFEngine instance that contains promises (business policy) that get deployed to Hosts. Hosts are clients that retrieve and execute promises.
Bootstrap the Policy Server to itself and then bootstrap each of the Hosts to the Policy Server. Bootstrapping establishes a trust relationship between the Policy Server and all Hosts. Thus, business policy that you create in the Policy Server can be deployed to Hosts throughout your company. Bootstrapping completes the installation process.
Log in to the Mission Portal. The Mission Portal is a graphical user interface that allows you to verify the the actual state of all your Hosts, thus ensuring that your promises are being executed. By using the Design Center inside the Mission Portal, you can also define new desired states (business policies) for your infrastructure.
Try out the Tutorials. Links to three tutorials give you a head start on learning CFEngine.

1. Download and install Enterprise on a Policy Server

Note: Internet access is required from the host if you wish to use the quick install script.

Run the following script on your designated Policy Server (hub) 64-bit machine (32-bit is not supported on the Policy Server):

$ wget http://s3.amazonaws.com/cfengine.packages/quick-install-cfengine-enterprise.sh  && sudo bash ./quick-install-cfengine-enterprise.sh hub

This script installs the latest CFEngine Enterprise Policy Server on your machine.

Note: CFEngine enterprise expectes to be installed on to a fresh system and not be co-located with any other webserver or database server.

2. Bootstrap the Policy Server

The Policy Server must be bootstrapped to itself. Find the IP address of your Policy Server (type $ ifconfig).

Run the bootstrap command:

$ sudo /var/cfengine/bin/cf-agent --bootstrap <IP address of policy server>

Example: $ sudo /var/cfengine/bin/cf-agent --bootstrap 192.168.1.12

Upon successful completion, a confirmation message appears: "Bootstrap to '192.168.1.12' completed successfully!"

Type the following to check which version of CFEngine your are running:

$ /var/cfengine/bin/cf-promises --version

The Policy Server is installed.

3. Install Enterprise on Hosts

Install Enterprise on your designated Host(s) by running the script below. Per the Free 25 agreement, you can install Enterprise on 25 Hosts. Note that the Hosts must be on the same network as the Policy Server that you just installed in Step 2.

wget http://s3.amazonaws.com/cfengine.packages/quick-install-cfengine-enterprise.sh  && sudo bash ./quick-install-cfengine-enterprise.sh client

Note that this installation works on 64- and 32-bit machines.

4. Bootstrap the Host to the Policy Server

All Hosts must be bootstrapped to the Policy Server in order to establish a connection between the Host and the Policy Server. Run the same commands that you ran in Step 3.

$ sudo /var/cfengine/bin/cf-agent --bootstrap <IP address of policy server>

Example: $ sudo /var/cfengine/bin/cf-agent --bootstrap 192.168.1.12

The installation process is complete and CFEngine Enterprise is up and running on your system.

5. Log in to the Mission Portal

The Mission Portal is immediately accessible. Connect to the Policy Server through your web browser at:

http://<IP address of your Policy Server>

username: admin
password: admin

The Mission Portal runs TCP port 80 by default. (Click here to configure the Mission Portal to use HTTPS instead of HTTP.) During the initial setup, the Host(s) might take a few minutes to show up in the Mission Portal. Simply refresh the web page and login again if necessary.

Note: If you are running Enterprise with Vagrant, you must add the correct port: http://localhost: in your browser. The is the port-forwarder number you use in your Vagrantfile (e.g. policyserver.vm.network "forwarded_port", guest: 80, host: 8080; the port will be 8080).

Tutorials

Configure and deploy a policy using sketches in the Design Center. This tutorial teaches you how to configure and deploy business policy by using the Design Center application in the Mission Portal. Next, it shows you how to verify that your business policy is being activated by viewing the Reports in the Mission Portal.
Create a standalone policy (Hello World). Whereas the above tutorial uses pre-defined policy (called sketches) that you can modify in the Mission Portal, this tutorial teaches you how to create business policy (promises) on the command line. Here, you can get a taste of the CFEngine language as you create standalone and executable scripts.
Distribute files from a central location. Whereas the first tutorial in this list teaches you how to deploy business policy through the Mission Portal, this advanced, command-line tutorial shows you how to distribute policy files from the Policy Server to all pertinent Hosts.