OpenStack Mistral Puppet Module
Go to file
OpenStack Release Bot 4c990064ca Update TOX_CONSTRAINTS_FILE for stable/wallaby
Update the URL to the upper-constraints file to point to the redirect
rule on releases.openstack.org so that anyone working on this branch
will switch to the correct upper-constraints list automatically when
the requirements repository branches.

Until the requirements repository has as stable/wallaby branch, tests will
continue to use the upper-constraints list on master.

Change-Id: Icb86a7fb313ff642673c9a811fde89462484d21c
2021-04-01 09:23:56 +00:00
doc Update sphinx to the latest version 2021-03-27 15:31:57 +08:00
examples Convert all class usage to relative names 2019-12-08 23:10:58 +01:00
lib/puppet Use anchor to require necessary packages/services 2020-05-04 03:39:23 +09:00
manifests Add support for oslo_policy/enforce_new_defaults 2021-03-24 16:43:10 +09:00
releasenotes Add support for oslo_policy/enforce_new_defaults 2021-03-24 16:43:10 +09:00
spec Add support for oslo_policy/enforce_new_defaults 2021-03-24 16:43:10 +09:00
.gitignore Dissuade .gitignore references to personal tools 2018-10-08 11:39:24 +08:00
.gitreview Update .gitreview for stable/wallaby 2021-04-01 09:23:53 +00:00
.zuul.yaml Drop the tripleo-puppet-undercloud job 2021-03-26 15:37:24 +09:00
CHANGELOG.md Release 8.0.0 2016-03-23 16:07:26 -04:00
CONTRIBUTING.rst [ussuri][goal] Add CONTRIBUTING.rst 2020-05-10 22:41:47 +02:00
Gemfile Use openstack_spec_helper from zuul checkout 2020-08-30 22:59:24 +02:00
LICENSE Update LICENSE 2018-04-06 20:14:40 +08:00
README.md Add Puppet Litmus 2020-08-31 21:37:17 +02:00
Rakefile Use puppet-openstack_spec_helper for Rakefile & spec_helper_acceptance 2016-01-21 14:08:58 +00:00
bindep.txt modulesync: sync and add nodepool-bionic for beaker 2018-07-18 16:18:47 +02:00
metadata.json Prepare Wallaby RC1 2021-03-26 11:24:16 +08:00
setup.cfg Change openstack-dev to openstack-discuss 2018-12-02 18:20:07 +01:00
setup.py Add basic structure for ReNo 2016-03-14 08:30:46 -04:00
tox.ini Update TOX_CONSTRAINTS_FILE for stable/wallaby 2021-04-01 09:23:56 +00:00

README.md

Team and repository tags

Team and repository tags

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

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

What the mistral module affects

  • Mistral, the workflow service for OpenStack.

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 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>

mistral_workflow

The mistral_workflow provider allows the creation/update/deletion of workflow definitions using a source file (in YAML).

mistral_workflow { 'my_workflow':
  ensure          => present,
  definition_file => '/home/user/my_workflow.yaml',
  is_public       => true,
}

Or:

mistral_workflow { 'my_workflow':
  ensure => absent,
}

If you need to force the update of the workflow or change it's public attribute, use latest:

mistral_workflow { 'my_workflow':
  ensure          => latest,
  definition_file => '/home/user/my_workflow.yaml',
  is_public       => false,
}

Although the mistral client allows multiple workflow definitions per source file, it not recommended to do so with this provider as the mistral_workflow is supposed to represent a single workflow.

name

The name of the workflow; this is only used when deleting the workflow since the definition file specifies the name of the workflow to create/update.

definition_file

The path to the file containing the definition of the workflow. This parameter is not mandatory but the creation or update will fail if it is not supplied.

is_public

Specifies whether the workflow must be public or not. Defaults to true.

Limitations

  • All the mistral types use the CLI tools and so need to be ran on the mistral node.

Development

Developer documentation for the entire puppet-openstack project.

Contributors

Release Notes

Repository