Unnamed repository; edit this file 'description' to name the repository. https://git.platform-os.org/openstack/kolla.git/atom?h=master 2016-11-16T04:34:17+00:00 2016-11-16T04:34:17+00:00 Steven Dake stdake@cisco.com 2016-11-16T02:01:25+00:00 urn:sha1:3fcef82946f7053affcfb0b1b3ef4292beb9fa95 Change-Id: I5396e4b9927d3e65b6aa4185238a43a4765a996b 2016-10-17T09:34:31+00:00 Christian Berendt berendt@betacloud-solutions.de 2016-10-17T08:46:02+00:00 urn:sha1:4223fdfbeb7f972e6f23a67308a8357092e46ad0 Logs should be stored in /var/log/kolla/elasticsearch. Change-Id: If3ba4ec6ce2dbe9859ca604f0ee2df7fc4d15bd9 Closes-bug: #1634046 2016-09-23T15:58:28+00:00 Serguei Bezverkhi sbezverk@cisco.com 2016-09-23T12:53:26+00:00 urn:sha1:911dfe4ef7c3cfd012ce3887ec491b8ee4581730 This PS modifies Elasticsearch and Kibana configuration templates so genconfig can genarate Kubernetes compatible config for these services. TrivialFix Change-Id: I6886307a163a9ca27a29e6dbdac4f9080948e4b5 2016-03-05T10:51:49+00:00 Éric Lemoine elemoine@mirantis.com 2016-02-24T15:05:36+00:00 urn:sha1:491aff0b88bc3dac13ea9180c952854fd0a67684 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-13T07:53:24+00:00 akwasniewska alicja.kwasniewska@intel.com 2016-01-14T10:06:29+00:00 urn:sha1:792666dd79aef7d041c6d5f0ce1f57125ee1affc Part of ELK stack. Includes Dockerfiles for both Centos and Ubuntu. Change-Id: I9f76adf084cd4f68e29326112b76ffd02b5adada Partially-implements: blueprint central-logging-service