From 1aca2b8b4d35331a3dad350b831d648596a523dc Mon Sep 17 00:00:00 2001
From: Spencer Krum <spencer.krum@hp.com>
Date: Wed, 27 Aug 2014 16:32:46 -0700
Subject: [PATCH] Conditionally manage puppetdb connection

This allows us to bring up the puppet3 master in an automated way,
then flip on puppetdb later. Most importantly this allows for a step
in the middle where an infra core applies the puppetmaster3 cert
and key from the original puppetmaster.

Change-Id: I77a815591649d55b8c17fb9431add0edd68ce0d2
---
 modules/openstack_project/manifests/puppetmaster.pp | 13 ++++++++-----
 1 file changed, 8 insertions(+), 5 deletions(-)

diff --git a/modules/openstack_project/manifests/puppetmaster.pp b/modules/openstack_project/manifests/puppetmaster.pp
index 27faf70ee3..bfc1b9e2b9 100644
--- a/modules/openstack_project/manifests/puppetmaster.pp
+++ b/modules/openstack_project/manifests/puppetmaster.pp
@@ -6,6 +6,7 @@ class openstack_project::puppetmaster (
   $sysadmins = [],
   $version   = '2.7.',
   $ca_server = undef,
+  $puppetdb = true,
 ) {
   include ansible
   include logrotate
@@ -105,11 +106,13 @@ class openstack_project::puppetmaster (
 
 # Enable puppetdb
 
-  class { 'puppetdb::master::config':
-    puppetdb_server              => 'puppetdb.openstack.org',
-    puppet_service_name          => 'apache2',
-    puppetdb_soft_write_failure  => true,
-    manage_storeconfigs          => false,
+  if $puppetdb {
+    class { 'puppetdb::master::config':
+      puppetdb_server              => 'puppetdb.openstack.org',
+      puppet_service_name          => 'apache2',
+      puppetdb_soft_write_failure  => true,
+      manage_storeconfigs          => false,
+    }
   }
 
 # Playbooks