22e1f0be41
With MOS 6.1 and later deployment_mode is always ha_compact. So this change removes the deployment_mode related tests in Puppet manifests. It also removes the deployment_mode tag that was set in Heka messages. This addresses a comment made by Simon Pasquier: https://review.openstack.org/#/c/255418/16/deployment_scripts/puppet/manifests/base.pp,unified Change-Id: I654d3a451bf86c28f66033cc98dd5a26bd2b80f0 |
||
|---|---|---|
| .. | ||
| README.md | ||
| log_index_template.json | ||
| notification_index_template.json | ||
| run_container.sh | ||
README.md
Description
Scripts and tools for running an Elasticsearch server to be used with the LMA collector.
Requirements
To run Elasticsearch, the host should have at least 1GB of free RAM. You also need sufficient free disk space for storing the data. The exact amount of disk depends highly on your environment and retention policy but 20GB is probably a sane minimum.
To store and query the data, clients need to be able to connect to the IP address of the container's host on the TCP port 9200.
Running
Simply:
$ ./run_container.sh
Use environment variables to override the default configuration:
$ ES_MEMORY=2 ./run_container.sh
Supported environment variables for configuration:
-
ES_LISTEN_ADDRESS: listen address on the container host (default=127.0.0.1)
-
ES_DATA: directory where to store the ES data and logs (default=~/es_volume)
-
ES_MEMORY: amount of memory (in GB) allocated to the JVM (default=16)
Testing
You can check that Elasticsearch is working using curl:
curl http://$HOST:9200/
Where HOST is the IP address or the name of the container's host.
The expected output is something like this:
{
"status" : 200,
"name" : "fuel.domain.tld",
"cluster_name" : "elasticsearch",
"version" : {
"number" : "1.4.2",
"build_hash" : "927caff6f05403e936c20bf4529f144f0c89fd8c",
"build_timestamp" : "2014-12-16T14:11:12Z",
"build_snapshot" : false,
"lucene_version" : "4.10.2"
},
"tagline" : "You Know, for Search"
}