)]}'
{"specs/logging-with-heka.rst":[{"author":{"_account_id":14119,"name":"Sam Yaple","email":"sam+git@yaple.net","username":"SamYaple"},"change_message_id":"580f28a71b402de70d3b8af48a033e3c4e7dc915","unresolved":false,"context_lines":[{"line_number":8,"context_line":"suggests to use ELK (Elasticsearch, Logstash, Kibana) as a way to index all the"},{"line_number":9,"context_line":"logs, and visualize them."},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"This spec suggests using Heka [2] instead of Logstash, while still using"},{"line_number":12,"context_line":"Elasticsearch for indexing and Kibana for visualization."},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"What is Heka?"}],"source_content_type":"text/x-rst","patch_set":6,"id":"9a68dd71_f0d228d0","line":11,"updated":"2016-01-25 21:03:25.000000000","message":"so we are _not_ replacing rsyslog with Heka? rsyslog config stays as is?","commit_id":"38771afe9f0a0d60cb10714cd33924a8cced6641"},{"author":{"_account_id":19300,"name":"Eric Lemoine","email":"elemoine@mirantis.com","username":"elemoine"},"change_message_id":"7ac65d1dc1fb2ae221584dcbbdcd586e24f90a92","unresolved":false,"context_lines":[{"line_number":8,"context_line":"suggests to use ELK (Elasticsearch, Logstash, Kibana) as a way to index all the"},{"line_number":9,"context_line":"logs, and visualize them."},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"This spec suggests using Heka [2] instead of Logstash, while still using"},{"line_number":12,"context_line":"Elasticsearch for indexing and Kibana for visualization."},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"What is Heka?"}],"source_content_type":"text/x-rst","patch_set":6,"id":"7a5de9d1_9080fcc1","line":11,"in_reply_to":"9a68dd71_ad29a939","updated":"2016-01-29 13:13:21.000000000","message":"Done","commit_id":"38771afe9f0a0d60cb10714cd33924a8cced6641"},{"author":{"_account_id":19300,"name":"Eric Lemoine","email":"elemoine@mirantis.com","username":"elemoine"},"change_message_id":"e80a434b7848ba886c9c74ce511223add182bc90","unresolved":false,"context_lines":[{"line_number":8,"context_line":"suggests to use ELK (Elasticsearch, Logstash, Kibana) as a way to index all the"},{"line_number":9,"context_line":"logs, and visualize them."},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"This spec suggests using Heka [2] instead of Logstash, while still using"},{"line_number":12,"context_line":"Elasticsearch for indexing and Kibana for visualization."},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"What is Heka?"}],"source_content_type":"text/x-rst","patch_set":6,"id":"9a68dd71_ad29a939","line":11,"in_reply_to":"9a68dd71_f0d228d0","updated":"2016-01-26 09:22:22.000000000","message":"The goal is to remove Rsyslog, as mentioned later in the document.  But we need to be able to handle haproxy and keepalived, as you noted later in your review.","commit_id":"38771afe9f0a0d60cb10714cd33924a8cced6641"},{"author":{"_account_id":6794,"name":"Simon Pasquier","email":"pasquier.simon@gmail.com","username":"simon-pasquier"},"change_message_id":"4a94574b1b013d90fae014d2c0ed2a25d8b3db52","unresolved":false,"context_lines":[{"line_number":86,"context_line":"based on some prototyping work we have conducted [4]."},{"line_number":87,"context_line":""},{"line_number":88,"context_line":"Also, it is important to note that RabbitMQ logs are not available today.  This"},{"line_number":89,"context_line":"is related to RabbitMQ not writing its logs to Syslog.  (RabbitMQ just does not"},{"line_number":90,"context_line":"support logging to Syslog currently.)  Naturally it is important that the logs"},{"line_number":91,"context_line":"of all the Kolla services should be collected by the logging system.  This"},{"line_number":92,"context_line":"proposal aims to address that issue."}],"source_content_type":"text/x-rst","patch_set":6,"id":"9a68dd71_50bd3ed6","line":89,"range":{"start_line":89,"start_character":53,"end_line":89,"end_character":55},"updated":"2016-01-26 08:50:58.000000000","message":"(nit) to be removed","commit_id":"38771afe9f0a0d60cb10714cd33924a8cced6641"},{"author":{"_account_id":14119,"name":"Sam Yaple","email":"sam+git@yaple.net","username":"SamYaple"},"change_message_id":"580f28a71b402de70d3b8af48a033e3c4e7dc915","unresolved":false,"context_lines":[{"line_number":87,"context_line":""},{"line_number":88,"context_line":"Also, it is important to note that RabbitMQ logs are not available today.  This"},{"line_number":89,"context_line":"is related to RabbitMQ not writing its logs to Syslog.  (RabbitMQ just does not"},{"line_number":90,"context_line":"support logging to Syslog currently.)  Naturally it is important that the logs"},{"line_number":91,"context_line":"of all the Kolla services should be collected by the logging system.  This"},{"line_number":92,"context_line":"proposal aims to address that issue."},{"line_number":93,"context_line":""}],"source_content_type":"text/x-rst","patch_set":6,"id":"9a68dd71_90de4cdb","line":90,"updated":"2016-01-25 21:03:25.000000000","message":"this rabbitmq info can be removed. There is a plugin that we decided to use during Tokyo summit that makes rabbitmq log to syslog. Nevertheless, rabbitmq today does not log to syslog","commit_id":"38771afe9f0a0d60cb10714cd33924a8cced6641"},{"author":{"_account_id":19300,"name":"Eric Lemoine","email":"elemoine@mirantis.com","username":"elemoine"},"change_message_id":"e80a434b7848ba886c9c74ce511223add182bc90","unresolved":false,"context_lines":[{"line_number":87,"context_line":""},{"line_number":88,"context_line":"Also, it is important to note that RabbitMQ logs are not available today.  This"},{"line_number":89,"context_line":"is related to RabbitMQ not writing its logs to Syslog.  (RabbitMQ just does not"},{"line_number":90,"context_line":"support logging to Syslog currently.)  Naturally it is important that the logs"},{"line_number":91,"context_line":"of all the Kolla services should be collected by the logging system.  This"},{"line_number":92,"context_line":"proposal aims to address that issue."},{"line_number":93,"context_line":""}],"source_content_type":"text/x-rst","patch_set":6,"id":"9a68dd71_6dcad170","line":90,"in_reply_to":"9a68dd71_90de4cdb","updated":"2016-01-26 09:22:22.000000000","message":"Do you mean you would remove that paragraph entirely?  Or do you mean you would remove that sentence between brackets?","commit_id":"38771afe9f0a0d60cb10714cd33924a8cced6641"},{"author":{"_account_id":6794,"name":"Simon Pasquier","email":"pasquier.simon@gmail.com","username":"simon-pasquier"},"change_message_id":"4a94574b1b013d90fae014d2c0ed2a25d8b3db52","unresolved":false,"context_lines":[{"line_number":87,"context_line":""},{"line_number":88,"context_line":"Also, it is important to note that RabbitMQ logs are not available today.  This"},{"line_number":89,"context_line":"is related to RabbitMQ not writing its logs to Syslog.  (RabbitMQ just does not"},{"line_number":90,"context_line":"support logging to Syslog currently.)  Naturally it is important that the logs"},{"line_number":91,"context_line":"of all the Kolla services should be collected by the logging system.  This"},{"line_number":92,"context_line":"proposal aims to address that issue."},{"line_number":93,"context_line":""}],"source_content_type":"text/x-rst","patch_set":6,"id":"9a68dd71_9bb41b83","line":90,"in_reply_to":"9a68dd71_90de4cdb","updated":"2016-01-26 08:50:58.000000000","message":"Out of curiosity, do you remember the name of the plugin? I looked at the Tokyo etherpads but failed to find a reference to it.","commit_id":"38771afe9f0a0d60cb10714cd33924a8cced6641"},{"author":{"_account_id":14119,"name":"Sam Yaple","email":"sam+git@yaple.net","username":"SamYaple"},"change_message_id":"580f28a71b402de70d3b8af48a033e3c4e7dc915","unresolved":false,"context_lines":[{"line_number":105,"context_line":""},{"line_number":106,"context_line":"* When ``DockerLogInput`` is used there is no way to differentiate log messages"},{"line_number":107,"context_line":"  for containers running multiple  processes.  ``neutron-agents`` is an example"},{"line_number":108,"context_line":"  of a multi-process container.  (Sam Yaple has raised that issue multiple"},{"line_number":109,"context_line":"  times.)"},{"line_number":110,"context_line":""},{"line_number":111,"context_line":"* If Heka is stopped and restarted later then log messages will be lost, as the"}],"source_content_type":"text/x-rst","patch_set":6,"id":"9a68dd71_b0d910f5","line":108,"updated":"2016-01-25 21:03:25.000000000","message":"This should be reworded to state something like \"containers that produce multiple log files\" rather than multiprocess since all of our containers are multiprocess","commit_id":"38771afe9f0a0d60cb10714cd33924a8cced6641"},{"author":{"_account_id":19300,"name":"Eric Lemoine","email":"elemoine@mirantis.com","username":"elemoine"},"change_message_id":"d64ef1c95ebc014575cad25d4505aa552d234175","unresolved":false,"context_lines":[{"line_number":105,"context_line":""},{"line_number":106,"context_line":"* When ``DockerLogInput`` is used there is no way to differentiate log messages"},{"line_number":107,"context_line":"  for containers running multiple  processes.  ``neutron-agents`` is an example"},{"line_number":108,"context_line":"  of a multi-process container.  (Sam Yaple has raised that issue multiple"},{"line_number":109,"context_line":"  times.)"},{"line_number":110,"context_line":""},{"line_number":111,"context_line":"* If Heka is stopped and restarted later then log messages will be lost, as the"}],"source_content_type":"text/x-rst","patch_set":6,"id":"7a5de9d1_60208e4a","line":108,"in_reply_to":"9a68dd71_b0d910f5","updated":"2016-01-27 11:32:48.000000000","message":"Done","commit_id":"38771afe9f0a0d60cb10714cd33924a8cced6641"},{"author":{"_account_id":14119,"name":"Sam Yaple","email":"sam+git@yaple.net","username":"SamYaple"},"change_message_id":"580f28a71b402de70d3b8af48a033e3c4e7dc915","unresolved":false,"context_lines":[{"line_number":123,"context_line":"other people have come across that issue [7]."},{"line_number":124,"context_line":""},{"line_number":125,"context_line":"Use local log files"},{"line_number":126,"context_line":"-------------------"},{"line_number":127,"context_line":""},{"line_number":128,"context_line":"Another option consists of configuring all the Kolla services to log into local"},{"line_number":129,"context_line":"files, and using Heka\u0027s ``LogstreamerInput`` plugin [5]."}],"source_content_type":"text/x-rst","patch_set":6,"id":"9a68dd71_50e454aa","line":126,"updated":"2016-01-25 21:03:25.000000000","message":"+2 for this option. I like this alot actually","commit_id":"38771afe9f0a0d60cb10714cd33924a8cced6641"},{"author":{"_account_id":14119,"name":"Sam Yaple","email":"sam+git@yaple.net","username":"SamYaple"},"change_message_id":"580f28a71b402de70d3b8af48a033e3c4e7dc915","unresolved":false,"context_lines":[{"line_number":144,"context_line":"For this option to be applicable all the services must have the capability of"},{"line_number":145,"context_line":"logging into files.  To our knowlegde all the Kolla services have this"},{"line_number":146,"context_line":"capability, so that shouldn\u0027t be a problem in practice.  In particular, this"},{"line_number":147,"context_line":"will fix the RabbitMQ problem, as RabbitMQ does support logging to a file."},{"line_number":148,"context_line":""},{"line_number":149,"context_line":"Also, this option obviously requires that the services have permissions to"},{"line_number":150,"context_line":"create log files in the Docker volume.  For this we propose to use an"}],"source_content_type":"text/x-rst","patch_set":6,"id":"9a68dd71_70df18d6","line":147,"updated":"2016-01-25 21:03:25.000000000","message":"Of note, keepalived and haproxy do _not_ have the ability to log to a file and _require_ syslog to log. So we have services that cannot log to syslog, and some that cannot log to file. Either way presents its issues","commit_id":"38771afe9f0a0d60cb10714cd33924a8cced6641"},{"author":{"_account_id":19300,"name":"Eric Lemoine","email":"elemoine@mirantis.com","username":"elemoine"},"change_message_id":"7ac65d1dc1fb2ae221584dcbbdcd586e24f90a92","unresolved":false,"context_lines":[{"line_number":144,"context_line":"For this option to be applicable all the services must have the capability of"},{"line_number":145,"context_line":"logging into files.  To our knowlegde all the Kolla services have this"},{"line_number":146,"context_line":"capability, so that shouldn\u0027t be a problem in practice.  In particular, this"},{"line_number":147,"context_line":"will fix the RabbitMQ problem, as RabbitMQ does support logging to a file."},{"line_number":148,"context_line":""},{"line_number":149,"context_line":"Also, this option obviously requires that the services have permissions to"},{"line_number":150,"context_line":"create log files in the Docker volume.  For this we propose to use an"}],"source_content_type":"text/x-rst","patch_set":6,"id":"7a5de9d1_70622040","line":147,"in_reply_to":"9a68dd71_218f0277","updated":"2016-01-29 13:13:21.000000000","message":"Now covered by the spec.","commit_id":"38771afe9f0a0d60cb10714cd33924a8cced6641"},{"author":{"_account_id":19300,"name":"Eric Lemoine","email":"elemoine@mirantis.com","username":"elemoine"},"change_message_id":"e80a434b7848ba886c9c74ce511223add182bc90","unresolved":false,"context_lines":[{"line_number":144,"context_line":"For this option to be applicable all the services must have the capability of"},{"line_number":145,"context_line":"logging into files.  To our knowlegde all the Kolla services have this"},{"line_number":146,"context_line":"capability, so that shouldn\u0027t be a problem in practice.  In particular, this"},{"line_number":147,"context_line":"will fix the RabbitMQ problem, as RabbitMQ does support logging to a file."},{"line_number":148,"context_line":""},{"line_number":149,"context_line":"Also, this option obviously requires that the services have permissions to"},{"line_number":150,"context_line":"create log files in the Docker volume.  For this we propose to use an"}],"source_content_type":"text/x-rst","patch_set":6,"id":"9a68dd71_218f0277","line":147,"in_reply_to":"9a68dd71_70df18d6","updated":"2016-01-26 09:22:22.000000000","message":"I had missed that. Thanks.\n\nSo if we want to handle keepalived and haproxy then we need to have something that can handle Syslog.  We could possibly use Heka for that, relying on its UdpInput plugin [*].  We currently have no experience with this plugin, so I\u0027m going to do tests.\n\n(For the note, it seems to me that Kolla doesn\u0027t currently collect logs from keepalived and haproxy.)\n\n[*] \u003chttps://github.com/mozilla-services/heka/issues/790\u003e","commit_id":"38771afe9f0a0d60cb10714cd33924a8cced6641"},{"author":{"_account_id":2928,"name":"Patrick Petit","email":"ppetit@opennext.io","username":"patrick-michel-petit"},"change_message_id":"7de9406ae739640a9965821be3b30b4e3ed481f3","unresolved":false,"context_lines":[{"line_number":150,"context_line":"create log files in the Docker volume.  For this we propose to use an"},{"line_number":151,"context_line":"``extend_start.sh`` script in the Heka container.  That script will use ``sudo"},{"line_number":152,"context_line":"chown`` and ``sudo chmod`` to set the appropriate owner, group and permissions"},{"line_number":153,"context_line":"on the Docker volume.  More specifically our plan is to use ``kolla`` as the"},{"line_number":154,"context_line":"group of the volume directory, and use the ``setuid`` permission on the volume"},{"line_number":155,"context_line":"directory so that files created within the volume inherit its group id.  Note"},{"line_number":156,"context_line":"that this sort of technique is already used in Kolla.  See [8] for example."}],"source_content_type":"text/x-rst","patch_set":6,"id":"9a68dd71_e916ac57","line":153,"updated":"2016-01-26 15:06:56.000000000","message":"But you can\u0027t since the volume is mounted ro in the Heka container. I know we already discussed this but to avoid others to make the same comment I leave it here anyway.","commit_id":"38771afe9f0a0d60cb10714cd33924a8cced6641"},{"author":{"_account_id":19300,"name":"Eric Lemoine","email":"elemoine@mirantis.com","username":"elemoine"},"change_message_id":"d64ef1c95ebc014575cad25d4505aa552d234175","unresolved":false,"context_lines":[{"line_number":150,"context_line":"create log files in the Docker volume.  For this we propose to use an"},{"line_number":151,"context_line":"``extend_start.sh`` script in the Heka container.  That script will use ``sudo"},{"line_number":152,"context_line":"chown`` and ``sudo chmod`` to set the appropriate owner, group and permissions"},{"line_number":153,"context_line":"on the Docker volume.  More specifically our plan is to use ``kolla`` as the"},{"line_number":154,"context_line":"group of the volume directory, and use the ``setuid`` permission on the volume"},{"line_number":155,"context_line":"directory so that files created within the volume inherit its group id.  Note"},{"line_number":156,"context_line":"that this sort of technique is already used in Kolla.  See [8] for example."}],"source_content_type":"text/x-rst","patch_set":6,"id":"7a5de9d1_401792ed","line":153,"in_reply_to":"9a68dd71_4c09f4dc","updated":"2016-01-27 11:32:48.000000000","message":"Done","commit_id":"38771afe9f0a0d60cb10714cd33924a8cced6641"},{"author":{"_account_id":19300,"name":"Eric Lemoine","email":"elemoine@mirantis.com","username":"elemoine"},"change_message_id":"0f6747df7e866f2a8fce95a3e3aecbce6600d136","unresolved":false,"context_lines":[{"line_number":150,"context_line":"create log files in the Docker volume.  For this we propose to use an"},{"line_number":151,"context_line":"``extend_start.sh`` script in the Heka container.  That script will use ``sudo"},{"line_number":152,"context_line":"chown`` and ``sudo chmod`` to set the appropriate owner, group and permissions"},{"line_number":153,"context_line":"on the Docker volume.  More specifically our plan is to use ``kolla`` as the"},{"line_number":154,"context_line":"group of the volume directory, and use the ``setuid`` permission on the volume"},{"line_number":155,"context_line":"directory so that files created within the volume inherit its group id.  Note"},{"line_number":156,"context_line":"that this sort of technique is already used in Kolla.  See [8] for example."}],"source_content_type":"text/x-rst","patch_set":6,"id":"9a68dd71_4c09f4dc","line":153,"in_reply_to":"9a68dd71_e916ac57","updated":"2016-01-26 15:50:40.000000000","message":"You are right.  I need to change that.  As also discussed it may make sense to use a data only container here, to be able to mount the volume in read-only mode in the Heka container.","commit_id":"38771afe9f0a0d60cb10714cd33924a8cced6641"},{"author":{"_account_id":6794,"name":"Simon Pasquier","email":"pasquier.simon@gmail.com","username":"simon-pasquier"},"change_message_id":"4a94574b1b013d90fae014d2c0ed2a25d8b3db52","unresolved":false,"context_lines":[{"line_number":179,"context_line":"as well.  For that we propose to mount the host\u0027s ``/var/log`` directory into"},{"line_number":180,"context_line":"the Heka container, and configure Heka to get logs from standard log files"},{"line_number":181,"context_line":"located in that directory (e.g. ``kern.log``, ``auth.log``, ``messages``).  The"},{"line_number":182,"context_line":"list of system log files will be determined when at development time."},{"line_number":183,"context_line":""},{"line_number":184,"context_line":"Log rotation"},{"line_number":185,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":6,"id":"9a68dd71_700ac28b","line":182,"range":{"start_line":182,"start_character":44,"end_line":182,"end_character":48},"updated":"2016-01-26 08:50:58.000000000","message":"remove?","commit_id":"38771afe9f0a0d60cb10714cd33924a8cced6641"},{"author":{"_account_id":19300,"name":"Eric Lemoine","email":"elemoine@mirantis.com","username":"elemoine"},"change_message_id":"d64ef1c95ebc014575cad25d4505aa552d234175","unresolved":false,"context_lines":[{"line_number":179,"context_line":"as well.  For that we propose to mount the host\u0027s ``/var/log`` directory into"},{"line_number":180,"context_line":"the Heka container, and configure Heka to get logs from standard log files"},{"line_number":181,"context_line":"located in that directory (e.g. ``kern.log``, ``auth.log``, ``messages``).  The"},{"line_number":182,"context_line":"list of system log files will be determined when at development time."},{"line_number":183,"context_line":""},{"line_number":184,"context_line":"Log rotation"},{"line_number":185,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":6,"id":"7a5de9d1_e0d23e34","line":182,"in_reply_to":"9a68dd71_700ac28b","updated":"2016-01-27 11:32:48.000000000","message":"Done","commit_id":"38771afe9f0a0d60cb10714cd33924a8cced6641"},{"author":{"_account_id":14119,"name":"Sam Yaple","email":"sam+git@yaple.net","username":"SamYaple"},"change_message_id":"580f28a71b402de70d3b8af48a033e3c4e7dc915","unresolved":false,"context_lines":[{"line_number":189,"context_line":"The work on Heka proposed in this spec isn\u0027t directly related to log rotation,"},{"line_number":190,"context_line":"but we are suggesting to address this issue for Mitaka.  This will mean"},{"line_number":191,"context_line":"creating a new container that uses ``logrotate`` to manage the log files"},{"line_number":192,"context_line":"created by the Kolla containers."},{"line_number":193,"context_line":""},{"line_number":194,"context_line":"Create an ``heka`` user"},{"line_number":195,"context_line":"-----------------------"}],"source_content_type":"text/x-rst","patch_set":6,"id":"9a68dd71_10f1fc6a","line":192,"updated":"2016-01-25 21:03:25.000000000","message":"Perhaps changing kolla-ansible to a kolla-toolbox container (already suggested) and running logrotate in there since it currently does not perform any actions but `/bin/sleep infinity`","commit_id":"38771afe9f0a0d60cb10714cd33924a8cced6641"},{"author":{"_account_id":19300,"name":"Eric Lemoine","email":"elemoine@mirantis.com","username":"elemoine"},"change_message_id":"e80a434b7848ba886c9c74ce511223add182bc90","unresolved":false,"context_lines":[{"line_number":189,"context_line":"The work on Heka proposed in this spec isn\u0027t directly related to log rotation,"},{"line_number":190,"context_line":"but we are suggesting to address this issue for Mitaka.  This will mean"},{"line_number":191,"context_line":"creating a new container that uses ``logrotate`` to manage the log files"},{"line_number":192,"context_line":"created by the Kolla containers."},{"line_number":193,"context_line":""},{"line_number":194,"context_line":"Create an ``heka`` user"},{"line_number":195,"context_line":"-----------------------"}],"source_content_type":"text/x-rst","patch_set":6,"id":"9a68dd71_2d4a99ad","line":192,"in_reply_to":"9a68dd71_10f1fc6a","updated":"2016-01-26 09:22:22.000000000","message":"Yep, that may make sense.","commit_id":"38771afe9f0a0d60cb10714cd33924a8cced6641"},{"author":{"_account_id":6794,"name":"Simon Pasquier","email":"pasquier.simon@gmail.com","username":"simon-pasquier"},"change_message_id":"4a94574b1b013d90fae014d2c0ed2a25d8b3db52","unresolved":false,"context_lines":[{"line_number":203,"context_line":"---------------"},{"line_number":204,"context_line":""},{"line_number":205,"context_line":"Heka is a mature product maintained and used in production by Mozilla.  So we"},{"line_number":206,"context_line":"trust Heka a being secure.  We also trust the Heka developers as being serious"},{"line_number":207,"context_line":"should security vulnerabilities be found in the Heka code."},{"line_number":208,"context_line":""},{"line_number":209,"context_line":"As described above we are proposing to use a Docker volume between the service"}],"source_content_type":"text/x-rst","patch_set":6,"id":"9a68dd71_5640ba35","line":206,"range":{"start_line":206,"start_character":11,"end_line":206,"end_character":12},"updated":"2016-01-26 08:50:58.000000000","message":"as","commit_id":"38771afe9f0a0d60cb10714cd33924a8cced6641"},{"author":{"_account_id":19300,"name":"Eric Lemoine","email":"elemoine@mirantis.com","username":"elemoine"},"change_message_id":"d64ef1c95ebc014575cad25d4505aa552d234175","unresolved":false,"context_lines":[{"line_number":203,"context_line":"---------------"},{"line_number":204,"context_line":""},{"line_number":205,"context_line":"Heka is a mature product maintained and used in production by Mozilla.  So we"},{"line_number":206,"context_line":"trust Heka a being secure.  We also trust the Heka developers as being serious"},{"line_number":207,"context_line":"should security vulnerabilities be found in the Heka code."},{"line_number":208,"context_line":""},{"line_number":209,"context_line":"As described above we are proposing to use a Docker volume between the service"}],"source_content_type":"text/x-rst","patch_set":6,"id":"7a5de9d1_c0e14200","line":206,"in_reply_to":"9a68dd71_5640ba35","updated":"2016-01-27 11:32:48.000000000","message":"Done","commit_id":"38771afe9f0a0d60cb10714cd33924a8cced6641"},{"author":{"_account_id":14119,"name":"Sam Yaple","email":"sam+git@yaple.net","username":"SamYaple"},"change_message_id":"580f28a71b402de70d3b8af48a033e3c4e7dc915","unresolved":false,"context_lines":[{"line_number":253,"context_line":"Target Milestone for completion: Mitaka 3 (March 4th, 2016)."},{"line_number":254,"context_line":""},{"line_number":255,"context_line":"Work Items"},{"line_number":256,"context_line":"----------"},{"line_number":257,"context_line":""},{"line_number":258,"context_line":"1. Create an Heka Docker image"},{"line_number":259,"context_line":"2. Create an Heka configuration for Kolla"}],"source_content_type":"text/x-rst","patch_set":6,"id":"9a68dd71_30f44059","line":256,"updated":"2016-01-25 21:03:25.000000000","message":"Does this _include_ integration with Elasticsearch and Kibana? Or is this just Heka implementation?","commit_id":"38771afe9f0a0d60cb10714cd33924a8cced6641"},{"author":{"_account_id":19300,"name":"Eric Lemoine","email":"elemoine@mirantis.com","username":"elemoine"},"change_message_id":"d64ef1c95ebc014575cad25d4505aa552d234175","unresolved":false,"context_lines":[{"line_number":253,"context_line":"Target Milestone for completion: Mitaka 3 (March 4th, 2016)."},{"line_number":254,"context_line":""},{"line_number":255,"context_line":"Work Items"},{"line_number":256,"context_line":"----------"},{"line_number":257,"context_line":""},{"line_number":258,"context_line":"1. Create an Heka Docker image"},{"line_number":259,"context_line":"2. Create an Heka configuration for Kolla"}],"source_content_type":"text/x-rst","patch_set":6,"id":"7a5de9d1_00943a35","line":256,"in_reply_to":"9a68dd71_30f44059","updated":"2016-01-27 11:32:48.000000000","message":"Done\n\nI also added an item about making the Heka container upgradable.","commit_id":"38771afe9f0a0d60cb10714cd33924a8cced6641"},{"author":{"_account_id":19300,"name":"Eric Lemoine","email":"elemoine@mirantis.com","username":"elemoine"},"change_message_id":"e80a434b7848ba886c9c74ce511223add182bc90","unresolved":false,"context_lines":[{"line_number":253,"context_line":"Target Milestone for completion: Mitaka 3 (March 4th, 2016)."},{"line_number":254,"context_line":""},{"line_number":255,"context_line":"Work Items"},{"line_number":256,"context_line":"----------"},{"line_number":257,"context_line":""},{"line_number":258,"context_line":"1. Create an Heka Docker image"},{"line_number":259,"context_line":"2. Create an Heka configuration for Kolla"}],"source_content_type":"text/x-rst","patch_set":6,"id":"9a68dd71_edf1e16b","line":256,"in_reply_to":"9a68dd71_30f44059","updated":"2016-01-26 09:22:22.000000000","message":"I think the integration with Elasticsearch and Kibana is part of this work.  This is an oversight from me.  Thanks for catching this.","commit_id":"38771afe9f0a0d60cb10714cd33924a8cced6641"},{"author":{"_account_id":14119,"name":"Sam Yaple","email":"sam+git@yaple.net","username":"SamYaple"},"change_message_id":"ec6db9710d17be647901ebcc531e3b6aa7cd643a","unresolved":false,"context_lines":[{"line_number":148,"context_line":""},{"line_number":149,"context_line":"Also, this option requires that the services have the permission to create"},{"line_number":150,"context_line":"files into the Docker volume, and that Heka has the permission to read these"},{"line_number":151,"context_line":"files.  For this our proposition is to use a data-only container, whose volume"},{"line_number":152,"context_line":"will be mounted into the service containers in read-write mode and into the"},{"line_number":153,"context_line":"Heka container in read-only mode.  The data-only container image will use the"},{"line_number":154,"context_line":"Kolla base image as its base image, to be able to set the group of the volume"}],"source_content_type":"text/x-rst","patch_set":8,"id":"7a5de9d1_2a41fb0b","line":151,"updated":"2016-01-27 19:01:42.000000000","message":"Im confused as to the introduction of the data-only container again. We have moved away from that, instead relying on named volumes. data containers have issue and are not suited for this task","commit_id":"7f42aa1c596b46d476f6bf7008bc639e62b288c1"},{"author":{"_account_id":19300,"name":"Eric Lemoine","email":"elemoine@mirantis.com","username":"elemoine"},"change_message_id":"f21eeb6f4b549e3f6b8d4230dbc071f1327edcf0","unresolved":false,"context_lines":[{"line_number":148,"context_line":""},{"line_number":149,"context_line":"Also, this option requires that the services have the permission to create"},{"line_number":150,"context_line":"files into the Docker volume, and that Heka has the permission to read these"},{"line_number":151,"context_line":"files.  For this our proposition is to use a data-only container, whose volume"},{"line_number":152,"context_line":"will be mounted into the service containers in read-write mode and into the"},{"line_number":153,"context_line":"Heka container in read-only mode.  The data-only container image will use the"},{"line_number":154,"context_line":"Kolla base image as its base image, to be able to set the group of the volume"}],"source_content_type":"text/x-rst","patch_set":8,"id":"7a5de9d1_ec776d00","line":151,"in_reply_to":"7a5de9d1_2a41fb0b","updated":"2016-01-28 07:43:35.000000000","message":"I was expecting this comment.  I wanted to give \"data-only containers\" a try, to see if that could help me meet my requirements, and that sort of did.\n\nMy requirements are:\n\n* have the service containers write logs to a shared volume\n* have the Heka container read logs from that shared volume\n* use a non-root user to run the hekad daemon\n\nWith a named volume I have to use sudo commands in an extend_start.sh script of the Heka container.  I wanted to see if I could use a data-only container to avoid that \"sudo mess\".\n\nBut, although I\u0027d like to know more about the issues you\u0027ve had with data containers, I\u0027m fine to go back to a named volume and the \"sudo\" dance.\n\nThanks for your comment.","commit_id":"7f42aa1c596b46d476f6bf7008bc639e62b288c1"}]}