Go to file

Paul Belanger 4d654d1891 Remove logic to check for puppetlabs-apache

Now that puppet-httpd has been fully migrated too, we can remove this
obsolete logic.

Change-Id: Ic4e07a4031854bed0e53305d6cc1b376b8c60f21
Signed-off-by: Paul Belanger <pabelanger@redhat.com>

2015-08-19 09:45:49 -04:00

files

Set up file conditions for os-loganalyze

2015-08-11 21:36:40 +10:00

manifests

Remove logic to check for puppetlabs-apache

2015-08-19 09:45:49 -04:00

spec

Check resources in the openstackci::loghost class

2015-07-08 14:45:23 -07:00

templates

Set up file conditions for os-loganalyze

2015-08-11 21:36:40 +10:00

.gitreview

Added .gitreview

2015-03-18 17:00:55 +00:00

Gemfile

Add Gemfile

2015-06-08 12:41:18 -07:00

LICENSE

Initial files for the puppet-openstackci repo

2015-03-24 12:05:27 -07:00

metadata.json

Migrate to puppet-httpd module

2015-07-24 13:32:54 -04:00

Rakefile

Initial files for the puppet-openstackci repo

2015-03-24 12:05:27 -07:00

README.md

Add developer guidelines

2015-04-29 01:46:24 -07:00

README.md

OpenStack Continuous Integration Module

Overview

Configures an OpenStack Continuous Integration System

Developing

If you are adding features to this module, first ask yourself: "Does this logic belong in the module for the service?"

An example of this is the gearman-logging.conf file needed by the zuul service. This file should be managed by the zuul module, not managed here. What should go in this module is high level directives and integrations such as a list of jenkins plugins to install or a class that instantiates multiple services.