- Overview - What is the tacker module?
- Module Description - What does the module do?
- Setup - The basics of getting started with tacker
- Implementation - An under-the-hood peek at what the module is doing
- Limitations - OS compatibility, etc.
- Development - Guide for contributing to the module
- Contributors - Those with commits
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.
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.
What the tacker module affects
- Tacker, the NFV orchestration service for OpenStack.
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
To utilize the tacker module's functionality you will need to declare multiple resources.
tacker is a combination of Puppet manifest and ruby code to delivery configuration and extra functionality through types and providers.
- All the tacker types use the CLI tools and so need to be ran on the tacker node.
This module has beaker-rspec tests
To run the tests on the default vagrant node:
bundle install
bundle exec rake acceptanceFor more information on writing and running beaker-rspec tests visit the documentation:
Developer documentation for the entire puppet-openstack project.