
In order to be able to take an action after all the packages of the module have been installed/updated or all the services have been started/restarted, we set a 'tuskar-package' and 'tuskar-service' tag for each package and service of this module. At the moment, there is a generic openstack tag that is not specific enough if one wants to take action upon a single module change. Use case : If an action needs to be taken after all the packages have been installed or updated : Package <| tag == 'tuskar-package' |> -> X Change-Id: Ie80cdb04a7b9d5adb87bf13ab1adee963adae6af
puppet-tuskar
6.0.0 - 2015.1 - Kilo
Table of Contents
- Overview - What is the tuskar module?
- Module Description - What does the module do?
- Setup - The basics of getting started with tuskar
- 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
Overview
The tuskar 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 as part of the core software. The module itself is used to flexibly configure and manage the management service for Openstack.
Module Description
Setup
What the tuskar module affects:
- tuskar, the management service for Openstack.
Implementation
tuskar
tuskar is a combination of Puppet manifest and ruby code to delivery configuration and extra functionality through types and providers.
Limitations
Development
Developer documentation for the entire puppet-openstack project.
Contributors
Description