openstack/puppet-openstack-integration
Code Issues Proposed changes
30a78d1b80
puppet-openstack-integration/manifests/mongodb.pp

11 lines
215 B
ObjectPascal
Raw Normal View History

Deploy MongoDB on scenario002 Some services (like Zaqar) require MongoDB in place to be tested. We plan to test Zaqar soon, when the Puppet module will be finished. So this patch is a first iteration by deploying MongoDB. It also bump the version of puppetlabs-mongodb to use latest release (0.12). Change-Id: I408049e658e1b7466dfce9dc565480b538656230
2016-02-12 11:56:28 -05:00
class openstack_integration::mongodb {
include ::mongodb::globals
include ::mongodb::client
scenario002: deploy & test Zaqar puppet-zaqar is freshly new and we want to test it. * configure mongodb replicaset (required for zaqar): 'openstack'. * deploy zaqar on scenario002 with mongodb backend. * configure tempest to test zaqar. * run TestManageQueue tempest tests in tempest. Note about TestManageQueue: Zaqar does not maintain Tempest tests, and run their own functional testing tools. api.messaging.test_queues tests are known to work, so they will be the only tests run in our CI to validate Zaqar is working. Note: * SSL does not work out of the box, we need to add support for WSGI deployment with Apache, but Zaqa does not provide WSGI app, it's in their roadmap. * IPv6 binding on default wsgi does not work, so using IPv4 now. Change-Id: I1aa563f37aa7a231b2218f79b72c73c668d968f3
2016-02-17 15:30:37 -05:00
class { '::mongodb::server':
replset => 'openstack',
replset_members => ['127.0.0.1:27017'],
}
Deploy MongoDB on scenario002 Some services (like Zaqar) require MongoDB in place to be tested. We plan to test Zaqar soon, when the Puppet module will be finished. So this patch is a first iteration by deploying MongoDB. It also bump the version of puppetlabs-mongodb to use latest release (0.12). Change-Id: I408049e658e1b7466dfce9dc565480b538656230
2016-02-12 11:56:28 -05:00
}
Copy Permalink