Helper classes that utilize the core Puppet OpenStack modules
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
ZhongShengping 3dda38e19f Prepare Ussuri M3 2 days ago
doc [ussuri][goal] Cleanup for python 2.7 drop 1 month ago
examples Add hash based repository management 5 years ago
files repos: configure RDO Virtualization repository 3 years ago
lib/puppet Use puppet4 functions-api 1 year ago
manifests Merge "Remove old EPEL compat code" 5 days ago
releasenotes Update master for stable/train 6 months ago
spec Merge "Remove old EPEL compat code" 5 days ago
templates Set optional API version-related environment vars 1 year ago
.gitignore Dissuade .gitignore references to personal tools 1 year ago
.gitreview OpenDev Migration Patch 11 months ago
.zuul.yaml switch documentation job to new PTI 1 year ago
CHANGELOG.md Release 8.0.0 4 years ago
Gemfile Move to opendev 11 months ago
LICENSE Update LICENSE 2 years ago
README.md Fix Repository 11 months ago
Rakefile Use puppet-openstack_spec_helper for Rakefile & spec_helper_acceptance 4 years ago
bindep.txt modulesync: sync and add nodepool-bionic for beaker 1 year ago
metadata.json Prepare Ussuri M3 2 days ago
setup.cfg Change openstack-dev to openstack-discuss 1 year ago
setup.py Add basic structure for ReNo 4 years ago
tox.ini [ussuri][goal] Cleanup for python 2.7 drop 1 month ago

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. Release Notes - Release notes for the project
  8. Contributors - Those with commits
  9. Repository - The project source code repository
  10. 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.

Release Notes

Contributors

Repository

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