openstack/tripleo-docs
Code Issues Proposed changes
5c3d73144b
tripleo-docs/doc/source/advanced_deployment/ops_tools.rst
Emilien Macchi 63f6f8ede0 First documentation for Operational tools 
This patch is a first documentation for deploying Operational tools in
TripleO.

That's a start of work and expect more content in the future, but that's
the basic structure of what we need to deploy the stack.

It includes Monitoring & Logging content for both undercloud &
overcloud.

Co-Authored-By: Swapnil Kulkarni <me@coolsvap.net>
Change-Id: I9326a46de121ba6591babe632355b78557741d4d
2016-05-24 16:58:59 +02:00

3.0 KiB
Raw Blame History

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.

Architecture

  1. Undercloud:
  2. Overcloud:

Deploying the Undercloud

  1. Edit undercloud.conf before the deployment:
    • set enable_monitoring to true if you want to enable Availability Monitoring. You can also specify a password for undercloud_sensu_password, otherwise one will be automatically generated.
    • set enable_logging to 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: elastic_close_index_days and elastic_delete_index_days.
  2. That's it, you're ready to deploy your undercloud!

Deploying the Overcloud

Note

The template_deploy document has a more detailed explanation of the following steps.

  1. As the stack user, copy the Operational tools configuration files to your home directory:

    • Availability Monitoring:

      cp /usr/share/openstack-tripleo-heat-templates/environments/monitoring-sensu-config.yaml ~

    • Centralized Logging:

      cp /usr/share/openstack-tripleo-heat-templates/environments/logging-fluentd-config.yaml ~

  2. Edit the parameters in the Operational tools configuration files to fit your requirements.

  3. 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

  4. Wait for the completion of the overcloud deployment process.

Accessing to the Dashboards

  1. Availability Monitoring: you can reach the Sensu dashboard (Uchiwa) on this URL:

    http://<UNDERCLOUD_IP_ADDRESS>:3000

  2. Centralized Logging: you can reach the Elastic dashboard (Kibana) on this URL:

    http://<UNDERCLOUD_IP_ADDRESS>:8300/index.html#/dashboard/file/logstash.json