Helper classes that utilize the core Puppet OpenStack modules
Go to file
Tobias Urdin f9acf4a20e Remove PE requirement from metadata.json
The PE requirement in metadata.json is not
supported anymore and puppet-lint will throw:

The 'pe' requirement is no longer supported by the Forge.

Change-Id: I317944576781be64e1d7d712e2a655d95dea795b
(cherry picked from commit 7462927491)
(cherry picked from commit 67355a7da5)
2020-04-10 16:33:34 +09:00
examples Add hash based repository management 2014-11-27 22:12:25 +11:00
files repos: configure RDO Virtualization repository 2016-09-30 08:45:07 -04:00
lib/puppet Fixes for new pacemaker versions 2015-02-10 11:17:46 +01:00
manifests Set show_diff to false for auth_file 2020-02-14 00:13:54 +01:00
releasenotes Use Python to compute release notes version 2017-08-30 13:46:08 -07:00
spec latest unit test failed 2018-08-16 12:22:26 +00:00
templates Set OS_INTERFACE and OS_ENDPOINT_TYPE in auth file 2018-02-01 19:05:40 +01:00
.gitignore Add basic structure for ReNo 2016-03-14 08:33:40 -04:00
.gitreview OpenDev Migration Patch 2019-04-19 19:42:24 +00:00
.zuul.yaml import zuul job settings from project-config 2018-08-31 08:40:09 -04:00
CHANGELOG.md Release 8.0.0 2016-03-23 16:07:40 -04:00
Gemfile Update Gemfile to pull spec_helper from stable/queens 2018-08-16 12:22:49 +00:00
LICENSE Synchronize LICENSE file with OpenStack projects 2015-04-20 09:29:08 -04:00
README.md Update to the latest address in README 2017-09-21 12:03:38 +08:00
Rakefile Use puppet-openstack_spec_helper for Rakefile & spec_helper_acceptance 2016-01-20 16:01:20 -05:00
bindep.txt Add Puppet package to bindep, for module build 2017-10-27 13:14:58 -07:00
metadata.json Remove PE requirement from metadata.json 2020-04-10 16:33:34 +09:00
setup.cfg Merge "Change author in setup.cfg" 2017-12-01 23:33:41 +00:00
setup.py Add basic structure for ReNo 2016-03-14 08:33:40 -04:00
test-requirements.txt Remove pinned versions from test-requirements.txt 2018-01-16 12:29:47 +08:00
tox.ini Update UPPER_CONSTRAINTS_FILE for stable/queens 2018-02-20 22:17:27 +00:00

README.md

Team and repository tags

Team and repository tags

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