Disable Telemetry services on undercloud by default

Finally lets disable by default. The use case for telemetry
has been quite slim anyway. The interested users now seem to
be ok with enabling it manually when needed. So lets do this!

Change-Id: Ic35bcf4f789a3f30e4634789e965203be74d2e8c

elements/puppet-stack-config/puppet-stack-config.pp

@@ -157,7 +157,7 @@ class { '::heat::db::mysql':
   dbname        => $heat_dsn[6],
   allowed_hosts => $allowed_hosts,
 }
-if str2bool(hiera('enable_telemetry', true)) {
+if str2bool(hiera('enable_telemetry', false)) {
 
   # Ceilometer
 

instack_undercloud/undercloud.py

@@ -298,9 +298,9 @@ _opts = [
                 help=('Whether to install Tempest in the Undercloud.')
                 ),
     cfg.BoolOpt('enable_telemetry',
-                default=True,
+                default=False,
                 help=('Whether to install Telemetry services '
-                      '(ceilometer, aodh) in the Undercloud.')
+                      '(ceilometer, gnocchi, aodh, panko ) in the Undercloud.')
                 ),
     cfg.BoolOpt('enable_ui',
                 default=True,

releasenotes/notes/disable-telemetry-by-default-d596b78fc08df1a9.yaml

@@ -0,0 +1,10 @@
+---
+upgrade:
+  - If you had telemetry enabled in Ocata and you upgrade to pike with
+    defaults, the telemetry services will be disabled upon upgrade. If
+    you choose to keep it enabled, set the enable_telemetry option to
+    true before upgrade and services will continue to be enabled after upgrade.
+fixes:
+  - Finally disabling telemetry services on undercloud by default. Telemetry
+    use case has been quite limited on undercloud and it makes sense to
+    disable by default and let user enabl based on need.

undercloud.conf.sample

@@ -154,7 +154,7 @@
 
 # Whether to install Telemetry services (ceilometer, aodh) in the
 # Undercloud. (boolean value)
-#enable_telemetry = true
+#enable_telemetry = false
 
 # Whether to install the TripleO UI. (boolean value)
 #enable_ui = true