Overview

This document describes how to install Enterprise Chef, and all three of the current add-ons for
both Ubuntu & RHEL-based hosts. It includes a description of each command, and then the
command itself to accommodate for the dierent OSs, as well as example package filenames,
and a way to Verify successful installations for each component. NOTEs have also been added
to connect you with additional or option information on a given topic.
NOTE: Enterprise Chef can be configured in several ways to support a "Scaled Front End" (API
handling/web interface) topology, a "Scaled Back End" (node information/user databases)
topology, a "Standalone" topology (bother fron & back ends are on a single system), and a
"High Availability" topology (both scaled front & back ends).
This guide covers the installation of a Chef Server on a single system (referred to as
"Standalone").

Prerequisites
Greater detail regarding prerequisites for installing Enterprise Chef can be found on the Docs
Site but is meant to be a more concise document.
If you don't already have packages, you will need to contact Chef Sales or your sales
representative.
4 platform-specific packages are required (example package filenames given):
Enterprise Chef (private-chef-x.x.x-x)
Reporting (opscode-reporting-x.x.x-x)
Push Jobs (opscode-push-jobs-server_x.x.x-x)
Management Console (opscode-manage_x.x.x-x)
The push-jobs cookbook:
Downloaded directly from Amazon S3
Or from the Community Site
The separate push-jobs-client packages (example package filenames given):

opscode-push-jobs-client-x.x.x-x
Minimum System requirements:
Operating Systems:
Red Hat Enterprise Linux 6.2 or newer
CentOS 6.2 or newer
Ubuntu Linux 10.04, 11.04, 12.04
At Minimum:
4 cores, 2.0 GHz AMD 41xx/61xx or Intel Xeon 5000/E5 CPUs
4 GB RAM
5 GB free in /opt
5 GB free in /var
Ensure no previous versions of Open Source Chef or Enterprise Chef server are currently
installed. A fresh OS is recommended.
sudo yum list | grep -E 'chef|opscode'
sudo dpkg --get-selections | grep -E 'chef|opscode'

Installing Enterprise Chef

Before package install, the system's hostname must be a resolvable FQDN
See the 'About the Hostname' section of the Docs site prerequisite page.
Set the system's time correctly
See the 'NTP' section of the Docs site prerequisite page.
Open ports 80/443 to inbound trac on any local firewall present
Install the package:
sudo rpm -Uvh private-chef-x.x.x-x.elx.x86_64.rpm
sudo dpkg -i private-chef_x.x.x-x.ubuntu.xx.xx_amd64.deb

Reconfigure the server:

sudo private-chef-ctl reconfigure

Verify:
Run the built-in tests:
sudo private-chef-ctl test

Installing Reporting
On the Chef Server
Install the package:
sudo rpm -Uvh opscode-reporting-x.x.x-x.elx.x86_64.rpm
sudo dpkg -i opscode-reporting_x.x.x-x.ubuntu.xx.xx_amd64.deb

Reconfigure the reporting server:

sudo opscode-reporting-ctl reconfigure

Restart the reporting service:

sudo private-chef-ctl restart opscode-reporting

Verify:
Run the built-in tests:
sudo opscode-reporting-ctl test
Run chef-client -l info on a node and look for: INFO: Sending
resource update report near the end of the output ("Reporting" enabled in

chef-client 11.6.0 and later).

On the Workstation
Install the knife-push gem:
gem install knife-reporting

Verify:
Attempt to run the following:
knife runs --help NOTE: See the Docs site page for more instructions
on using the knife runs subcommand provided by knifereporting .

Installing Push Jobs

NOTE: Please see the Docs site if you require greater detail on the installation of Push Jobs.
On the Chef Server
Open ports 10000-10003 to inbound trac on any local firewall present
Install the package:
sudo rpm -Uvh opscode-push-jobs-server-x.x.x-x.elx.x86_64.rpm
sudo dpkg -i opscode-push-jobs-server_x.x.xx.ubuntu.xx.xx_amd64.deb

Reconfigure the Push Jobs server:

