example42/puppet-horizon

Name: puppet-horizon

Owner: Example42

Description: Puppet module for Horizon

Created: 2013-12-15 10:15:34.0

Updated: 2014-09-25 23:24:29.0

Pushed: 2013-12-16 15:35:28.0

Homepage: null

Size: 116

Language: Ruby

GitHub Committers

User	Most Recent Commit	# Commits

Other Committers

User	Email	Most Recent Commit	# Commits

README

horizon

Table of Contents

1. Overview
2. Module Description
3. Setup
   • Resources managed by horizon module
   • Setup requirements
   • Beginning with module horizon
4. Usage
5. Operating Systems Support
6. Development

Overview

This module installs, manages and configures horizon.

Module Description

The module is based on stdmod naming standards version 0.9.0.

Refer to http://github.com/stdmod/ for complete documentation on the common parameters.

For a fully automated Puppet setup of OpenStack you'd better use the official StackForge modules. This module is intended to be a quick replacement for setups where you want to manage configurations based on plain template files or where you want to puppettize an existing OpenStack installation.

Setup

Resources managed by horizon module

• This module installs the horizon package
• Can manage all the configuration files (by default no file is changed)

Setup Requirements

• PuppetLabs stdlib module
• StdMod stdmod module
• Puppet version >= 2.7.x
• Facter version >= 1.6.2

Beginning with module horizon

To install the package provided by the module just include it:

    include horizon

The main class arguments can be provided either via Hiera (from Puppet 3.x) or direct parameters:

    class { 'horizon':
      parameter => value,
    }

The module provides a generic define to manage any horizon configuration file in /etc/horizon:

    horizon::conf { 'sample.conf':
      content => '# Test',
    }

Usage

• A common way to use this module involves the management of the main configuration file via a custom template (provided in a custom site module):

  class { 'horizon':
    config_file_template => 'site/horizon/horizon.conf.erb',
  }
  

• You can write custom templates that use setting provided but the config_file_options_hash paramenter

  class { 'horizon':
    config_file_template      => 'site/horizon/horizon.conf.erb',
    config_file_options_hash  => {
      opt  => 'value',
      opt2 => 'value2',
    },
  }
  

• Use custom source (here an array) for main configuration file. Note that template and source arguments are alternative.

  class { 'horizon':
    config_file_source => [ "puppet:///modules/site/horizon/horizon.conf-${hostname}" ,
                            "puppet:///modules/site/horizon/horizon.conf" ],
  }
  

• Recurse from a custom source directory for the whole configuration directory (/etc/horizon).

  class { 'horizon':
    config_dir_source  => 'puppet:///modules/site/horizon/conf/',
  }
  

• Use custom source directory for the whole configuration directory and purge all the local files that are not on the dir. Note: This option can be used to be sure that the content of a directory is exactly the same you expect, but it is desctructive and may remove files.

  class { 'horizon':
    config_dir_source => 'puppet:///modules/site/horizon/conf/',
    config_dir_purge  => true, # Default: false.
  }
  

• Use custom source directory for the whole configuration dir and define recursing policy.

  class { 'horizon':
    config_dir_source    => 'puppet:///modules/site/horizon/conf/',
    config_dir_recursion => false, # Default: true.
  }
  

• Do not trigger a service restart when a config file changes.

  class { 'horizon':
    config_dir_notify => '', # Default: Service[horizon]
  }
  

Operating Systems Support

This is tested on these OS:

• RedHat osfamily 6
• Ubuntu 12.04

Development

Pull requests (PR) and bug reports via GitHub are welcomed.

When submitting PR please follow these quidelines:

• Provide puppet-lint compliant code
• If possible provide rspec tests
• Follow the module style and stdmod naming standards

When submitting bug report please include or link:

• The Puppet code that triggers the error
• The output of facter on the system where you try it
• All the relevant error logs
• Any other information useful to undestand the context