Forge Home


eNovance Openstack Module


8,574 latest version

2.3 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Version information

  • 2.2.0 (latest)
  • 2.1.0
  • 2.0.0
  • 1.3.0
  • 1.2.0
  • 1.1.0
released Oct 30th 2014
This version is compatible with:
  • Puppet Enterprise 3.x
  • Puppet 3.x
  • Debian, Ubuntu, CentOS, RedHat

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'eNovance-cloud', '2.2.0'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add eNovance-cloud
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install eNovance-cloud --version 2.2.0

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.



eNovance/cloud — version 2.2.0 Oct 30th 2014


Build Status Puppet Forge License

Table of Contents

  1. Overview - What is the cloud module?
  2. Module Description - What does the module do?
  3. Setup - The basics of getting started with puppet-openstack-cloud
  4. Implementation - An under-the-hood peek at what the module is doing
  5. Limitations - OS compatibility, etc.
  6. Getting Involved - How to go deeper
  7. Development - Guide for contributing to the module
  8. Contributors - Those with commits
  9. Release Notes - Notes on the most recent updates to the module


The OpenStack Puppet Modules are a flexible Puppet implementation capable of configuring the core OpenStack services:

Cinder, Glance and Nova can use Ceph as backend storage, using puppet-ceph.

Only KVM and QEMU are supported as hypervisors, for now. Neutron use ML2 plugin with GRE and Open-vSwitch drivers. Cinder has multi-backend support:

  • RBD (default)
  • NetAPP
  • iSCSI
  • EMC VNX direct
  • NFS Neutron supports:
  • ML2 plugin with OVS agent (GRE + VXLAN supported)
  • Cisco plugin with N1KV agent (non-ML2) Trove support is now experimental.

Puppet Modules are a collection of related contents that can be used to model the configuration of a discrete service.

These Puppet modules are based on the openstack documentation.

Module Description

There are a lot of moving pieces in OpenStack, consequently there are several Puppet modules needed to cover all these pieces. Each module is then made up of several class definitions, resource declarations, defined resources, and custom types/providers. A common pattern to reduce this complexity in Puppet is to create a composite module that bundles all these component type modules into a common set of configurations. The cloud module is doing this compositing and exposing a set of variables needed to be successful in getting a functional stack up and running.

Pre-module Dependencies

  • Puppet 3 or greater
  • Facter 1.6.1 or greater (versions that support the osfamily fact)

Notes about Puppet3

Puppet 3.x isn't yet available on Debian/RedHat stable osfamily, but hopefully puppet provides a Official repository, please see this page for the setup.


These modules have been fully tested on Ubuntu Precise and Debian Wheezy and RHEL 6.


What the cloud module affects

  • The entirety of OpenStack!

Installing Puppet

Puppet Labs provides two tools for getting started with managing configuration modeling with Puppet, Puppet Enterprise or its underlying opensource projects, i.e. Puppet and MCollective.

  • Puppet Enterprise is a complete configuration management platform, with an optimized set of components proven to work well together. Is free up to 10 nodes so if you're just using Puppet for OpenStack management this might just work perfectly. It will come configured with a handful of extra components that make for a richer experience, like a web interface for managing the orchestration of Puppet and certificate management.
  • Puppet manages your servers: you describe machine configurations in an easy-to-read declarative language, and Puppet will bring your systems into the desired state and keep them there. This is the opensource version of Puppet and should be available in your operating system's package repositories but it is generally suggested you use the yum or apt repositories from Puppet Labs if possible.

Consult the documentation linked above to help you make your decision but don't fret about the choice to much, opensource Puppet agents are compatible with Puppet Enterprise Puppet masters.

Optional Puppet features

The swift portions of this module needs Puppet's exported resources. Exported resources leverages the PuppetDB to export and share data across other Puppet managed nodes.

Installing latest unstable cloud module from source

cd /etc/puppet/modules
git clone cloud
cd cloud
gem install --no-ri --no-rdoc r10k
# a debian package is available in jessie
PUPPETFILE=./Puppetfile PUPPETFILE_DIR=../ r10k --verbose 3 puppetfile install

Pre-puppet setup

The things that follow can be handled by Puppet but are out of scope of this document and are not included in the cloud module.

Beginning with puppet-openstack-cloud

Utilization of this module can come in many forms. It was designed to be capable of deploying all services to a single node or distributed across several. This is not an exhaustive list, we recommend you consult and understand all the manifests included in this module and the core openstack documentation.


(more doc should be written here)


  • Deploys only with rabbitmq and mysql RPC/data backends.
  • Not backwards compatible with pre-2.x release of the cloud modules.

Getting Involved

Need a feature? Found a bug? Let us know!

We are extremely interested in growing a community of OpenStack experts and users around these modules so they can serve as an example of consolidated best practices of how to deploy openstack.

The best way to get help with this set of modules is to email the group associated with this project:

dev [at] enovance [dot] com

Issues should be opened here:


Release Notes