labs: Disable telemetry service

Telemetry service comes with high overhead by consuming higher
resources than expected for the default minimal cluster configuration
for training labs.

Commented out the telementry related scripts under the config folder.
To re-enable it, just uncomment the required lines.

Change-Id: I6d53c4aefe689100c0315a366430a34ff1a807fe
This commit is contained in:
Pranav Salunke 2015-05-27 08:32:18 +02:00
parent d5e6feac8a
commit 22394d6fb4

View File

@ -35,8 +35,12 @@ cmd snapshot_cycle -n controller openstack_networks_configured
cmd queue setup_lbaas_controller.sh
cmd snapshot_cycle -n controller lbaas-controller_installed
cmd queue ubuntu/setup_telemetry_controller.sh
cmd snapshot_cycle -n controller telemetry-controller_installed
# Telemetry service is disabled for the time being as it overloads
# the cluster. For enabling the same, please uncomment the following.
# Warning: Use higher configuration (Disk space). The default
# configuration is optimized for 4GB i3/i5 based machine.
# cmd queue ubuntu/setup_telemetry_controller.sh
# cmd snapshot_cycle -n controller telemetry-controller_installed
cmd queue ubuntu/setup_heat_controller.sh
cmd snapshot_cycle -n controller heat_controller_installed
@ -57,8 +61,13 @@ cmd queue ubuntu/setup_neutron_compute.sh
cmd queue ubuntu/setup_cinder_volumes.sh
cmd snapshot_cycle -n compute cinder-volume_installed
cmd queue ubuntu/setup_telemetry_compute.sh
cmd snapshot_cycle -n compute telemetry-compute_installed
# Telemetry service is disabled for the time being as it overloads
# the cluster. For enabling the same, please uncomment the following.
# Warning: Use higher configuration (RAM, CPU's). The default
# configuration is optimized for 4GB i3/i5 based machine.
# cmd queue ubuntu/setup_telemetry_compute.sh
# cmd snapshot_cycle -n compute telemetry-compute_installed
# - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# Take snapshot of database changes on controller VM, too
cmd queue shutdown_controller.sh