x
/
puppet-tuskar
Code Issues Proposed changes
RETIRED, OpenStack Tuskar Puppet Module
46 Commits 1 Branch 4 Tags 452 KiB
Go to file
Emilien Macchi 79cb000d22 Try to use zuul-cloner to prepare fixtures 
In OpenStack Infra, we would like to run Puppet unit tests that
sometimes depends on other Puppet OpenStack modules.
Example: a patch in puppet-openstacklib that needs to be tested in puppet-nova.

This patch modifies the Rakefile to:
* clean spec_prep and spec_clean Rake tasks
* use openstack/puppet-openstack-integration/install_modules_unit.sh script
  to clone modules.
* do not use .fixtures.yaml file to clone modules and rely on
  zuul-cloner or git.
* Add openstack/ in gitignore so we never commit the
  puppet-openstack-integration repository (can happen when spec_clean
  did not run but you want to submit the patch anyway)
* Allow to run a custom Puppetfile if PUPPETFILE env is exported. It
  will allow people to test the module with the dependencies they like,
  feature we had with .fixtures.yaml.

Also add 'r10k' to Gemfile.

That way, we will be able to use zuul dependencies and run tests accross
modules like we do with functional testing.

Change-Id: I154e5ab5623b932fc3c550f7969a39993f38a3cf
 		2015-10-08 15:21:50 -07:00
examples Add Puppet 4.x lint checks 2015-02-25 05:12:22 +01:00
lib/puppet Reflect provider change in puppet-openstacklib 2015-08-19 10:01:40 +02:00
manifests Rely on autorequire for config resource ordering 2015-08-12 19:28:03 +02:00
spec Merge "Initial msync run for all Puppet OpenStack modules" 2015-09-11 16:10:50 +00:00
.gitignore Try to use zuul-cloner to prepare fixtures 2015-10-08 15:21:50 -07:00
.gitreview Update .gitreview file for project rename 2015-06-12 23:12:30 +00:00
CHANGELOG.md Prepare 6.0.0 release 2015-07-09 10:29:02 -04:00
Gemfile Try to use zuul-cloner to prepare fixtures 2015-10-08 15:21:50 -07:00
LICENSE First commit without unit tests 2014-10-29 17:08:09 -04:00
README.md Reflect provider change in puppet-openstacklib 2015-08-19 10:01:40 +02:00
Rakefile Try to use zuul-cloner to prepare fixtures 2015-10-08 15:21:50 -07:00
metadata.json Prepare 6.0.0 release 2015-07-09 10:29:02 -04:00

README.md

puppet-tuskar

6.0.0 - 2015.1 - Kilo

Table of Contents

  1. Overview - What is the tuskar module?
  2. Module Description - What does the module do?
  3. Setup - The basics of getting started with tuskar
  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 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.

Types

tuskar_config

The tuskar_config provider is a children of the ini_setting provider. It allows one to write an entry in the /etc/tuskar/tuskar.conf file.

tuskar_config { 'DEFAULT/verbose' :
  value => true,
}

This will write verbose=true in the [DEFAULT] section.

name

Section/setting name to manage from tuskar.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>

Limitations

Development

Developer documentation for the entire puppet-openstack project.

Contributors