70dd361368
This is a mechanically generated patch to complete step 1 of moving the zuul job settings out of project-config and into each project repository. Because there will be a separate patch on each branch, the branch specifiers for branch-specific jobs have been removed. Because this patch is generated by a script, there may be some cosmetic changes to the layout of the YAML file(s) as the contents are normalized. See the python3-first goal document for details: https://governance.openstack.org/tc/goals/stein/python3-first.html Change-Id: Ia497cab864f6bac56d9809907f563775280e166a Story: #2002586 Task: #24325
Team and repository tags
zaqar
Table of Contents
- Overview - What is the zaqar module?
- Module Description - What does the module do?
- Setup - The basics of getting started with zaqar
- 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 zaqar 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 queue service for OpenStack.
Module Description
The zaqar module is a thorough attempt to make Puppet capable of managing the entirety of zaqar. This includes manifests to provision region specific endpoint and database connections. Types are shipped as part of the zaqar module to assist in manipulation of configuration files.
Setup
What the zaqar module affects
Zaqar, the queue service for OpenStack.
Installing zaqar
puppet module install openstack/zaqar
Beginning with zaqar
Implementation
zaqar
zaqar is a combination of Puppet manifest and ruby code to delivery configuration and extra functionality through types and providers.
Types
zaqar_config
The zaqar_config provider is a children of the ini_setting provider. It allows one to write an entry in the /etc/zaqar/zaqar.conf file.
zaqar_config { 'DEFAULT/debug' :
value => true,
}
This will write debug=true in the [DEFAULT] section.
name
Section/setting name to manage from zaqar.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
- All the zaqar types use the CLI tools and so need to be ran on the zaqar 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.