Re: [openstack-dev] [kolla] Vagrant environment for kolla-kubernetes

On Fri, May 13, 2016 at 10:36 AM, Martin André wrote: > On Fri, May 13, 2016 at 8:57 AM, Britt Houser (bhouser) > wrote: >> Would we ever run AIO-k8s vagrant w/o Kolla repo? If not, then it makes >> sense to me just to extend Vagrant kolla repo. > > Agreed. Vagrant is for developers and develop

Re: [openstack-dev] [kolla][vote] Proposing Alicja Kwasniewska for core reviewer

+1 Looking forward to more collaboration on Diagnostics and other stuff :) Le 4 mars 2016 17:58, "Steven Dake (stdake)" a écrit : > > Core Reviewers, > > Alicja has been instrumental in our work around jinja2 docker file creation, removing our symlink madness. She has also been instrumental in

[openstack-dev] [kolla][logging] log rotation

Hi Kolla devs So with the Heka work services write their logs into files (in the "kolla_logs" volume). This means that we need log rotation. This was mentioned in the "logging-with-heka" spec [*]. I've just created a change request [**] that adds a "cron" Dockerfile and Ansible tasks/plays to dep

Re: [openstack-dev] [kolla] discussion about core reviewer limitations by company

Le 20 févr. 2016 18:12, "Steven Dake (stdake)" a écrit : > > Hey folks, > > Mirantis has been developing a big footprint in the core review team, and Red Hat already has a big footprint in the core review team. These are all good things, but I want to avoid in the future a situation in which one

Re: [openstack-dev] [kolla] Make "central logging" optional

On Fri, Feb 5, 2016 at 4:46 PM, Eric LEMOINE wrote: > Hi Kolla devs > > The other day inc0 said that we would like "central logging" to be > optional in Mitaka, and still use Rsyslog and keep the current > behavior if "central logging" is disabled. > &g

Re: [openstack-dev] [kolla] Location of Heka Lua plugins

Le 6 févr. 2016 20:39, "Steven Dake (stdake)" a écrit : > > > > On 2/5/16, 1:14 AM, "Eric LEMOINE" wrote: > > >On Thu, Feb 4, 2016 at 5:13 PM, Jeff Peeler wrote: > >I totally agree with you Jeff. > > > >It is to be noted that we (my tea

[openstack-dev] [kolla] Make "central logging" optional

Hi Kolla devs The other day inc0 said that we would like "central logging" to be optional in Mitaka, and still use Rsyslog and keep the current behavior if "central logging" is disabled. I would like to propose an alternative, where we do remove Rsyslog as planned in the spec. I like the idea of

Re: [openstack-dev] [kolla] Location of Heka Lua plugins

On Thu, Feb 4, 2016 at 5:13 PM, Jeff Peeler wrote: > On Thu, Feb 4, 2016 at 9:22 AM, Michał Jastrzębski wrote: >> TLDR; +1 to have lua in tree of kolla, not sure if we want to switch later >> >> So I'm not so sure about switching. If these git repos are in >> /openstack/ namespace, then sure, oth

[openstack-dev] [kolla] Location of Heka Lua plugins

Hi As discussed yesterday in our IRC meeting we'll need specific Lua plugins for parsing OpenStack, MariaDB and RabbitMQ logs. We already have these Lua plugins in one of our Fuel plugins [*]. So our plan is to move these Lua plugins in their own Git repo, and distribute them as deb and rpm pack

[openstack-dev] [kolla] Heka POC

Hi Kolla devs So I've identified the following tests/POCs: * Verify Heka can read logs from containers that log to stdout * Verify Heka can read logs from containers that log to Syslog (/dev/log) * Verify Heka can write logs to local files (as currently done using Rsyslog) If these three POCs "s

Re: [openstack-dev] [kolla] Heka v ELK stack logistics

On Fri, Jan 15, 2016 at 2:40 PM, Michał Jastrzębski wrote: > Yeah that's true. We did all of openstack systems but we didn't > implement infra around yet. I'd guess most of services can log either > to stdout or file, and both sources should be accessible by heka. > Also, I'd be surprised if heka

Re: [openstack-dev] [kolla] Heka v ELK stack logistics

On Fri, Jan 15, 2016 at 11:57 AM, Michal Rostecki wrote: > On 01/15/2016 11:14 AM, Simon Pasquier wrote: >> >> My 2 cents on RabbitMQ logging... >> >> On Fri, Jan 15, 2016 at 8:39 AM, Michal Rostecki > > wrote: >> >> I'd suggest to check the similar options in Ra

Re: [openstack-dev] [kolla] Heka v ELK stack logistics

> > In case of MariaDB I see that you can > > - do --skip-syslog, then all things go to "error log" > - set "error log" path by --log-error > > So maybe setting stdout/stderr may work here? > > I'd suggest to check the similar options in RabbitMQ and other non-OpenStack > components. > > I may help

Re: [openstack-dev] [kolla] Heka v ELK stack logistics

On Wed, Jan 13, 2016 at 1:15 PM, Steven Dake (stdake) wrote: > Hey folks, > > I'd like to have a mailing list discussion about logistics of the ELKSTACK > solution that Alicja has sorted out vs the Heka implementation that Eric is > proposing. > > My take on that is Eric wants to replace rsyslog a

Re: [openstack-dev] [kolla] Can Heka solve all the deficiencies in the current rsyslog implementation: was Re: [kolla] Introduction of Heka in Kolla

On Wed, Jan 13, 2016 at 1:27 PM, Steven Dake (stdake) wrote: > Eric, Hi Steven > > Apologies for top post, not really sure where in this thread to post this > list of questions as its sort of a change in topic so I changed the > subject line :) > > 1. > Somewhere I read when researching this H

