Puppet can become confused if there are classes of similar names
at different levels. In this case 'puppetdb' is available from the
puppetdb module and is available from openstack_project::puppetdb.
Putting the extra :: in front explicitly grabs it from top scope
so we don't have any issues.
Change-Id: Iaec56b82004c972f5771b6039675db5c2d725f91
Use inherits keyword to bring puppetboard::params into scope
Use 2>&1 in install_modules to silence warnings
Set puppetdb class to open port 80 when puppetboard is used
Remove inherits from params check from puppet lint
Change-Id: I75fc35542e9f2641bcab613d7e1aef83d9300217
This places the puppet web dashboard puppetboard from
https://github.com/nedap/puppetboard onto the puppetdb server.
This enables anyone to see the output of puppet runs, which nodes
are failing and which nodes have not checked in over time. We can
also quickly and interactively query the facts database.
This also modifies install_modules.sh to support a list of modules
that will be installed without dependency resolution.
Change-Id: I09d09410dd8fa71759ce6b2f9c7f34f78eefe204
This sets the puppetdb server to listen on all interfaces over
both ipv4 and ipv6. I have left a comment in the code for future
travelers wondering if '0.0.0.0' will open up ipv6 addresses as
well.
Change-Id: I2396c721afdf956085b46d8633a236aaab46fa94
This brings in the puppetdb module via install_modules.sh and
creates a new class, openstack_project::puppetdb. It was modeled
on openstack_project::puppetmaster. Note that this will not enable
puppetdb to participate in the Puppet ecosystem yet. An additional
class will have to be added to the master:
class { 'puppetdb::master::config':
puppetdb_server => 'puppetdb',
}
I will leave this out of this change so we can bring up puppetdb in
stages.
This paves the way for puppetboard to be brought online.
Change-Id: I8194372bd31e08f12a815fd04dcdf338565ed911
