A Squirro cluster This page can be extensively configured. This section covers the available configuration options and facilities in detail.
Table of Contents
Table of Contents |
---|
outline | true |
---|
exclude | Table of Contents |
---|
|
Configuration Management with Puppet
The Configuration Files section below outlines the various ways Squirro and its services can be configured. Squirro in a Box also ships with a Puppet configuration, which automates the management of those configuration files.
Info |
---|
|
Puppet is a configuration management utility. It ensures servers are running with the correct configuration. |
Puppet configuration
Squirro's Puppet recipe is driven by one file: /etc/squirro.yaml
. The available configuration settings are described on the separate page squirro.yaml.
Puppet execution
Whenever the squirro.yaml
file is modified, Puppet should be executed to apply the new configuration. Puppet is executed by running the following command as root:
Code Block |
---|
|
[root@localhost ~]# puppetrun |
Info |
---|
title | Automatic Puppet execution |
---|
|
Puppet is run every 60 minutes and upon reboot. When changing a Squirro config file directly, it might be under puppet control and thus any changes are reverted again with the next Puppet run. If you choose not to use Puppet, puppet can be disabled with the following command: puppet agent --disable
|
Configuration Files
Squirro
Each service has its own configuration file /etc/squirro/<servicename>.ini
. Additionally there is a common configuration file which applies to all services at /etc/squirro/common.ini
.
Filter by label (Content by label) |
---|
showLabels | false |
---|
showSpace | false |
---|
sort | title |
---|
excerptType | simple |
---|
cql | label = "squirro-configuration" and space = currentSpace() |
---|
|
Elasticsearch
For configuration of Elasticsearch, please refer to its documentation: Elasticsearch Configuration.now be found at Configuration on the Squirro Docs site.