Helper classes that utilize the core Puppet OpenStack modules
Go to file
Emilien Macchi e361c88af9 repos: disable EPEL by default
EPEL is not required when deploying OpenStack with RDO repositories.
In fact, it's causing some packaging conflicts for some dependencies,
and having it installed might cause some deployment failures.

To avoid this situation, let's disable its setup by default to improve
our user experience but add a note about why we disable it by default.

Change-Id: I2f06619e74f5e07889e29a82401344dda67ef51a
2016-09-28 16:12:46 -04:00
examples Add hash based repository management 2014-11-27 22:12:25 +11:00
files Bump UCA & RDO to Liberty GA 2015-11-02 16:58:42 -05:00
lib/puppet Fixes for new pacemaker versions 2015-02-10 11:17:46 +01:00
manifests repos: disable EPEL by default 2016-09-28 16:12:46 -04:00
releasenotes repos: disable EPEL by default 2016-09-28 16:12:46 -04:00
spec Fix unit tests for apt module 2016-09-26 11:24:31 -06:00
templates authfile: fix OS_IDENTITY_API_VERSION 2016-02-16 17:25:07 -05:00
.gitignore Add basic structure for ReNo 2016-03-14 08:33:40 -04:00
.gitreview Update .gitreview file for project rename 2015-06-12 23:12:30 +00:00
bindep.txt Move other-requirements.txt to bindep.txt 2016-08-12 21:09:59 +02:00
CHANGELOG.md Release 8.0.0 2016-03-23 16:07:40 -04:00
Gemfile Gemfile: rely on puppet-openstack_spec_helper for dependencies 2016-03-29 21:37:01 -04:00
LICENSE Synchronize LICENSE file with OpenStack projects 2015-04-20 09:29:08 -04:00
metadata.json Puppet OpenStack Newton RC2 2016-09-26 17:35:33 +00:00
Rakefile Use puppet-openstack_spec_helper for Rakefile & spec_helper_acceptance 2016-01-20 16:01:20 -05:00
README.md Merge "Change wiki to docs" 2016-06-03 16:46:13 +00:00
setup.cfg Add basic structure for ReNo 2016-03-14 08:33:40 -04:00
setup.py Add basic structure for ReNo 2016-03-14 08:33:40 -04:00
test-requirements.txt Add basic structure for ReNo 2016-03-14 08:33:40 -04:00
tox.ini Add basic structure for ReNo 2016-03-14 08:33:40 -04:00

openstack_extras

Table of Contents

  1. Overview - What is the openstack_extras module?
  2. Module Description - What does the module do?
  3. Setup - The basics of getting started with openstack_extras
  4. Implementation - An under-the-hood peek at what the module is doing
  5. Limitations - OS compatibility, etc.
  6. Development - Guide for contributing to the module
  7. Contributors - Those with commits
  8. Versioning - Notes on the version numbering scheme

Overview

The openstack_extras module is a part of OpenStack, an effort by the Openstack infrastructure team to provide continuous integration testing and code review for Openstack and Openstack community projects as part of the core software. The module itself is used to add useful utilities for composing and deploying OpenStack with the Openstack puppet modules.

Module Description

The openstack_extras module is intended to provide useful utilities to help with OpenStack deployments, including composition classes, HA utilities, monitoring functionality, and so on.

This module combines other modules in order to build and leverage an entire OpenStack software stack. This module replaces functionality from the deprecated stackforge/puppet-openstack module.

Setup

Installing openstack_extras

puppet module install openstack/openstack_extras

Beginning with openstack_extras

Instructions for beginning with openstack_extras will be added later.

Implementation

openstack_extras

openstack_extras is a combination of Puppet manifest and ruby code to delivery configuration and extra functionality through types and providers.

HA configuration for Openstack services

This module allows to configure Openstack services in HA. Please refer to the ha-guide for details. If you have a Corosync with Pacemaker cluster with several nodes joined, you may want to use an HA service provider which allows you to create the pacemaker resources for Openstack services and run them in HA mode. The example HA service configuration for keystone service:

openstack_extras::pacemaker::service { 'openstack-keystone' :
    ensure             => present,
    metadata           => {},
    ms_metadata        => {},
    operations         => {},
    parameters         => {},
    primitive_class    => 'systemd',
    primitive_provider => false,
    primitive_type     => 'openstack-keystone',
    use_handler        => false,
    clone              => true,
    require            => Package['openstack-keystone']
}

This example will create a pacemaker clone resource named p_openstack-keystone-clone and will start it with the help of systemd.

And this example will create a resource p_cinder-api-clone for Cinder API service with the given OCF script template from some cluster module:

  $metadata = {
    'resource-stickiness' => '1'
  }
  $operations = {
    'monitor'  => {
      'interval' => '20',
      'timeout'  => '30',
    },
    'start'    => {
      'timeout' => '60',
    },
    'stop'     => {
      'timeout' => '60',
    },
  }
  $ms_metadata = {
    'interleave' => true,
  }

  openstack_extras::pacemaker::service { 'cinder-api' :
    primitive_type      => 'cinder-api',
    metadata            => $metadata,
    ms_metadata         => $ms_metadata,
    operations          => $operations,
    clone               => true,
    ocf_script_template => 'cluster/cinder_api.ocf.erb',
  }

Limitations

  • Limitations will be added as they are discovered.

Development

Developer documentation for the entire puppet-openstack project.

Contributors

Versioning

This module has been given version 5 to track the puppet-openstack modules. The versioning for the puppet-openstack modules are as follows:

Puppet Module :: OpenStack Version :: OpenStack Codename
2.0.0         -> 2013.1.0          -> Grizzly
3.0.0         -> 2013.2.0          -> Havana
4.0.0         -> 2014.1.0          -> Icehouse
5.0.0         -> 2014.2.0          -> Juno
6.0.0         -> 2015.1.0          -> Kilo