aboutsummaryrefslogtreecommitdiff
path: root/ansible/roles/elasticsearch
AgeCommit message (Collapse)AuthorFilesLines
2016-11-15Remove Ansible from KollaSteven Dake12-172/+0
Change-Id: I5396e4b9927d3e65b6aa4185238a43a4765a996b
2016-11-03Move precheck into its own roleJeffrey Zhang1-0/+1
* Merge prechecks.yml and site.yml playbook * Create empty precheck.yml into all roles. Change-Id: I8a138558a26c0a2a66c5fd48ed37be657c99c1dd Implements: blueprint condition-pre-check
2016-10-17Fix log directory of ElasticsearchChristian Berendt2-1/+6
Logs should be stored in /var/log/kolla/elasticsearch. Change-Id: If3ba4ec6ce2dbe9859ca604f0ee2df7fc4d15bd9 Closes-bug: #1634046
2016-10-15Fix elasticsearch upgrade permission issuezhubingbing1-0/+7
Change-Id: I113912e492c719385700da89307c7af4538207f9 Partial-Bug: #1631503
2016-09-27Remove do_reconfigure.yml file for all rolesJeffrey Zhang2-66/+63
do_reconfigure.yml is introduced to use serial directive. But we use it in wrong. Now serial has moved to playbook file. So it is time to remove the do_reconfigure.yml file Closes-Bug: #1628152 Change-Id: I8d42d27e6bc302a0e575b0353956eaef9b2ca9fd
2016-09-23ES and Kibana config modification for KubeSerguei Bezverkhi1-4/+5
This PS modifies Elasticsearch and Kibana configuration templates so genconfig can genarate Kubernetes compatible config for these services. TrivialFix Change-Id: I6886307a163a9ca27a29e6dbdac4f9080948e4b5
2016-09-13Added serial option to site.yml.Mick Thompson2-2/+0
Useful for upgrade etc., which is preferablly done serially. Example usage: tools/kolla-ansible deploy OR tools/kolla-ansible upgrade Closes-Bug: #1576708 DocImpact Change-Id: I34b2e16f8ce53e472a4682a4738c4ac0f5abf00c
2016-08-24Fix bug in Elasticsearch roleDuong Ha-Quang3-0/+68
Add Ansbile reconfigure playbook to Elasticsearch role. Add run condition to start playbook in Elasticsearch role. Change-Id: I7862089cae55d392eb2d922f89a382d392cf8b97 Closes-Bug: #1616005
2016-05-03map the host localtime to the containerJeffrey Zhang1-0/+1
Closes-Bug: #1577148 Change-Id: I636cefc63cf532434a41af3898b63dffa711e280
2016-03-24Upgrade elasticsearchJeffrey Zhang1-0/+4
Change-Id: I24d17f98013d82f2e6f46548cac80c0303d6e171 Implements: blueprint upgrade-elasticsearch
2016-03-05Make Heka send logs to ElasticsearchÉric Lemoine2-3/+19
This patch includes changes relative to integrating Heka with Elasticsearch and Kibana. The main change is the addition of an Heka ElasticSearchOutput plugin to make Heka send the logs it collects to Elasticsearch. Since Logstash is not used the enable_elk deploy variable is renamed to enable_central_logging. If enable_central_logging is false then Elasticsearch and Kibana are not started, and Heka won't attempt to send logs to Elasticsearch. By default enable_central_logging is set to false. If enable_central_logging is set to true after deployment then the Heka container needs to be recreated (for Heka to get the new configuration). The Kibana configuration used property names that are deprecated in Kibana 4.2. This is changed to use non-deprecated property names. Previously logs read from files and from Syslog had a different Type in Heka. This is changed to always use "log" for the Type. In this way just one index instead of two is used in Elasticsearch, making things easier to the user on the visualization side. The HAProxy configuration is changed to add entries for Kibana. Kibana server is now accessible via the internal VIP, and also via the external VIP if there's one configured. The HAProxy configuration is changed to add an entry for Elasticsearch. So Elasticsearch is now accessible via the internal VIP. Heka uses that channel for communicating with Elasticsearch. Note that currently the Heka logs include "Plugin elasticsearch_output" errors when Heka starts. This occurs when Heka starts processing logs while Elasticsearch is not yet started. These are transient errors that go away when Elasticsearch is ready. And with buffering enabled on the ElasticSearchOuput plugin logs will be buffered and then retransmitted when Elasticsearch is ready. Change-Id: I6ff7a4f0ad04c4c666e174693a35ff49914280bb Implements: blueprint central-logging-service
2016-02-26Change kolla_internal_address variableSamYaple1-1/+1
Due to poor planning on our variable names we have a situation where we have "internal_address" which must be a VIP, but "external_address" which should be a DNS name. Now with two vips "external_vip_address" is a new variable. This corrects that issue by deprecating kolla_internal_address and replacing it with 4 nicely named variables. kolla_internal_vip_address kolla_internal_fqdn kolla_external_vip_address kolla_external_fqdn The default behaviour will remain the same, and the way the variable inheritance is setup the kolla_internal_address variable can still be set in globals.yml and propogate out to these 4 new variables like it normally would, but all reference to kolla_internal_address has been completely removed. Change-Id: I4556dcdbf4d91a8d2751981ef9c64bad44a719e5 Partially-Implements: blueprint ssl-kolla
2016-02-25Add the default empty reconfigure.yml file to all rolesJeffrey Zhang1-0/+1
DocImpact Partially-implements: bp kolla-reconfig Change-Id: I9738e80960bcfbef18d1ef1b7942f81c45684e85
2016-02-22Upgrade stub for elasticsearchMichal (inc0) Jastrzebski1-0/+1
This should be later replaced with actual upgrade logic Change-Id: I1c386a7f3bc0d15ebe4a47d2628833172a15f89b Partially-implements: blueprint upgrade-kolla Partially-implements: blueprint upgrade-elasticseatch
2016-02-13Added Elasticearch and its deployment.akwasniewska9-0/+72
Part of ELK stack. Includes Dockerfiles for both Centos and Ubuntu. Change-Id: I9f76adf084cd4f68e29326112b76ffd02b5adada Partially-implements: blueprint central-logging-service
generated by cgit v1.2.3 (git 2.39.1) at 2026-11-05 20:47:27 +0000