Initial commit
This commit is contained in:
commit
b182b5ac54
1
deployment/puppet/rabbitmq/.gitignore
vendored
Normal file
1
deployment/puppet/rabbitmq/.gitignore
vendored
Normal file
@ -0,0 +1 @@
|
|||||||
|
pkg/
|
11
deployment/puppet/rabbitmq/Modulefile
Normal file
11
deployment/puppet/rabbitmq/Modulefile
Normal file
@ -0,0 +1,11 @@
|
|||||||
|
name 'puppetlabs-rabbitmq'
|
||||||
|
version '0.0.1'
|
||||||
|
source 'UNKNOWN'
|
||||||
|
author 'puppetlabs'
|
||||||
|
license 'UNKNOWN'
|
||||||
|
summary 'UNKNOWN'
|
||||||
|
description 'UNKNOWN'
|
||||||
|
project_page 'UNKNOWN'
|
||||||
|
|
||||||
|
## Add dependencies, if any:
|
||||||
|
# dependency 'username/name', '>= 1.2.0'
|
3
deployment/puppet/rabbitmq/README
Normal file
3
deployment/puppet/rabbitmq/README
Normal file
@ -0,0 +1,3 @@
|
|||||||
|
rabbitmq
|
||||||
|
|
||||||
|
This is the rabbitmq module.
|
22
deployment/puppet/rabbitmq/files/README.markdown
Normal file
22
deployment/puppet/rabbitmq/files/README.markdown
Normal file
@ -0,0 +1,22 @@
|
|||||||
|
Files
|
||||||
|
=====
|
||||||
|
|
||||||
|
Puppet comes with both a client and server for copying files around. The file
|
||||||
|
serving function is provided as part of the central Puppet daemon,
|
||||||
|
puppetmasterd, and the client function is used through the source attribute of
|
||||||
|
file objects. Learn more at
|
||||||
|
http://projects.puppetlabs.com/projects/puppet/wiki/File_Serving_Configuration
|
||||||
|
|
||||||
|
You can use managed files like this:
|
||||||
|
|
||||||
|
class myclass {
|
||||||
|
package { mypackage: ensure => latest }
|
||||||
|
service { myservice: ensure => running }
|
||||||
|
file { "/etc/myfile":
|
||||||
|
source => "puppet://$servername/modules/mymodule/myfile"
|
||||||
|
}
|
||||||
|
}
|
||||||
|
|
||||||
|
The files are searched for in:
|
||||||
|
|
||||||
|
$modulepath/mymodule/files/myfile
|
28
deployment/puppet/rabbitmq/manifests/README.markdown
Normal file
28
deployment/puppet/rabbitmq/manifests/README.markdown
Normal file
@ -0,0 +1,28 @@
|
|||||||
|
Manifests
|
||||||
|
=========
|
||||||
|
|
||||||
|
Module manifest files belong in this directory.
|
||||||
|
|
||||||
|
`init.pp` defines how the module will carry out its tasks in this file.
|
||||||
|
|
||||||
|
Add additional definitions in this directory. Their file paths should match the
|
||||||
|
definition name; for example, a definition `mydefinition`, defined like this:
|
||||||
|
|
||||||
|
# Definition: mydefinition
|
||||||
|
#
|
||||||
|
# This is the mydefinition in the mymodule module.
|
||||||
|
#
|
||||||
|
# Parameters:
|
||||||
|
#
|
||||||
|
# Actions:
|
||||||
|
#
|
||||||
|
# Requires:
|
||||||
|
#
|
||||||
|
# Sample Usage:
|
||||||
|
#
|
||||||
|
# [Remember: No empty lines between comments and class definition]
|
||||||
|
define mydefinition {
|
||||||
|
# ...
|
||||||
|
}
|
||||||
|
|
||||||
|
Should be found in `mydefinition.pp` in this directory.
|
17
deployment/puppet/rabbitmq/manifests/init.pp
Normal file
17
deployment/puppet/rabbitmq/manifests/init.pp
Normal file
@ -0,0 +1,17 @@
|
|||||||
|
# Class: rabbitmq
|
||||||
|
#
|
||||||
|
# This module manages rabbitmq
|
||||||
|
#
|
||||||
|
# Parameters:
|
||||||
|
#
|
||||||
|
# Actions:
|
||||||
|
#
|
||||||
|
# Requires:
|
||||||
|
#
|
||||||
|
# Sample Usage:
|
||||||
|
#
|
||||||
|
# [Remember: No empty lines between comments and class definition]
|
||||||
|
class rabbitmq {
|
||||||
|
|
||||||
|
|
||||||
|
}
|
12
deployment/puppet/rabbitmq/metadata.json
Normal file
12
deployment/puppet/rabbitmq/metadata.json
Normal file
@ -0,0 +1,12 @@
|
|||||||
|
/*
|
||||||
|
+-----------------------------------------------------------------------+
|
||||||
|
| |
|
||||||
|
| ==> DO NOT EDIT THIS FILE! <== |
|
||||||
|
| |
|
||||||
|
| You should edit the `Modulefile` and run `puppet-module build` |
|
||||||
|
| to generate the `metadata.json` file for your releases. |
|
||||||
|
| |
|
||||||
|
+-----------------------------------------------------------------------+
|
||||||
|
*/
|
||||||
|
|
||||||
|
{}
|
7
deployment/puppet/rabbitmq/spec/README.markdown
Normal file
7
deployment/puppet/rabbitmq/spec/README.markdown
Normal file
@ -0,0 +1,7 @@
|
|||||||
|
Specs
|
||||||
|
=====
|
||||||
|
|
||||||
|
The Puppet project uses RSpec for testing.
|
||||||
|
|
||||||
|
For more information on RSpec, see http://rspec.info/
|
||||||
|
|
6
deployment/puppet/rabbitmq/spec/spec.opts
Normal file
6
deployment/puppet/rabbitmq/spec/spec.opts
Normal file
@ -0,0 +1,6 @@
|
|||||||
|
--format
|
||||||
|
s
|
||||||
|
--colour
|
||||||
|
--loadby
|
||||||
|
mtime
|
||||||
|
--backtrace
|
18
deployment/puppet/rabbitmq/spec/spec_helper.rb
Normal file
18
deployment/puppet/rabbitmq/spec/spec_helper.rb
Normal file
@ -0,0 +1,18 @@
|
|||||||
|
require 'pathname'
|
||||||
|
dir = Pathname.new(__FILE__).parent
|
||||||
|
$LOAD_PATH.unshift(dir, dir + 'lib', dir + '../lib')
|
||||||
|
|
||||||
|
require 'mocha'
|
||||||
|
require 'puppet'
|
||||||
|
gem 'rspec', '=1.2.9'
|
||||||
|
require 'spec/autorun'
|
||||||
|
|
||||||
|
Spec::Runner.configure do |config|
|
||||||
|
config.mock_with :mocha
|
||||||
|
end
|
||||||
|
|
||||||
|
# We need this because the RAL uses 'should' as a method. This
|
||||||
|
# allows us the same behaviour but with a different method name.
|
||||||
|
class Object
|
||||||
|
alias :must :should
|
||||||
|
end
|
@ -0,0 +1,4 @@
|
|||||||
|
Provider Specs
|
||||||
|
==============
|
||||||
|
|
||||||
|
Define specs for your providers under this directory.
|
@ -0,0 +1,4 @@
|
|||||||
|
Resource Type Specs
|
||||||
|
===================
|
||||||
|
|
||||||
|
Define specs for your resource types in this directory.
|
23
deployment/puppet/rabbitmq/templates/README.markdown
Normal file
23
deployment/puppet/rabbitmq/templates/README.markdown
Normal file
@ -0,0 +1,23 @@
|
|||||||
|
Templates
|
||||||
|
=========
|
||||||
|
|
||||||
|
Puppet supports templates and templating via ERB, which is part of the Ruby
|
||||||
|
standard library and is used for many other projects including Ruby on Rails.
|
||||||
|
Templates allow you to manage the content of template files, for example
|
||||||
|
configuration files that cannot yet be managed as a Puppet type. Learn more at
|
||||||
|
http://projects.puppetlabs.com/projects/puppet/wiki/Puppet_Templating
|
||||||
|
|
||||||
|
You can use templates like this:
|
||||||
|
|
||||||
|
class myclass {
|
||||||
|
package { mypackage: ensure => latest }
|
||||||
|
service { myservice: ensure => running }
|
||||||
|
file { "/etc/myfile":
|
||||||
|
content => template("mymodule/myfile.erb")
|
||||||
|
}
|
||||||
|
}
|
||||||
|
|
||||||
|
The templates are searched for in:
|
||||||
|
|
||||||
|
$templatedir/mymodule/myfile.erb
|
||||||
|
$modulepath/mymodule/templates/myfile.erb
|
1
deployment/puppet/rabbitmq/tests/init.pp
Normal file
1
deployment/puppet/rabbitmq/tests/init.pp
Normal file
@ -0,0 +1 @@
|
|||||||
|
include rabbitmq
|
Loading…
Reference in New Issue
Block a user