RETIRED, OpenStack Tacker Puppet Module
Go to file
Jiri Podivin 1dcde391e7 setuptools: Disable auto discovery
The latest release of setuptools 61.0 made a breaking change[1] and
because of this change 'pip install' fails with the following error.

~~~
error: Multiple top-level packages discovered in a flat-layout:
['lib', 'spec', 'manifests', 'releasenotes'].
~~~

Users that don't set 'packages', 'py_modules', or configuration'
are still likely to observe the auto-discovery behavior, which may
halt the build if the project contains multiple directories and/or
multiple Python files directly under the project root.

To disable auto discovery, one can do below in setup.py

~~~
setuptools.setup(..,packages=[],..)
~~~

or

~~~
setuptools.setup(..,py_modules=[],..)
~~~

[1] https://github.com/pypa/setuptools/issues/3197

Note setup.py is not used to install puppet modules. However it is used
to generate a release note, thus should be fixed.

Conflicts:
	setup.py

Signed-off-by: Jiri Podivin <jpodivin@redhat.com>
Change-Id: I00f6d92c02ac72626d1f39d8d9b3d3485fec488b
(cherry picked from commit 6f6227c979)
(cherry picked from commit 73be414d66)
2022-11-03 01:00:18 +09: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:21:57 +01:00
lib/puppet Use anchor to require necessary packages 2020-05-04 15:22:49 +09:00
manifests Add support for oslo_policy/enforce_new_defaults 2021-03-24 17:14:08 +09:00
releasenotes Add support for oslo_policy/enforce_new_defaults 2021-03-24 17:14:08 +09:00
spec Set fixture paths for unit tests 2021-06-03 06:11:40 +00:00
.gitignore Dissuade .gitignore references to personal tools 2018-10-08 11:39:25 +08:00
.gitreview Update .gitreview for stable/wallaby 2021-04-01 09:37:18 +00:00
.zuul.yaml Add Puppet Litmus 2020-08-31 21:58:43 +02:00
CONTRIBUTING.rst [ussuri][goal] Add CONTRIBUTING.rst 2020-05-10 22:53:23 +02:00
Gemfile Use openstack_spec_helper from zuul checkout 2020-08-30 23:06:09 +02:00
LICENSE Update LICENSE 2018-04-06 20:15:11 +08:00
README.md Add Puppet Litmus 2020-08-31 21:58:43 +02:00
Rakefile Commiting a cookie cutter module sync set of files 2016-06-14 11:42:37 -04:00
bindep.txt modulesync: sync and add nodepool-bionic for beaker 2018-07-18 16:20:16 +02:00
metadata.json Prepare Wallaby RC1 2021-03-26 11:24:17 +08:00
setup.cfg Change openstack-dev to openstack-discuss 2018-12-02 18:20:41 +01:00
setup.py setuptools: Disable auto discovery 2022-11-03 01:00:18 +09:00
tox.ini Update TOX_CONSTRAINTS_FILE for stable/wallaby 2021-04-01 09:37:22 +00: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
  8. Release Notes - Release notes for the project
  9. Repository - The project source code repository

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.

Development

Developer documentation for the entire puppet-openstack project.

Contributors

Release Notes

Repository