Re: [openstack-dev] [kolla] Introduction of Heka in Kolla

document #3 (the design document) in gerrit rather than google > docs in the main kolla repo as a spec using our special snowflake (read > less cumbersome) spec template. Sure. The Google doc is a temporary thing. > On 1/11/16, 8:16 AM, "Eric LEMOINE" wrote: >>In th

Re: [openstack-dev] [kolla] Introduction of Heka in Kolla

Hi Alicja Thank you for your comments. Answers and comments below. On Tue, Jan 12, 2016 at 1:19 PM, Kwasniewska, Alicja wrote: > Unfortunately I do not have any experience in working or testing Heka, so > it’s hard for me to compare its performance vs Logstash performance. However > I’ve rea

Re: [openstack-dev] [kolla] Introduction of Heka in Kolla

On Tue, Jan 12, 2016 at 5:36 PM, Michał Jastrzębski wrote: > So tracebacks sort of works, they're there just ugly. That's why I'm > also happy if we change rsyslog to heka. > > Eric, I hope I wont ask too much, but could you please prepare PoC of > kolla+heka, for what I care heka can log to local

Re: [openstack-dev] [kolla] Introduction of Heka in Kolla

Le 11 janv. 2016 18:45, "Michał Jastrzębski" a écrit : > > On 11 January 2016 at 10:55, Eric LEMOINE wrote: > > Currently the services running in containers send their logs to > > rsyslog. And rsyslog stores the logs in local files, located in the > > host'

Re: [openstack-dev] [kolla] Introduction of Heka in Kolla

On Mon, Jan 11, 2016 at 5:01 PM, Michał Jastrzębski wrote: > On 11 January 2016 at 09:16, Eric LEMOINE wrote: >> * Logstash was designed for logs processing. Heka is a "unified data >> processing" software, designed to process streams of any type of data. >&g

[openstack-dev] [kolla] Introduction of Heka in Kolla

Hi As discussed on IRC the other day [1] we want to propose a distributed logs processing architecture based on Heka [2], built on Alicja Kwasniewska's ELK work with . Please take a look at the design document I've started working on [3]. The document is