[Container-tools] Package ELK stack example using Atomicapp

[John Mark Walker]

----- Original Message -----
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On 08/06/15 09:18, Lalatendu Mohanty wrote:
> > On 06/08/2015 12:31 PM, Archit Sharma wrote:
> >> Hi,
> >> 
> >> So an idea came up to package the ELK stack [1] (which seems to
> >> be a common use-case) using atomic app, and then we could add it
> >> as an example under |nulecule/examples/|.
> >> 
> >> I'm willing to become a secondary owner for this issue, under
> >> guidance from a primary one, since I don't have much knowledge of
> >> atomicapp. I've raised an issue for the same [2].
> >> 
> >> Thoughts?
> >> 
> > 
> > Sounds interesting to me. Though I am not an expert in Nulecule as
> > of now, but I want to give it a try.
> > 
> >> Refs: [1] https://www.elastic.co/webinars/introduction-elk-stack
> >> [2] https://github.com/projectatomic/nulecule/issues/99
> >> 
> >> Cheers, Archit Sharma Associate Performance Engineer /
> >> [RHCE/RHCSA]
> >> 
> > 
> 
> Well, the ELK stack is interesting, but will probably not be the
> easiest one either.
> all components from the ELK stack aren't really available directly as
> RPM packages, except if we consider the ones available "upstream"
> (directly at Elasticsearch) but not really "packaged" but rather just
> combined into .rpm through fpm.

This is true, but not relevant for Nulecule purposes. I don't think we want "lack of RPMs" to be a blocker to packaging for Atomic App. 

Getting the software from upstream is easy enough, and we have quite a few connections to Elastic to help us if we need it. In fact, we should just start looping them in.

-JM