Deploying Operational Tools¶
TripleO comes with an optional suite of tools designed to help operators maintain an OpenStack environment. The tools perform the following functions:
- Availability Monitoring
- Centralized Logging
This document will go through the presentation and installation of these tools.
Deploying the Undercloud¶
undercloud.confbefore the deployment:
enable_monitoringto true if you want to enable Availability Monitoring. You can also specify a password for
undercloud_sensu_password, otherwise one will be automatically generated.
enable_loggingto true if you want to enable Centralized Logging. By default, the indexes will be closed after 7 days and deleted after 10 days by using Curator. You can change that with the 2 parameters:
- That’s it, you’re ready to deploy your undercloud!
Deploying the Overcloud¶
The Deploying with Heat Templates document has a more detailed explanation of the following steps.
stackuser, copy the Operational tools configuration files to your home directory:
cp /usr/share/openstack-tripleo-heat-templates/environments/monitoring-sensu-config.yaml ~
cp /usr/share/openstack-tripleo-heat-templates/environments/logging-fluentd-config.yaml ~
Edit the parameters in the Operational tools configuration files to fit your requirements.
Continue following the TripleO instructions for deploying an overcloud. Before entering the command to deploy the overcloud, add the environment file that you just configured as an argument:
openstack overcloud deploy --templates -e ~/monitoring-sensu-config.yaml -e ~/logging-fluentd-config.yaml
Wait for the completion of the overcloud deployment process.
Accessing to the Dashboards¶
Availability Monitoring: you can reach the Sensu dashboard (Uchiwa) on this URL:
Centralized Logging: you can reach the Elastic dashboard (Kibana) on this URL: