> Yeah I would +1 katakoda. Has anyone used or have a history with KataKoda? I'd hate to invest time in a hosted solution if the provider isn't going to be around. That's a definite 'con' to taking that approach.
Although most of the effort would be invested in "Metron on Docker" which might have value outside of KataKoda. And some level of work has already been done on Docker. > I also think that it would help to start distributing RPMs, DEBs, and the mpacks with the releases.. Agreed. I was thinking that whatever solution falls out of this discussion might require RPMs, DEBs, Maven Central, etc as prerequisites. Although each of those have value in their own right. On Fri, Oct 26, 2018 at 1:42 PM zeo...@gmail.com <zeo...@gmail.com> wrote: > Yeah I would +1 katakoda. I also think that it would help to start > distributing RPMs, DEBs, and the mpacks with the releases, as well as > consider a service like opensuse's build service for nightlies, etc. > > Jon > > On Fri, Oct 26, 2018 at 6:25 AM Anand Subramanian < > asubraman...@hortonworks.com> wrote: > > > Great idea! This will be a HUGE improvement in the user experience for > > first timers to Metron. Katakoda seems very interesting - simple and > > straight-forward. I loved the way you can provide instructions, commands > > (that can be directly clicked!), links, explanation and so on. > > > > Regards, > > Anand > > > > On 10/25/18, 7:49 PM, "Nick Allen" <n...@nickallen.org> wrote: > > > > We all know spinning up the development environment is a pain. > > Unfortunately, it is the only way for a new user to get a feel for > > Metron. > > We need a better way to introduce new users to Metron. > > > > I am hoping we can brainstorm ways to improve that experience. Here > > are a > > few thoughts that might help start a discussion. > > > > (1) Create a *KataKoda* [1] based demo. I ran across this after > > finding > > Apache Ozone's demo [2], which I think is great. > > > > > > - A user does not need to download or install anything. It is a > > completely hosted offering. > > - Provides a step-by-step demo experience that could guide > users > > through creating an enrichment, defining a profile, managing > > alerts. > > - Would require a Metron on Docker solution. > > > > (2) Create a *Vagrant Cloud* [3] hosted image of "Full Dev" with > > everything > > installed and ready to rock. A user would just need to install > > Vagrant and > > run: > > > > vagrant init metron/0.6.0 > > > > vagrant up > > > > > > - Reduces the number of dependencies needed to get Metron > > up-and-running. > > - Significantly increases the success rate of new users getting > > Metron running. > > - Still results in "Full Dev" Metron which requires too many > > resources for the average computer. > > > > Are these good options? What other approaches could we take? > Hopefully > > some JIRAs might fall out of this discussion. > > > > - Nick > > > > > > -- > > [1] https://www.katacoda.com > > [2] https://www.katacoda.com/elek/scenarios/ozone101 > > [3] https://app.vagrantup.com/boxes/search > > > > > > -- > > Jon Zeolla >
