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

Michał Jastrzębski inc007 at gmail.com
Thu Feb 4 14:22:04 UTC 2016

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, otherwise I'd be -1 to this, we
don't want to add dependency here. Also we're looking at pretty simple
set of files that won't change anytime soon probably. Also we might
introduce new service that fuel does not have, and while I'm sure we
can push new file to this repo, it's bigger issue than just coding it
in tree.


On 4 February 2016 at 07:45, Michal Rostecki <mrostecki at mirantis.com> wrote:
> On 02/04/2016 10:55 AM, Eric LEMOINE wrote:
>> 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 packages in the future.  This will allow to easily
>> share the Lua plugins between projects, and having a separate Git repo
>> will facilitate testing, documentation, etc.
>> But we may not have time to do that by the 4th of March (for Mitaka
>> 3), so my suggestion is to copy the Lua plugins that we need in Kolla.
>> This would be a temporary thing.  When our Lua plugins are
>> available/distributed as deb and rpm packages we will remove the Lua
>> plugins from the kolla repository and change the Heka Dockerfile to
>> install the Lua plugins from the package.
>> Please tell me if you agree with the approach.  Thank you!
>> [*]
>> <https://github.com/openstack/fuel-plugin-lma-collector/tree/master/deployment_scripts/puppet/modules/lma_collector/files/plugins/decoders>
> +1
> But of course when git repos will be available (even without packaging), I'd
> switch to them immediately.
> Cheers,
> Michal
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

More information about the OpenStack-dev mailing list