The vendor distribution mechanism for Logstash is JAR only; thus, an RPM must be created that can be implemented in our environment in a sane, compatible, re-usable way. Hint : https://github.com/mhorbul/logstash-rpm
Is this in EPEL or rpmforge, perhaps? Having a SPEC file to start from helps a lot, but I don't like getting into situations where we have to maintain our own packages... historically, that tends to mean packages just don't get maintained. Better packaged by us than not at all, though. :)
(In reply to Jake Maul [:jakem] from comment #1) > Is this in EPEL or rpmforge, perhaps? Sadly, it is not; however, there is actually already a package in the Mozilla repo, so I'm going to look into that further.
The package was built on an external server by somebody who no longer works for Mozilla. Long story short: we'll have to roll our own (not a problem). There was also some discussion on IRC as to whether we should make the package public, or even go so far as to become the official package maintainer for an RPM release of Logstash. We should really get in touch with Jordan before we get ahead of ourselves on this front. :)
I reviewed a number of the logstash-rpm repos extant on Github (we're certainly not short on options here, that's for sure), and ended up going with this one : https://github.com/lfrancke/logstash-rpm It's clean, standards-compliant, and most importantly, doesn't try to do anything too fancy. Long story short, I built the (S)RPM packages in a normal rpmbuild environment on hp-admin01; the only necessary change from lfrancke's spec file was updating the Logstash version number. The packages are now available in our normal repo : $ sudo yum info logstash.noarch | egrep "(Version|Repo)" Version : 1.1.9 Repo : mozilla
I made some minor adjustments to lfrancke's repo : https://github.com/phrawzty/logstash-rpm The packages have been re-built and inserted into mrepo.