Chapter 3. Install the Client-Side Tools
Before you deploy the overcloud, you need to determine the configuration settings to apply to each client. Copy the example environment files from the director’s Heat template collection and modify them to suit your environment.
3.1. Set Centralized Logging Client Parameters Copy linkLink copied to clipboard!
For Fluentd configuration settings, copy /usr/share/openstack-tripleo-heat-templates/environments/logging-environment.yaml
and modify the file to suit your environment. For example:
Simple configuration
Example SSL configuration
-
LoggingServers
- The destination system that will receive Fluentd log messages. -
LoggingUsesSSL
- Setting that determines whethersecure_forward
is used when forwarding log messages. -
LoggingSharedKey
- The shared secret used bysecure_forward
. -
LoggingSSLCertificate
- The PEM-encoded contents of the SSL CA certificate.
3.2. Set Availability Monitoring Client Parameters Copy linkLink copied to clipboard!
For the Sensu client configuration settings, copy /usr/share/openstack-tripleo-heat-templates/environments/monitoring-environment.yaml
and modify the file to suit your environment. For example:
-
MonitoringRabbit
- These parameters connect the Sensu client services to the RabbitMQ instance that runs on the monitoring server. -
MonitoringRabbitUseSSL
- Enables SSL for the RabbitMQ client. Uses SSL transport if the private key or certificate chain are not specified, as below. -
MonitoringRabbitSSLPrivateKey
- Defines the path to the private key file, or can contain the contents of that file. -
MonitoringRabbitSSLCertChain
- Defines the private SSL certificate chain to use. -
SensuClientCustomConfig
- Specify additional Sensu client configuration. Defines the OpenStack credentials to be used, including username/password,auth_url
, tenant, and region.
3.3. Install Operational Tools on Overcloud Nodes Copy linkLink copied to clipboard!
Include the modified YAML files with your openstack overcloud deploy
command to install the Sensu client and Fluentd tools on all overcloud nodes. For example:
openstack overcloud deploy --templates -e /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml -e network-environment.yaml -e ~/templates/monitoring-environment.yaml -e ~/templates/logging-environment.yaml --control-scale 3 --compute-scale 1 --ntp-server 192.168.122.10
$ openstack overcloud deploy --templates -e /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml -e network-environment.yaml -e ~/templates/monitoring-environment.yaml -e ~/templates/logging-environment.yaml --control-scale 3 --compute-scale 1 --ntp-server 192.168.122.10
3.4. Filter and Transform Logging Data Copy linkLink copied to clipboard!
You can filter and transform events sent to Fluentd by setting the LoggingDefaultFilters
parameter in your environment file. For example, the record_transformer
type can modify incoming events:
As a result, the data received by Kibana has been transformed accordingly: