RETIRED, OpenStack Tacker Puppet Module
Go to file
ZhongShengping 032cc767be Deprecate oslo.messaging rpc_backend option parameter
Oslo.messaging uses the transport_url to represent the rpc and
notification messaging driver to use and its full configuration. The
rpc_backend configuration option is deprecated for removal and
should not gate oslo.messaging driver configuration options.

This patch:
* deprecate rpc_backend
* remove conditional check
* update spec tests
* add release note

Change-Id: Iad4cb043fac8690d3ab076fa54fe4e1bb2fea110
Closes-Bug: #1708976
2017-08-07 14:34:01 +08:00
lib/puppet Commiting a cookie cutter module sync set of files 2016-06-14 11:42:37 -04:00
manifests Deprecate oslo.messaging rpc_backend option parameter 2017-08-07 14:34:01 +08:00
releasenotes Deprecate oslo.messaging rpc_backend option parameter 2017-08-07 14:34:01 +08:00
spec Deprecate oslo.messaging rpc_backend option parameter 2017-08-07 14:34:01 +08:00
tests adding cookiecutter files 2015-11-07 06:14:05 -05:00
.gitignore Add basic structure for ReNo 2016-10-07 15:02:22 +00:00
.gitreview adding cookiecutter files 2015-11-07 06:14:05 -05:00
Gemfile Update tox configuration 2017-05-17 09:47:05 -06:00
LICENSE Commiting a cookie cutter module sync set of files 2016-06-14 11:42:37 -04:00
README.md Update URLs in documents according to document migration 2017-07-14 08:54:33 +08:00
Rakefile Commiting a cookie cutter module sync set of files 2016-06-14 11:42:37 -04:00
bindep.txt Update tox configuration 2017-05-17 09:47:05 -06:00
metadata.json Bump modules to next minor with -dev 2017-08-04 13:38:53 -06:00
setup.cfg Update URLs in documents according to document migration 2017-07-14 08:54:33 +08:00
setup.py Add basic structure for ReNo 2016-10-07 15:02:22 +00:00
test-requirements.txt Update openstackdocstheme>=1.16.0 2017-07-31 11:04:05 +08:00
tox.ini Add environment variable 2017-06-12 16:05:22 +08:00

README.md

Team and repository tags

Team and repository tags

tacker

Table of Contents

  1. Overview - What is the tacker module?
  2. Module Description - What does the module do?
  3. Setup - The basics of getting started with tacker
  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 tacker 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 not part of the core software. The module its self is used to flexibly configure and manage the NFV orchestration service for OpenStack.

Module Description

The tacker module is a thorough attempt to make Puppet capable of managing the entirety of tacker. This includes manifests to provision region specific endpoint and database connections. Types are shipped as part of the tacker module to assist in manipulation of configuration files.

Setup

What the tacker module affects

  • Tacker, the NFV orchestration service for OpenStack.

Installing tacker

tacker is not currently in Puppet Forge, but is anticipated to be added soon.  Once that happens, you'll be able to install tacker with:
puppet module install openstack/tacker

Beginning with tacker

To utilize the tacker module's functionality you will need to declare multiple resources.

Implementation

tacker

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

Limitations

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

Beaker-Rspec

This module has beaker-rspec tests

To run the tests on the default vagrant node:

bundle install
bundle exec rake acceptance

For more information on writing and running beaker-rspec tests visit the documentation:

Development

Developer documentation for the entire puppet-openstack project.

Contributors