[openstack-dev] [kolla] Location of Heka Lua plugins
Steven Dake (stdake)
stdake at cisco.com
Thu Feb 4 19:59:55 UTC 2016
I agree with Michael. If the LUA plugins are going to be a separate
repository, they need to be in the OpenStack git namespace. I am +2 to
the idea assuming after extraction of the LUA plugins they hit the
OpenStack git namespace.
On 2/4/16, 7:22 AM, "Michał Jastrzębski" <inc007 at gmail.com> 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, 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
>On 4 February 2016 at 07:45, Michal Rostecki <mrostecki at mirantis.com>
>> On 02/04/2016 10:55 AM, Eric LEMOINE wrote:
>>> 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!
>> But of course when git repos will be available (even without
>> switch to them immediately.
>> OpenStack Development Mailing List (not for usage questions)
>>OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
More information about the OpenStack-dev