
The deployment guide is currently pointed at triplo-docs but it has been requested that we actually publish a deployment guide. This change extracts many of the installation doc pages and moves them into the deploy-guide source tree. Once the deploy-guide is published, we will follow up to reference the deployment guide from tripleo-docs. Change-Id: I0ebd26f014180a92c6cf4ab0929d99b2d860796f
29 lines
1.0 KiB
ReStructuredText
29 lines
1.0 KiB
ReStructuredText
Disable Telemetry
|
|
=================
|
|
|
|
This guide assumes that your undercloud is already installed and ready to
|
|
deploy an overcloud without Telemetry services.
|
|
|
|
Deploy your overcloud without Telemetry services
|
|
------------------------------------------------
|
|
|
|
If you don't need or don't want Telemetry services (Ceilometer, Gnocchi,
|
|
Panko and Aodh), you can disable the services by adding this environment
|
|
file when deploying the overcloud::
|
|
|
|
openstack overcloud deploy --templates \
|
|
-e /usr/share/openstack-tripleo-heat-templates/environments/disable-telemetry.yaml
|
|
|
|
Disabling Notifications
|
|
~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
When Telemetry is disabled, OpenStack Notifications will be disabled as well, and
|
|
the driver will be set to 'noop' for all OpenStack services.
|
|
If you would like to restore notifications, you would need to set NotificationDriver to
|
|
'messagingv2' in your environment.
|
|
|
|
.. Warning::
|
|
|
|
NotificationDriver parameter can only support 'noop' and 'messagingv2' for now.
|
|
Also note that 'messaging' driver is obsolete and isn't supported by TripleO.
|