sudo opscode-push-jobs-server-ctl reconfigure

Reconfigure the Chef Server:

sudo private-chef-ctl reconfigure

Verify:
Run the built-in tests:
opscode-push-jobs-server-ctl test

On the Node
NOTE: the Push Jobs client can be installed either through the use of the push-jobs
cookbook (described in the On the Workstation section below), or via some either means,

using the push-jobs-client packages directly. At this time, Push Jobs can only be run on 64bit nodes.
Install via the push-jobs-client packages:
sudo rpm -Uvh opscode-push-jobs-client-x.x.x-x.elx.x86_64.rpm
sudo dpkg -i opscode-push-jobs-client_x.x.xx.ubuntu.xx.xx_amd64.deb

Verify:
Confirm that the Pushy Client Service is running on the node
On the Workstation
Install the knife-push gem:
gem install knife-push

Verify:
Attempt to run the following:
knife job --help NOTE: See the Docs site page for instructions on
using the knife job subcommand provided by knife-push .
(Optional) If you are installing the push-jobs-client via the push-jobs cookbook:
Download the push-jobs cookbook either from the community site using
knife cookbook site install push-jobs from within your chefrepo

Or directly from Amazon S3

Upload the push-jobs cookbook to the Chef Server
Create a role with the required attributes of the push-jobs cookbook defined:
"push_jobs": {
"whitelist": {
"chef-client": "/usr/bin/chef-client",
"reboot": "reboot"
},
"package_url": "http://<push-jobs-client-package-url>",
"package_checksum": "<push-jobs-client-package-checksum>"
}

NOTE: You'll need to designate a URL pointing at the given push-jobs-client

package you want this cookbook to install. Please see the documentation for the
cookbook for more information.
Upload that role to the Chef Server
Add the push-jobs cookbook to the run-list of nodes where Push Jobs will be

run
Run chef-client (to setup the "opscode-push-jobs-client" service on the node)
Verify:
Confirm that the Chef Server can communicate with the node:
Run knife node status on the workstation and look for node_name
available in the output

Installing the Management Console

Before package install, disable the legacy web UI in the private-chef configuration
file:
Create /etc/opscode/private-chef.rb with the follwoing contents:
opscode_webui['enable'] = false
fqdn_api "chef.chef-demo.com"

NOTE: Where "chef.chef-demo.com" is the FQDN of your Enterprise Chef Server.

Reconfigure the Chef Server:
sudo private-chef-ctl reconfigure

Install the package

sudo rpm -Uvh opscode-manage_x.x.x-x.elx.x86_64.rpm
sudo dpkg -i opscode-manage_x.x.x-x.ubuntu.xx.xx_amd64.deb

Reconfigure the Chef Server's web interface:

sudo opscode-manage-ctl reconfigure

Verify:
Visit Chef Server url:
Create first user through the "Sign up" link

Recap & Tips

You should now have a fully-functioning Chef Server up and running, with Reporting,
Management Console, and Push Jobs setup.
Create an alias for the private-chef-ctl command:
Add alias pcc='sudo private-chef-ctl' to your .bashrc or equivalent
Within documentation and package names, Enterprise Chef is still sometimes referred to
as "Private Chef". At version 1.4.6, "Private Chef" became "Enterprise Chef", and
versioning jumped to 11.0.0.
Please see the Docs site for documentation on upgrading individual add-ons or
upgrading the Enterprise Chef Server.

DISCLAIMER: These instructions were authored and tested with Enterprise Chef version
11.1.6, Reporting version 1.2.0, Management Console version 1.3.1, and the Push Jobs
Server version 1.1.2, the Push Jobs Client version 1.1.1, the knife-push Ruby gem version
0.5.0, the knife-reporting Ruby gem version 0.3.2, and the push-jobs cookbook 2.2.0. But
these instructions should apply to future versions of each.
If you have any questions of feedback on this document, please contact sales@getchef.com.
2008-2014 Chef. All
Rights Reserved.

1008 Western
Ave #600

Seattle, WA
98104

tel: 206508-4799

fax: 206223-2770