[Container-tools] Package ELK stack example using Atomicapp

[Karanbir Singh]

On 08/06/15 16:21, Bill Burns wrote:
> 
> 
> On 06/08/2015 10:44 AM, Daniel Riek wrote:
>> Or so I thought...
> 
> Yes, I send out the request last Wed at the engineering coordination
> meeting, followed up with minutes and an email to the eng-common-logging
> list. Interested folks have started to reach out and thus these emails on
> container tools. Cc'in the common-logging list on this thread.

We are happy to front the user-story for this effort in the CentOS infra
team - we have been looking at ELK for a while and would be very willing
to do our implemention based on the content being created here as atomicapp.

> 
> How about folks interested join the Wed 3:30 pm Eastern call and we
> can coordinate there. Let me know if you need to be added to the invite.

that might be harder for people who dont actually work at Red Hat ( you
are posting to a public list.. )

> 
> cheers,
>  Bill
> 
> 
>>
>> On 06/08/2015 10:16 AM, Daniel Riek wrote:
>>> Adding bill who is coordinating our log aggregation / analysis work
>>> across tje products and was looking for volunteers for this.
>>>
>>>
>>> Sent from my T-Mobile 4G LTE Device
>>>
>>>
>>> -------- Original message --------
>>> From: John Mark Walker <jowalker at redhat.com>
>>> Date:06/08/2015 09:17 (GMT-05:00)
>>> To: Fabian Arrotin <fabian.arrotin at redhat.com>
>>> Cc: container-tools at redhat.com
>>> Subject: Re: [Container-tools] Package ELK stack example using Atomicapp
>>>
>>>
>>>
>>> ----- 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
>>>
>>>
>>> _______________________________________________
>>> Container-tools mailing list
>>> Container-tools at redhat.com
>>> https://www.redhat.com/mailman/listinfo/container-tools
>>>
>>>
>>> _______________________________________________
>>> Container-tools mailing list
>>> Container-tools at redhat.com
>>> https://www.redhat.com/mailman/listinfo/container-tools
>>
> 
> 
> 
> _______________________________________________
> Container-tools mailing list
> Container-tools at redhat.com
> https://www.redhat.com/mailman/listinfo/container-tools
> 


-- 
Karanbir Singh, The CentOS Project, London, UK
RH Ext. 8274455 | DID: 0044 207 009 4455