OpenStack Mistral Puppet Module
Go to file
Venkata Mahesh Jonnalagadda 87c7e5d22f Provide default service_name for keystone endpoint
This change updates the mistral::keystone::auth class to include a default
service_name of 'mistral' so that if a user changes the auth_name, the
service is still created as being related to 'mistral'. This improves the
user experiance when they want to customize the usernames for services.

Closes-bug: #1590040

Change-Id: I94d5429a21acea5d9fe8812f85fb65cfeb3094a3
2016-06-10 07:03:58 -04:00
lib/puppet Reflect provider change in puppet-openstacklib 2016-01-04 10:23:20 -05:00
manifests Provide default service_name for keystone endpoint 2016-06-10 07:03:58 -04:00
releasenotes Provide default service_name for keystone endpoint 2016-06-10 07:03:58 -04:00
spec Provide default service_name for keystone endpoint 2016-06-10 07:03:58 -04:00
templates Split log file of mistral services 2016-01-21 10:54:10 +02:00
tests puppet-mistral: initial commit 2015-08-09 10:00:45 +00:00
.gitignore Add basic structure for ReNo 2016-03-14 08:30:46 -04:00
.gitreview Added .gitreview 2015-07-24 11:07:53 +00:00
CHANGELOG.md Release 8.0.0 2016-03-23 16:07:26 -04:00
Gemfile Gemfile: rely on puppet-openstack_spec_helper for dependencies 2016-03-29 21:36:40 -04:00
LICENSE puppet-mistral: initial commit 2015-08-09 10:00:45 +00:00
README.md Fix markdown format typo 2016-06-01 12:53:55 +08:00
Rakefile Use puppet-openstack_spec_helper for Rakefile & spec_helper_acceptance 2016-01-21 14:08:58 +00:00
metadata.json Switch mistral to use puppet-oslo module 2016-04-18 13:51:35 +03:00
other-requirements.txt Add other-requirements.txt for bindep 2016-05-19 22:15:55 +00:00
setup.cfg Add basic structure for ReNo 2016-03-14 08:30:46 -04:00
setup.py Add basic structure for ReNo 2016-03-14 08:30:46 -04:00
test-requirements.txt Add basic structure for ReNo 2016-03-14 08:30:46 -04:00
tox.ini Add basic structure for ReNo 2016-03-14 08:30:46 -04:00

README.md

mistral

Table of Contents

  1. Overview - What is the mistral module?
  2. Module Description - What does the module do?
  3. Setup - The basics of getting started with mistral
  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

Overview

The Mistral module itself is a workflow service for OpenStack cloud.

Module Description

The mistral module is an attempt to make Puppet capable of managing the entirety of mistral.

Setup

Beginning with mistral

To use the mistral module's functionality you will need to declare multiple resources. This is not an exhaustive list of all the components needed; we recommend you consult and understand the core of openstack documentation.

Implementation

Mistral

puppet-mistral is a combination of Puppet manifests and ruby code to deliver configuration and extra functionality through types and providers.

Types

mistral_config

The mistral_config provider is a children of the ini_setting provider. It allows one to write an entry in the /etc/mistral/mistral.conf file.

mistral_config { 'DEFAULT/use_syslog' :
  value => false,
}

This will write use_syslog=false in the [DEFAULT] section.

name

Section/setting name to manage from mistral.conf

value

The value of the setting to be defined.

secret

Whether to hide the value from Puppet logs. Defaults to false.

ensure_absent_val

If value is equal to ensure_absent_val then the resource will behave as if ensure => absent was specified. Defaults to <SERVICE DEFAULT>

Beaker-Rspec

This module has beaker-rspec tests

To run:

bundle install
bundle exec rspec spec/acceptance

Development

Developer documentation for the entire puppet-openstack project.

Contributors