UPDATE!

This repository is no longer in use by the Puppet SE Team, and will be official Archived on Friday, July 1st. It will then be deleted on Friday, July 15th. If you are using any of the included code in any way, please take efforts to preserver your access to the code at your earlier convenience.

Thanks! - The Puppetlabs SE Team

Vagrant Puppet Enterprise Stack

Table of Contents

1. Overview
2. Prerequisites
3. Puppet Master Setup
   • Quickstart
     • Links
   • Next Steps

Overview

This project provides a demo environment for running a Puppet master and several agents.

Prerequisites

This tool is built on top of a few different technologies, mainly VirtualBox and Vagrant, so you'll need to ensure that those are present before you continue. You'll also need to have the Git tools installed to checkout the repository.

1. Install Virtual Box.
2. Install Vagrant.
3. Install the required Vagrant plugins:

• $ vagrant plugin install oscar
• $ vagrant plugin install vagrant-hosts
• $ vagrant plugin install vagrant-reload

4. Install Optional Vagrant Plugins:

• $ vagrant plugin install vagrant-multiprovider-snap (Required for snapshot functionaility in Vagrant versions less than 1.8, functionaility is part of Vagrant core from v1.8 by utilising the "vagrant snapshot" command )

In addition, keep in mind the raw cpu and memory requirements. The master is 2CPU and 8G of memory.

Puppet Master Setup

Quickstart

After getting the pre-reqs setup, run scripts/init.sh. This will stand up the master and all configured agents. For all agents, the will be snapshotted after provisioning and then shutdown. The master will be left running. To complete the setup run vagrant hosts list and update your hosts file.

The new master is already fully deployed, running with a hostname of master.inf.puppet.vm. In additon, an internal Git server is running on the new master.

Links

• Puppet Enterprise Console.
• Git Server.

Credentials

SSH:

• vagrant ssh /master/

Enterprise Console:

• user: admin
• password: puppetlabs

Git Server:

• user: puppet
• password: puppetlabs

Next Steps

Once the master is up and running, you'll need to add your license key to the master. Code manager deployments will not work successfully until you add a license key because there are some PE only modules in use.

Optional: Login to the Git server (here) and update the puppet users ssh keys with your own public so that you can make updates to the control-repo.