fb38fa63b3
In order to support subscriptions in StoryBoard, we're adding a queueing system to support triggered events. The specification in question is #95307, which goes into detail on the various different options evaluated. I also anticipate that this system can be used for report generation. Change-Id: Ia4cc91f1e75365a9fb41ca163e55548023233412 Story: 96
42 lines
1.3 KiB
Puppet
42 lines
1.3 KiB
Puppet
# Copyright (c) 2014 Hewlett-Packard Development Company, L.P.
|
|
#
|
|
# Licensed under the Apache License, Version 2.0 (the "License"); you may
|
|
# not use this file except in compliance with the License. You may obtain
|
|
# a copy of the License at
|
|
#
|
|
# http://www.apache.org/licenses/LICENSE-2.0
|
|
#
|
|
# Unless required by applicable law or agreed to in writing, software
|
|
# distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
|
|
# WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
|
|
# License for the specific language governing permissions and limitations
|
|
# under the License.
|
|
|
|
# == Class: storyboard::rabbit
|
|
#
|
|
# The StoryBoard Rabbit manifest installs a standalone rabbitmq instance
|
|
# which is used to handle deferred processing and reporting tasks for
|
|
# StoryBoard.
|
|
#
|
|
class storyboard::rabbit (
|
|
$rabbitmq_user = 'storyboard',
|
|
$rabbitmq_user_password = 'changeme'
|
|
) {
|
|
|
|
class { 'rabbitmq':
|
|
service_manage => true,
|
|
delete_guest_user => true
|
|
}
|
|
|
|
rabbitmq_user { $rabbitmq_user:
|
|
password => $rabbitmq_user_password
|
|
}
|
|
|
|
rabbitmq_user_permissions { "${rabbitmq_user}@/":
|
|
configure_permission => '.*',
|
|
read_permission => '.*',
|
|
write_permission => '.*',
|
|
require => Rabbitmq_user[$rabbitmq_user]
|
|
}
|
|
}
|