Skip to content
Snippets Groups Projects

puppet-iaas

Table of Contents

  1. Overview
  2. Module Description - What the module does and why it is useful
  3. Setup - The basics of getting started with iaas
  4. Usage - Configuration options and additional functionality
  5. References
  6. Limitations

Overview

This Puppet module allows deploying a highly-available installation of OpenStack Juno on commodity servers supporting multiple networks architecture.

The present modlue is part of the outcomes of the Open City Paltform (OCP) National Project.

The iaas module derive fron the puppet-iaas module authored by Qunentin Machu.

Module Description

Different types of nodes are created by the deployment :

Setup

Setup Requirements

This module assumes nodes running Ubuntu 14.04 (Trusty) with either Puppet Enterprise or Puppet.

More information related to the setup requirement are available in the present guide Setup requirements

This module depends on Hiera.

Beginning with iaas module

To ensure high availability, three Service nodes, three Storage nodes, two Controller nodes and two Network nodes must be deployed, be sure to have ten available servers. In addition, a number of Compute nodes are also to be available for the deployment.

Usage

The nodes should be deployed in the following order : Service nodes, Storage nodes, Controller nodes, Network nodes and then Compute nodes.

Hiera Configuration

The first step to using the iaas module is to configure hiera with specific settings pointing to your installation. In this module, the examples directory contains sample 'common.yaml' file with all of the settings required by this module. These configuration options include Service settings, Storage settings, Network settings, OpenStack core settings and related passwords. If any of these settings are undefined or not properly set, your deployment may fail.

Site configuration

The second step to using the iaas module is to configure manifest file with specific settings pointing to your installation. In this module, the examples directory contains sample 'site.pp' file according to your deployment. These configuration options include Service variables and node-specific configuration settings. If any of these settings are undefined or not properly set, your deployment may fail.

Node balancing

In order to balance requests across the different nodes, HAproxy and Keepalived have to be configured properly. Make sure also that node hostname con be asily resolved.

References

In order to devop and test the module and its components, the following official guides and sites have been considered:

Limitations

This module is still under development.