Puppet Enterprise 2016.2


In this guide, you’ll install the puppetlabs-apache module, a Puppet Enterprise-supported module. Modules contain classes, which are named chunks of Puppet code and are the primary means by which Puppet Enterprise configures and manages nodes. While you can use any module available on the Forge, PE customers can take advantage of supported modules. These modules are designed to make common services easier, and are tested and maintained by Puppet.

In the module writing basics quick start guide, you’ll learn more about modules, including customizing and writing your own modules on either the Windows or *nix platform.

Prerequisites: This guide assumes you’ve already installed a monolithic PE deployment, and have installed at least one *nix agent node.

Installing a Forge module

To install the Apache module, run: puppet module install puppetlabs-apache. The result looks like this:

    Preparing to install into /etc/puppetlabs/code/environments/production/modules ...
    Notice: Downloading from http://forgeapi.puppetlabs.com ...
    Notice: Installing -- do not interrupt ...
    └── puppetlabs-apache (v1.1.1)

To view detailed info about the module, see the Apache module on the Forge.

You have just installed a Puppet module! All of the classes in the module are now available to be added to the console and assigned to nodes.

Note about module directories

By default, Puppet keeps modules in /etc/puppetlabs/code/environments/production/modules. This includes modules installed by PE, those that you download from the Forge, and those you write yourself.

Note: PE also creates another module directory: /opt/puppetlabs/puppet/modules. Don’t modify anything in or add modules of your own to this directory.

Next: Adding classes to Puppet agent nodes (*nix)

Back to top
The page rank or the 1 our of 5 rating a user has given the page.
The email address of the user submitting feedback.
The URL of the page being ranked/rated.