You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nifi.apache.org by Joe Witt <jo...@gmail.com> on 2015/05/13 16:01:54 UTC
From apache nifi (incubating) site to running nifi in fewest clicks...
All,
Yesterday I had a chance to talk to a really cool startup with awesome
developers who gave some great feedback on nifi. One of the things
they mentioned was how much they loved the UI. In fact they said if
they hadn't seen the reference to the UI they would have said
'interesting' and moved on but not really followed up.
The point they made is we should make it as easy as possible to get
from landing on the apache nifi webpage to having an up and running
instance of NiFi for them to get to start playing with the UI.
I'd like to put this out there to get a sense of how people see this
being most effectively done.
They mentioned Vagrant. We've also had some folks mention and
contribute references to docker images. Other ideas might be
providing a live/running site where people could just immediately
start gaining familiarity with nifi.
Each of these have different pros/cons and it is unclear how to do
these in apache effective ways.
Look forward to ideas you all may have or thoughts on what other
effective approaches projects have taken.
Thanks
Joe
Re: From apache nifi (incubating) site to running nifi in fewest clicks...
Posted by Corey Flowers <cf...@onyxpoint.com>.
I would think Docker would be the way to go, or maybe variety of images
from the different opensource products, such as an image for Docker,
Virtualbox and others. We are actually going to host a live demo on our
website soon. You could link to that too, I believe we are going to use
VirtualBox to run the nifi instance.
On Wed, May 13, 2015 at 10:14 AM, Aldrin Piri <al...@gmail.com> wrote:
> Completely agree on the UI being a boon for helping people "get" NiFi.
>
> So, there are a few ways to tackle this, and perhaps this will help us
> figure out where such things belong with the project.
>
> Live demo would be awesome, but the costs of hosting, security, are
> nontrivial factors to account for. What might strike an interesting
> balance, but would be a significant undertaking, would be to create an
> emulated environment in the browser, like a lot of sites use for demos.
>
> Vagrantfiles would certainly be helpful, especially for developers in
> getting a VM up and running with properly tuned settings.
>
> We have a couple Docker images floating around. Tony made one with the
> initial release and I have started one inspired by that work that is
> available via the Docker Hub Registry [1] with source available, for the
> time being at [2] in fulfillment of NIFI-153[3].
>
> There was some discussion of how to do this the "right" way in the Apache
> process, that did not lead to any best practice. Regardless, all of these
> notions are good ones.
>
> [1] https://registry.hub.docker.com/u/aldrin/apache-nifi/
> [2] https://github.com/apiri/dockerfile-apache-nifi
> [3] https://issues.apache.org/jira/browse/NIFI-153
>
> On Wed, May 13, 2015 at 10:01 AM, Joe Witt <jo...@gmail.com> wrote:
>
> > All,
> >
> > Yesterday I had a chance to talk to a really cool startup with awesome
> > developers who gave some great feedback on nifi. One of the things
> > they mentioned was how much they loved the UI. In fact they said if
> > they hadn't seen the reference to the UI they would have said
> > 'interesting' and moved on but not really followed up.
> >
> > The point they made is we should make it as easy as possible to get
> > from landing on the apache nifi webpage to having an up and running
> > instance of NiFi for them to get to start playing with the UI.
> >
> > I'd like to put this out there to get a sense of how people see this
> > being most effectively done.
> >
> > They mentioned Vagrant. We've also had some folks mention and
> > contribute references to docker images. Other ideas might be
> > providing a live/running site where people could just immediately
> > start gaining familiarity with nifi.
> >
> > Each of these have different pros/cons and it is unclear how to do
> > these in apache effective ways.
> >
> > Look forward to ideas you all may have or thoughts on what other
> > effective approaches projects have taken.
> >
> > Thanks
> > Joe
> >
>
--
Corey Flowers
Vice President, Onyx Point, Inc
(410) 541-6699
cflowers@onyxpoint.com
-- This account not approved for unencrypted proprietary information --
Re: From apache nifi (incubating) site to running nifi in fewest clicks...
Posted by Aldrin Piri <al...@gmail.com>.
Completely agree on the UI being a boon for helping people "get" NiFi.
So, there are a few ways to tackle this, and perhaps this will help us
figure out where such things belong with the project.
Live demo would be awesome, but the costs of hosting, security, are
nontrivial factors to account for. What might strike an interesting
balance, but would be a significant undertaking, would be to create an
emulated environment in the browser, like a lot of sites use for demos.
Vagrantfiles would certainly be helpful, especially for developers in
getting a VM up and running with properly tuned settings.
We have a couple Docker images floating around. Tony made one with the
initial release and I have started one inspired by that work that is
available via the Docker Hub Registry [1] with source available, for the
time being at [2] in fulfillment of NIFI-153[3].
There was some discussion of how to do this the "right" way in the Apache
process, that did not lead to any best practice. Regardless, all of these
notions are good ones.
[1] https://registry.hub.docker.com/u/aldrin/apache-nifi/
[2] https://github.com/apiri/dockerfile-apache-nifi
[3] https://issues.apache.org/jira/browse/NIFI-153
On Wed, May 13, 2015 at 10:01 AM, Joe Witt <jo...@gmail.com> wrote:
> All,
>
> Yesterday I had a chance to talk to a really cool startup with awesome
> developers who gave some great feedback on nifi. One of the things
> they mentioned was how much they loved the UI. In fact they said if
> they hadn't seen the reference to the UI they would have said
> 'interesting' and moved on but not really followed up.
>
> The point they made is we should make it as easy as possible to get
> from landing on the apache nifi webpage to having an up and running
> instance of NiFi for them to get to start playing with the UI.
>
> I'd like to put this out there to get a sense of how people see this
> being most effectively done.
>
> They mentioned Vagrant. We've also had some folks mention and
> contribute references to docker images. Other ideas might be
> providing a live/running site where people could just immediately
> start gaining familiarity with nifi.
>
> Each of these have different pros/cons and it is unclear how to do
> these in apache effective ways.
>
> Look forward to ideas you all may have or thoughts on what other
> effective approaches projects have taken.
>
> Thanks
> Joe
>
Re: From apache nifi (incubating) site to running nifi in fewest clicks...
Posted by Sean Busbey <bu...@cloudera.com>.
docker would mean folks could deploy nifi via Amazon ECS[1], which is a
benefit IMHO.
[1]: http://docs.aws.amazon.com/AmazonECS/latest/developerguide/Welcome.html
On Wed, May 13, 2015 at 10:44 AM, Adam Taft <ad...@adamtaft.com> wrote:
> You forgot these potential steps:
>
> - download/install docker
> - download apache-nifi docker image
>
> These steps are basically analogous to:
>
> - download JDK
> - download apache-nifi tar.gz
>
> So the docker solution is only saving the configuration of nifi.properties
> step; something which should always be modified by the user anyway.
>
> Adding docker into the mix, especially if it's included as a regular output
> from the build, means yet-another-deployment-artifact to manage and
> maintain. If the community can consistently support it, and the issue of
> defaulting all nifi properties is resolved, then I'd say go for it.
>
> You're basically suggesting to trade a Docker installation/configuration
> for the JDK installation/configuration. Docker is the hotness and all, so
> maybe it's worth it for the gee-whiz perspective. But again, it doesn't
> add very much real value (for demo purposes). The Docker image would have
> to add value beyond a simple bootstrap demo, to be truly valuable.
>
> Two cents.
>
> Adam
>
>
>
>
>
> On Wed, May 13, 2015 at 10:28 AM, Aldrin Piri <al...@gmail.com>
> wrote:
>
> > Not sure I agree with your assessment. The demand is there for Docker
> > containers, even for Java apps, as evidenced by the Registry that grows
> > larger every day.
> >
> > NiFi is easy to set up, but it's certainly easier to do:
> >
> > docker run -P apache-nifi
> > http://localhost:8080/nifi
> >
> > Through a container, or equivalent, we control the totality of the user
> > experience for running. If they want to get into internals, they have
> the
> > option to, but certainly do not need to nor do they have to worry about
> > modifying their current system to support it.
> >
> > On Wed, May 13, 2015 at 10:21 AM, Adam Taft <ad...@adamtaft.com> wrote:
> >
> > > It is a Java app. So it's not like having virtualized container adds a
> > > whole lot of value. To quickly try out NiFi, currently you would:
> > >
> > > - install java (if not already)
> > > - download latest tar.gz
> > > - unzip to some user directory
> > > - modify nifi.properties
> > > - bin/nifi.sh start
> > > - http://localhost:8080/nifi
> > >
> > > With a virtualized container, you're possibly saving the step of
> > > downloading java and modifying the nifi.properties (to some default
> > > "unsecure" configuration). The rest of the steps would still be
> > performed,
> > > substituting download of the image and running it.
> > >
> > > So maybe this is simply a function of a "quick start" documentation,
> with
> > > screenshots? I'm not seeing a lot of value for using a container,
> simply
> > > for demo purposes.
> > >
> > > A live hosted demo might be interesting to consider. You would have to
> > > deal with the problem of someone using a GetFile that is looking at
> /etc,
> > > for example.
> > >
> > > Adam
> > >
> > >
> > >
> > > On Wed, May 13, 2015 at 10:01 AM, Joe Witt <jo...@gmail.com> wrote:
> > >
> > > > All,
> > > >
> > > > Yesterday I had a chance to talk to a really cool startup with
> awesome
> > > > developers who gave some great feedback on nifi. One of the things
> > > > they mentioned was how much they loved the UI. In fact they said if
> > > > they hadn't seen the reference to the UI they would have said
> > > > 'interesting' and moved on but not really followed up.
> > > >
> > > > The point they made is we should make it as easy as possible to get
> > > > from landing on the apache nifi webpage to having an up and running
> > > > instance of NiFi for them to get to start playing with the UI.
> > > >
> > > > I'd like to put this out there to get a sense of how people see this
> > > > being most effectively done.
> > > >
> > > > They mentioned Vagrant. We've also had some folks mention and
> > > > contribute references to docker images. Other ideas might be
> > > > providing a live/running site where people could just immediately
> > > > start gaining familiarity with nifi.
> > > >
> > > > Each of these have different pros/cons and it is unclear how to do
> > > > these in apache effective ways.
> > > >
> > > > Look forward to ideas you all may have or thoughts on what other
> > > > effective approaches projects have taken.
> > > >
> > > > Thanks
> > > > Joe
> > > >
> > >
> >
>
--
Sean
Re: From apache nifi (incubating) site to running nifi in fewest clicks...
Posted by Adam Taft <ad...@adamtaft.com>.
You forgot these potential steps:
- download/install docker
- download apache-nifi docker image
These steps are basically analogous to:
- download JDK
- download apache-nifi tar.gz
So the docker solution is only saving the configuration of nifi.properties
step; something which should always be modified by the user anyway.
Adding docker into the mix, especially if it's included as a regular output
from the build, means yet-another-deployment-artifact to manage and
maintain. If the community can consistently support it, and the issue of
defaulting all nifi properties is resolved, then I'd say go for it.
You're basically suggesting to trade a Docker installation/configuration
for the JDK installation/configuration. Docker is the hotness and all, so
maybe it's worth it for the gee-whiz perspective. But again, it doesn't
add very much real value (for demo purposes). The Docker image would have
to add value beyond a simple bootstrap demo, to be truly valuable.
Two cents.
Adam
On Wed, May 13, 2015 at 10:28 AM, Aldrin Piri <al...@gmail.com> wrote:
> Not sure I agree with your assessment. The demand is there for Docker
> containers, even for Java apps, as evidenced by the Registry that grows
> larger every day.
>
> NiFi is easy to set up, but it's certainly easier to do:
>
> docker run -P apache-nifi
> http://localhost:8080/nifi
>
> Through a container, or equivalent, we control the totality of the user
> experience for running. If they want to get into internals, they have the
> option to, but certainly do not need to nor do they have to worry about
> modifying their current system to support it.
>
> On Wed, May 13, 2015 at 10:21 AM, Adam Taft <ad...@adamtaft.com> wrote:
>
> > It is a Java app. So it's not like having virtualized container adds a
> > whole lot of value. To quickly try out NiFi, currently you would:
> >
> > - install java (if not already)
> > - download latest tar.gz
> > - unzip to some user directory
> > - modify nifi.properties
> > - bin/nifi.sh start
> > - http://localhost:8080/nifi
> >
> > With a virtualized container, you're possibly saving the step of
> > downloading java and modifying the nifi.properties (to some default
> > "unsecure" configuration). The rest of the steps would still be
> performed,
> > substituting download of the image and running it.
> >
> > So maybe this is simply a function of a "quick start" documentation, with
> > screenshots? I'm not seeing a lot of value for using a container, simply
> > for demo purposes.
> >
> > A live hosted demo might be interesting to consider. You would have to
> > deal with the problem of someone using a GetFile that is looking at /etc,
> > for example.
> >
> > Adam
> >
> >
> >
> > On Wed, May 13, 2015 at 10:01 AM, Joe Witt <jo...@gmail.com> wrote:
> >
> > > All,
> > >
> > > Yesterday I had a chance to talk to a really cool startup with awesome
> > > developers who gave some great feedback on nifi. One of the things
> > > they mentioned was how much they loved the UI. In fact they said if
> > > they hadn't seen the reference to the UI they would have said
> > > 'interesting' and moved on but not really followed up.
> > >
> > > The point they made is we should make it as easy as possible to get
> > > from landing on the apache nifi webpage to having an up and running
> > > instance of NiFi for them to get to start playing with the UI.
> > >
> > > I'd like to put this out there to get a sense of how people see this
> > > being most effectively done.
> > >
> > > They mentioned Vagrant. We've also had some folks mention and
> > > contribute references to docker images. Other ideas might be
> > > providing a live/running site where people could just immediately
> > > start gaining familiarity with nifi.
> > >
> > > Each of these have different pros/cons and it is unclear how to do
> > > these in apache effective ways.
> > >
> > > Look forward to ideas you all may have or thoughts on what other
> > > effective approaches projects have taken.
> > >
> > > Thanks
> > > Joe
> > >
> >
>
Re: From apache nifi (incubating) site to running nifi in fewest clicks...
Posted by Aldrin Piri <al...@gmail.com>.
Not sure I agree with your assessment. The demand is there for Docker
containers, even for Java apps, as evidenced by the Registry that grows
larger every day.
NiFi is easy to set up, but it's certainly easier to do:
docker run -P apache-nifi
http://localhost:8080/nifi
Through a container, or equivalent, we control the totality of the user
experience for running. If they want to get into internals, they have the
option to, but certainly do not need to nor do they have to worry about
modifying their current system to support it.
On Wed, May 13, 2015 at 10:21 AM, Adam Taft <ad...@adamtaft.com> wrote:
> It is a Java app. So it's not like having virtualized container adds a
> whole lot of value. To quickly try out NiFi, currently you would:
>
> - install java (if not already)
> - download latest tar.gz
> - unzip to some user directory
> - modify nifi.properties
> - bin/nifi.sh start
> - http://localhost:8080/nifi
>
> With a virtualized container, you're possibly saving the step of
> downloading java and modifying the nifi.properties (to some default
> "unsecure" configuration). The rest of the steps would still be performed,
> substituting download of the image and running it.
>
> So maybe this is simply a function of a "quick start" documentation, with
> screenshots? I'm not seeing a lot of value for using a container, simply
> for demo purposes.
>
> A live hosted demo might be interesting to consider. You would have to
> deal with the problem of someone using a GetFile that is looking at /etc,
> for example.
>
> Adam
>
>
>
> On Wed, May 13, 2015 at 10:01 AM, Joe Witt <jo...@gmail.com> wrote:
>
> > All,
> >
> > Yesterday I had a chance to talk to a really cool startup with awesome
> > developers who gave some great feedback on nifi. One of the things
> > they mentioned was how much they loved the UI. In fact they said if
> > they hadn't seen the reference to the UI they would have said
> > 'interesting' and moved on but not really followed up.
> >
> > The point they made is we should make it as easy as possible to get
> > from landing on the apache nifi webpage to having an up and running
> > instance of NiFi for them to get to start playing with the UI.
> >
> > I'd like to put this out there to get a sense of how people see this
> > being most effectively done.
> >
> > They mentioned Vagrant. We've also had some folks mention and
> > contribute references to docker images. Other ideas might be
> > providing a live/running site where people could just immediately
> > start gaining familiarity with nifi.
> >
> > Each of these have different pros/cons and it is unclear how to do
> > these in apache effective ways.
> >
> > Look forward to ideas you all may have or thoughts on what other
> > effective approaches projects have taken.
> >
> > Thanks
> > Joe
> >
>
Re: From apache nifi (incubating) site to running nifi in fewest clicks...
Posted by Adam Taft <ad...@adamtaft.com>.
It is a Java app. So it's not like having virtualized container adds a
whole lot of value. To quickly try out NiFi, currently you would:
- install java (if not already)
- download latest tar.gz
- unzip to some user directory
- modify nifi.properties
- bin/nifi.sh start
- http://localhost:8080/nifi
With a virtualized container, you're possibly saving the step of
downloading java and modifying the nifi.properties (to some default
"unsecure" configuration). The rest of the steps would still be performed,
substituting download of the image and running it.
So maybe this is simply a function of a "quick start" documentation, with
screenshots? I'm not seeing a lot of value for using a container, simply
for demo purposes.
A live hosted demo might be interesting to consider. You would have to
deal with the problem of someone using a GetFile that is looking at /etc,
for example.
Adam
On Wed, May 13, 2015 at 10:01 AM, Joe Witt <jo...@gmail.com> wrote:
> All,
>
> Yesterday I had a chance to talk to a really cool startup with awesome
> developers who gave some great feedback on nifi. One of the things
> they mentioned was how much they loved the UI. In fact they said if
> they hadn't seen the reference to the UI they would have said
> 'interesting' and moved on but not really followed up.
>
> The point they made is we should make it as easy as possible to get
> from landing on the apache nifi webpage to having an up and running
> instance of NiFi for them to get to start playing with the UI.
>
> I'd like to put this out there to get a sense of how people see this
> being most effectively done.
>
> They mentioned Vagrant. We've also had some folks mention and
> contribute references to docker images. Other ideas might be
> providing a live/running site where people could just immediately
> start gaining familiarity with nifi.
>
> Each of these have different pros/cons and it is unclear how to do
> these in apache effective ways.
>
> Look forward to ideas you all may have or thoughts on what other
> effective approaches projects have taken.
>
> Thanks
> Joe
>
Re: From apache nifi (incubating) site to running nifi in fewest clicks...
Posted by Aldrin Piri <al...@gmail.com>.
Homebrew would be great as well as package files for the major Linux
distributions (RPM, .deb)
On Wed, May 13, 2015 at 10:08 AM, Matt Gilman <ma...@gmail.com>
wrote:
> For those with OSX we could make the latest convenience binaries available
> with homebrew [1]. I needed to test something using ActiveMQ last week and
> found it available there. Two commands and I had a running instance locally
> (with default settings), but we could certainly do something similar.
>
> [1] http://brew.sh/
>
> On Wed, May 13, 2015 at 10:01 AM, Joe Witt <jo...@gmail.com> wrote:
>
> > All,
> >
> > Yesterday I had a chance to talk to a really cool startup with awesome
> > developers who gave some great feedback on nifi. One of the things
> > they mentioned was how much they loved the UI. In fact they said if
> > they hadn't seen the reference to the UI they would have said
> > 'interesting' and moved on but not really followed up.
> >
> > The point they made is we should make it as easy as possible to get
> > from landing on the apache nifi webpage to having an up and running
> > instance of NiFi for them to get to start playing with the UI.
> >
> > I'd like to put this out there to get a sense of how people see this
> > being most effectively done.
> >
> > They mentioned Vagrant. We've also had some folks mention and
> > contribute references to docker images. Other ideas might be
> > providing a live/running site where people could just immediately
> > start gaining familiarity with nifi.
> >
> > Each of these have different pros/cons and it is unclear how to do
> > these in apache effective ways.
> >
> > Look forward to ideas you all may have or thoughts on what other
> > effective approaches projects have taken.
> >
> > Thanks
> > Joe
> >
>
Re: From apache nifi (incubating) site to running nifi in fewest clicks...
Posted by Joe Witt <jo...@gmail.com>.
So do those screencasts Jenn! Nice work!
On Thu, May 14, 2015 at 4:56 AM, Jennifer Barnabee
<je...@gmail.com> wrote:
> The new web site looks awesome!!!
>
> On Wed, May 13, 2015 at 10:27 AM, Matt Gilman <ma...@gmail.com>
> wrote:
>
>> Jenn's screencasts are linked to in the updated website which should be
>> live later today!
>>
>> Matt
>>
>> On Wed, May 13, 2015 at 10:23 AM, Jennifer Barnabee <
>> jennifer.barnabee@gmail.com> wrote:
>>
>> > We have the screencasts I did [1] - in case that helps.
>> >
>> > [1]
>> > https://www.youtube.com/playlist?list=PLHre9pIBAgc4e-tiq9OIXkWJX8bVXuqlG
>> >
>> > -Jenn
>> >
>> > On Wed, May 13, 2015 at 10:17 AM, Dan Bress <db...@onyxconsults.com>
>> > wrote:
>> >
>> > > I agree, while NiFi has a lot of magic under the covers, the most
>> > > impressive thing to new people is how easy you can configure and
>> control
>> > > that magic via the UI. I think showing off this capability as soon as
>> > > possible is the best way to attract new users.
>> > >
>> > > If there was a way to have a live demo linked from the site, or even
>> just
>> > > an image/movie showing how easy it is to add processors, link them
>> > together
>> > > and quickly have a working dataflow, I think people would understand
>> the
>> > > benefits of NiFi more quickly.
>> > >
>> > > Dan Bress
>> > > Software Engineer
>> > > ONYX Consulting Services
>> > >
>> > > ________________________________________
>> > > From: Matt Gilman <ma...@gmail.com>
>> > > Sent: Wednesday, May 13, 2015 10:08 AM
>> > > To: dev@nifi.incubator.apache.org
>> > > Subject: Re: From apache nifi (incubating) site to running nifi in
>> fewest
>> > > clicks...
>> > >
>> > > For those with OSX we could make the latest convenience binaries
>> > available
>> > > with homebrew [1]. I needed to test something using ActiveMQ last week
>> > and
>> > > found it available there. Two commands and I had a running instance
>> > locally
>> > > (with default settings), but we could certainly do something similar.
>> > >
>> > > [1] http://brew.sh/
>> > >
>> > > On Wed, May 13, 2015 at 10:01 AM, Joe Witt <jo...@gmail.com> wrote:
>> > >
>> > > > All,
>> > > >
>> > > > Yesterday I had a chance to talk to a really cool startup with
>> awesome
>> > > > developers who gave some great feedback on nifi. One of the things
>> > > > they mentioned was how much they loved the UI. In fact they said if
>> > > > they hadn't seen the reference to the UI they would have said
>> > > > 'interesting' and moved on but not really followed up.
>> > > >
>> > > > The point they made is we should make it as easy as possible to get
>> > > > from landing on the apache nifi webpage to having an up and running
>> > > > instance of NiFi for them to get to start playing with the UI.
>> > > >
>> > > > I'd like to put this out there to get a sense of how people see this
>> > > > being most effectively done.
>> > > >
>> > > > They mentioned Vagrant. We've also had some folks mention and
>> > > > contribute references to docker images. Other ideas might be
>> > > > providing a live/running site where people could just immediately
>> > > > start gaining familiarity with nifi.
>> > > >
>> > > > Each of these have different pros/cons and it is unclear how to do
>> > > > these in apache effective ways.
>> > > >
>> > > > Look forward to ideas you all may have or thoughts on what other
>> > > > effective approaches projects have taken.
>> > > >
>> > > > Thanks
>> > > > Joe
>> > > >
>> > >
>> >
>>
Re: From apache nifi (incubating) site to running nifi in fewest clicks...
Posted by Jennifer Barnabee <je...@gmail.com>.
The new web site looks awesome!!!
On Wed, May 13, 2015 at 10:27 AM, Matt Gilman <ma...@gmail.com>
wrote:
> Jenn's screencasts are linked to in the updated website which should be
> live later today!
>
> Matt
>
> On Wed, May 13, 2015 at 10:23 AM, Jennifer Barnabee <
> jennifer.barnabee@gmail.com> wrote:
>
> > We have the screencasts I did [1] - in case that helps.
> >
> > [1]
> > https://www.youtube.com/playlist?list=PLHre9pIBAgc4e-tiq9OIXkWJX8bVXuqlG
> >
> > -Jenn
> >
> > On Wed, May 13, 2015 at 10:17 AM, Dan Bress <db...@onyxconsults.com>
> > wrote:
> >
> > > I agree, while NiFi has a lot of magic under the covers, the most
> > > impressive thing to new people is how easy you can configure and
> control
> > > that magic via the UI. I think showing off this capability as soon as
> > > possible is the best way to attract new users.
> > >
> > > If there was a way to have a live demo linked from the site, or even
> just
> > > an image/movie showing how easy it is to add processors, link them
> > together
> > > and quickly have a working dataflow, I think people would understand
> the
> > > benefits of NiFi more quickly.
> > >
> > > Dan Bress
> > > Software Engineer
> > > ONYX Consulting Services
> > >
> > > ________________________________________
> > > From: Matt Gilman <ma...@gmail.com>
> > > Sent: Wednesday, May 13, 2015 10:08 AM
> > > To: dev@nifi.incubator.apache.org
> > > Subject: Re: From apache nifi (incubating) site to running nifi in
> fewest
> > > clicks...
> > >
> > > For those with OSX we could make the latest convenience binaries
> > available
> > > with homebrew [1]. I needed to test something using ActiveMQ last week
> > and
> > > found it available there. Two commands and I had a running instance
> > locally
> > > (with default settings), but we could certainly do something similar.
> > >
> > > [1] http://brew.sh/
> > >
> > > On Wed, May 13, 2015 at 10:01 AM, Joe Witt <jo...@gmail.com> wrote:
> > >
> > > > All,
> > > >
> > > > Yesterday I had a chance to talk to a really cool startup with
> awesome
> > > > developers who gave some great feedback on nifi. One of the things
> > > > they mentioned was how much they loved the UI. In fact they said if
> > > > they hadn't seen the reference to the UI they would have said
> > > > 'interesting' and moved on but not really followed up.
> > > >
> > > > The point they made is we should make it as easy as possible to get
> > > > from landing on the apache nifi webpage to having an up and running
> > > > instance of NiFi for them to get to start playing with the UI.
> > > >
> > > > I'd like to put this out there to get a sense of how people see this
> > > > being most effectively done.
> > > >
> > > > They mentioned Vagrant. We've also had some folks mention and
> > > > contribute references to docker images. Other ideas might be
> > > > providing a live/running site where people could just immediately
> > > > start gaining familiarity with nifi.
> > > >
> > > > Each of these have different pros/cons and it is unclear how to do
> > > > these in apache effective ways.
> > > >
> > > > Look forward to ideas you all may have or thoughts on what other
> > > > effective approaches projects have taken.
> > > >
> > > > Thanks
> > > > Joe
> > > >
> > >
> >
>
Re: From apache nifi (incubating) site to running nifi in fewest clicks...
Posted by Matt Gilman <ma...@gmail.com>.
Jenn's screencasts are linked to in the updated website which should be
live later today!
Matt
On Wed, May 13, 2015 at 10:23 AM, Jennifer Barnabee <
jennifer.barnabee@gmail.com> wrote:
> We have the screencasts I did [1] - in case that helps.
>
> [1]
> https://www.youtube.com/playlist?list=PLHre9pIBAgc4e-tiq9OIXkWJX8bVXuqlG
>
> -Jenn
>
> On Wed, May 13, 2015 at 10:17 AM, Dan Bress <db...@onyxconsults.com>
> wrote:
>
> > I agree, while NiFi has a lot of magic under the covers, the most
> > impressive thing to new people is how easy you can configure and control
> > that magic via the UI. I think showing off this capability as soon as
> > possible is the best way to attract new users.
> >
> > If there was a way to have a live demo linked from the site, or even just
> > an image/movie showing how easy it is to add processors, link them
> together
> > and quickly have a working dataflow, I think people would understand the
> > benefits of NiFi more quickly.
> >
> > Dan Bress
> > Software Engineer
> > ONYX Consulting Services
> >
> > ________________________________________
> > From: Matt Gilman <ma...@gmail.com>
> > Sent: Wednesday, May 13, 2015 10:08 AM
> > To: dev@nifi.incubator.apache.org
> > Subject: Re: From apache nifi (incubating) site to running nifi in fewest
> > clicks...
> >
> > For those with OSX we could make the latest convenience binaries
> available
> > with homebrew [1]. I needed to test something using ActiveMQ last week
> and
> > found it available there. Two commands and I had a running instance
> locally
> > (with default settings), but we could certainly do something similar.
> >
> > [1] http://brew.sh/
> >
> > On Wed, May 13, 2015 at 10:01 AM, Joe Witt <jo...@gmail.com> wrote:
> >
> > > All,
> > >
> > > Yesterday I had a chance to talk to a really cool startup with awesome
> > > developers who gave some great feedback on nifi. One of the things
> > > they mentioned was how much they loved the UI. In fact they said if
> > > they hadn't seen the reference to the UI they would have said
> > > 'interesting' and moved on but not really followed up.
> > >
> > > The point they made is we should make it as easy as possible to get
> > > from landing on the apache nifi webpage to having an up and running
> > > instance of NiFi for them to get to start playing with the UI.
> > >
> > > I'd like to put this out there to get a sense of how people see this
> > > being most effectively done.
> > >
> > > They mentioned Vagrant. We've also had some folks mention and
> > > contribute references to docker images. Other ideas might be
> > > providing a live/running site where people could just immediately
> > > start gaining familiarity with nifi.
> > >
> > > Each of these have different pros/cons and it is unclear how to do
> > > these in apache effective ways.
> > >
> > > Look forward to ideas you all may have or thoughts on what other
> > > effective approaches projects have taken.
> > >
> > > Thanks
> > > Joe
> > >
> >
>
Re: From apache nifi (incubating) site to running nifi in fewest clicks...
Posted by Joe Witt <jo...@gmail.com>.
Well played sean. Well played.
One of our strengths is our existing security capabilities and the
inherent flexibility to connect to an organizations existing
authorization schemes. But providing a reasonably secure
demonstration system also presents a barrier to entry to consider.
Our defaults out of the box are arguably irresponsible. We can
certainly do better there.
Back on the demo track:
Perhaps we have two demo's. One that just gets you in right away but
is 'wide open'. The other is a secure mode and in that we can use
certs and can lock down via firewalls any in/out traffic we dont' want
and we could even take out processors which interact with the outside
world. We could pump in provided data (like network traffic from
tcpdump, etc...).
On Wed, May 13, 2015 at 10:41 AM, Sean Busbey <bu...@cloudera.com> wrote:
> The costs of hosting a live demo is something the ASF can help with.
>
> Having a live instance that's world accessible would certainly give us a
> strong incentive to tighten up our security posture. :)
>
> --
> Sean
> On May 13, 2015 9:29 AM, "Joe Witt" <jo...@gmail.com> wrote:
>
>> Jenn
>>
>> That does help and once the new site goes live they'll be prominent.
>>
>> All,
>>
>> This company does have a live demo up and running. I've not
>> personally tried it yet but..
>> https://www.silvercloudcomputing.com/nifi-1.html
>>
>> Already a pretty solid thread going here. This is great!
>>
>> Thanks
>> Joe
>>
>> On Wed, May 13, 2015 at 10:23 AM, Jennifer Barnabee
>> <je...@gmail.com> wrote:
>> > We have the screencasts I did [1] - in case that helps.
>> >
>> > [1]
>> https://www.youtube.com/playlist?list=PLHre9pIBAgc4e-tiq9OIXkWJX8bVXuqlG
>> >
>> > -Jenn
>> >
>> > On Wed, May 13, 2015 at 10:17 AM, Dan Bress <db...@onyxconsults.com>
>> wrote:
>> >
>> >> I agree, while NiFi has a lot of magic under the covers, the most
>> >> impressive thing to new people is how easy you can configure and control
>> >> that magic via the UI. I think showing off this capability as soon as
>> >> possible is the best way to attract new users.
>> >>
>> >> If there was a way to have a live demo linked from the site, or even
>> just
>> >> an image/movie showing how easy it is to add processors, link them
>> together
>> >> and quickly have a working dataflow, I think people would understand the
>> >> benefits of NiFi more quickly.
>> >>
>> >> Dan Bress
>> >> Software Engineer
>> >> ONYX Consulting Services
>> >>
>> >> ________________________________________
>> >> From: Matt Gilman <ma...@gmail.com>
>> >> Sent: Wednesday, May 13, 2015 10:08 AM
>> >> To: dev@nifi.incubator.apache.org
>> >> Subject: Re: From apache nifi (incubating) site to running nifi in
>> fewest
>> >> clicks...
>> >>
>> >> For those with OSX we could make the latest convenience binaries
>> available
>> >> with homebrew [1]. I needed to test something using ActiveMQ last week
>> and
>> >> found it available there. Two commands and I had a running instance
>> locally
>> >> (with default settings), but we could certainly do something similar.
>> >>
>> >> [1] http://brew.sh/
>> >>
>> >> On Wed, May 13, 2015 at 10:01 AM, Joe Witt <jo...@gmail.com> wrote:
>> >>
>> >> > All,
>> >> >
>> >> > Yesterday I had a chance to talk to a really cool startup with awesome
>> >> > developers who gave some great feedback on nifi. One of the things
>> >> > they mentioned was how much they loved the UI. In fact they said if
>> >> > they hadn't seen the reference to the UI they would have said
>> >> > 'interesting' and moved on but not really followed up.
>> >> >
>> >> > The point they made is we should make it as easy as possible to get
>> >> > from landing on the apache nifi webpage to having an up and running
>> >> > instance of NiFi for them to get to start playing with the UI.
>> >> >
>> >> > I'd like to put this out there to get a sense of how people see this
>> >> > being most effectively done.
>> >> >
>> >> > They mentioned Vagrant. We've also had some folks mention and
>> >> > contribute references to docker images. Other ideas might be
>> >> > providing a live/running site where people could just immediately
>> >> > start gaining familiarity with nifi.
>> >> >
>> >> > Each of these have different pros/cons and it is unclear how to do
>> >> > these in apache effective ways.
>> >> >
>> >> > Look forward to ideas you all may have or thoughts on what other
>> >> > effective approaches projects have taken.
>> >> >
>> >> > Thanks
>> >> > Joe
>> >> >
>> >>
>>
Re: From apache nifi (incubating) site to running nifi in fewest clicks...
Posted by Sean Busbey <bu...@cloudera.com>.
The costs of hosting a live demo is something the ASF can help with.
Having a live instance that's world accessible would certainly give us a
strong incentive to tighten up our security posture. :)
--
Sean
On May 13, 2015 9:29 AM, "Joe Witt" <jo...@gmail.com> wrote:
> Jenn
>
> That does help and once the new site goes live they'll be prominent.
>
> All,
>
> This company does have a live demo up and running. I've not
> personally tried it yet but..
> https://www.silvercloudcomputing.com/nifi-1.html
>
> Already a pretty solid thread going here. This is great!
>
> Thanks
> Joe
>
> On Wed, May 13, 2015 at 10:23 AM, Jennifer Barnabee
> <je...@gmail.com> wrote:
> > We have the screencasts I did [1] - in case that helps.
> >
> > [1]
> https://www.youtube.com/playlist?list=PLHre9pIBAgc4e-tiq9OIXkWJX8bVXuqlG
> >
> > -Jenn
> >
> > On Wed, May 13, 2015 at 10:17 AM, Dan Bress <db...@onyxconsults.com>
> wrote:
> >
> >> I agree, while NiFi has a lot of magic under the covers, the most
> >> impressive thing to new people is how easy you can configure and control
> >> that magic via the UI. I think showing off this capability as soon as
> >> possible is the best way to attract new users.
> >>
> >> If there was a way to have a live demo linked from the site, or even
> just
> >> an image/movie showing how easy it is to add processors, link them
> together
> >> and quickly have a working dataflow, I think people would understand the
> >> benefits of NiFi more quickly.
> >>
> >> Dan Bress
> >> Software Engineer
> >> ONYX Consulting Services
> >>
> >> ________________________________________
> >> From: Matt Gilman <ma...@gmail.com>
> >> Sent: Wednesday, May 13, 2015 10:08 AM
> >> To: dev@nifi.incubator.apache.org
> >> Subject: Re: From apache nifi (incubating) site to running nifi in
> fewest
> >> clicks...
> >>
> >> For those with OSX we could make the latest convenience binaries
> available
> >> with homebrew [1]. I needed to test something using ActiveMQ last week
> and
> >> found it available there. Two commands and I had a running instance
> locally
> >> (with default settings), but we could certainly do something similar.
> >>
> >> [1] http://brew.sh/
> >>
> >> On Wed, May 13, 2015 at 10:01 AM, Joe Witt <jo...@gmail.com> wrote:
> >>
> >> > All,
> >> >
> >> > Yesterday I had a chance to talk to a really cool startup with awesome
> >> > developers who gave some great feedback on nifi. One of the things
> >> > they mentioned was how much they loved the UI. In fact they said if
> >> > they hadn't seen the reference to the UI they would have said
> >> > 'interesting' and moved on but not really followed up.
> >> >
> >> > The point they made is we should make it as easy as possible to get
> >> > from landing on the apache nifi webpage to having an up and running
> >> > instance of NiFi for them to get to start playing with the UI.
> >> >
> >> > I'd like to put this out there to get a sense of how people see this
> >> > being most effectively done.
> >> >
> >> > They mentioned Vagrant. We've also had some folks mention and
> >> > contribute references to docker images. Other ideas might be
> >> > providing a live/running site where people could just immediately
> >> > start gaining familiarity with nifi.
> >> >
> >> > Each of these have different pros/cons and it is unclear how to do
> >> > these in apache effective ways.
> >> >
> >> > Look forward to ideas you all may have or thoughts on what other
> >> > effective approaches projects have taken.
> >> >
> >> > Thanks
> >> > Joe
> >> >
> >>
>
Re: From apache nifi (incubating) site to running nifi in fewest clicks...
Posted by Joe Witt <jo...@gmail.com>.
Jenn
That does help and once the new site goes live they'll be prominent.
All,
This company does have a live demo up and running. I've not
personally tried it yet but..
https://www.silvercloudcomputing.com/nifi-1.html
Already a pretty solid thread going here. This is great!
Thanks
Joe
On Wed, May 13, 2015 at 10:23 AM, Jennifer Barnabee
<je...@gmail.com> wrote:
> We have the screencasts I did [1] - in case that helps.
>
> [1] https://www.youtube.com/playlist?list=PLHre9pIBAgc4e-tiq9OIXkWJX8bVXuqlG
>
> -Jenn
>
> On Wed, May 13, 2015 at 10:17 AM, Dan Bress <db...@onyxconsults.com> wrote:
>
>> I agree, while NiFi has a lot of magic under the covers, the most
>> impressive thing to new people is how easy you can configure and control
>> that magic via the UI. I think showing off this capability as soon as
>> possible is the best way to attract new users.
>>
>> If there was a way to have a live demo linked from the site, or even just
>> an image/movie showing how easy it is to add processors, link them together
>> and quickly have a working dataflow, I think people would understand the
>> benefits of NiFi more quickly.
>>
>> Dan Bress
>> Software Engineer
>> ONYX Consulting Services
>>
>> ________________________________________
>> From: Matt Gilman <ma...@gmail.com>
>> Sent: Wednesday, May 13, 2015 10:08 AM
>> To: dev@nifi.incubator.apache.org
>> Subject: Re: From apache nifi (incubating) site to running nifi in fewest
>> clicks...
>>
>> For those with OSX we could make the latest convenience binaries available
>> with homebrew [1]. I needed to test something using ActiveMQ last week and
>> found it available there. Two commands and I had a running instance locally
>> (with default settings), but we could certainly do something similar.
>>
>> [1] http://brew.sh/
>>
>> On Wed, May 13, 2015 at 10:01 AM, Joe Witt <jo...@gmail.com> wrote:
>>
>> > All,
>> >
>> > Yesterday I had a chance to talk to a really cool startup with awesome
>> > developers who gave some great feedback on nifi. One of the things
>> > they mentioned was how much they loved the UI. In fact they said if
>> > they hadn't seen the reference to the UI they would have said
>> > 'interesting' and moved on but not really followed up.
>> >
>> > The point they made is we should make it as easy as possible to get
>> > from landing on the apache nifi webpage to having an up and running
>> > instance of NiFi for them to get to start playing with the UI.
>> >
>> > I'd like to put this out there to get a sense of how people see this
>> > being most effectively done.
>> >
>> > They mentioned Vagrant. We've also had some folks mention and
>> > contribute references to docker images. Other ideas might be
>> > providing a live/running site where people could just immediately
>> > start gaining familiarity with nifi.
>> >
>> > Each of these have different pros/cons and it is unclear how to do
>> > these in apache effective ways.
>> >
>> > Look forward to ideas you all may have or thoughts on what other
>> > effective approaches projects have taken.
>> >
>> > Thanks
>> > Joe
>> >
>>
Re: From apache nifi (incubating) site to running nifi in fewest clicks...
Posted by Jennifer Barnabee <je...@gmail.com>.
We have the screencasts I did [1] - in case that helps.
[1] https://www.youtube.com/playlist?list=PLHre9pIBAgc4e-tiq9OIXkWJX8bVXuqlG
-Jenn
On Wed, May 13, 2015 at 10:17 AM, Dan Bress <db...@onyxconsults.com> wrote:
> I agree, while NiFi has a lot of magic under the covers, the most
> impressive thing to new people is how easy you can configure and control
> that magic via the UI. I think showing off this capability as soon as
> possible is the best way to attract new users.
>
> If there was a way to have a live demo linked from the site, or even just
> an image/movie showing how easy it is to add processors, link them together
> and quickly have a working dataflow, I think people would understand the
> benefits of NiFi more quickly.
>
> Dan Bress
> Software Engineer
> ONYX Consulting Services
>
> ________________________________________
> From: Matt Gilman <ma...@gmail.com>
> Sent: Wednesday, May 13, 2015 10:08 AM
> To: dev@nifi.incubator.apache.org
> Subject: Re: From apache nifi (incubating) site to running nifi in fewest
> clicks...
>
> For those with OSX we could make the latest convenience binaries available
> with homebrew [1]. I needed to test something using ActiveMQ last week and
> found it available there. Two commands and I had a running instance locally
> (with default settings), but we could certainly do something similar.
>
> [1] http://brew.sh/
>
> On Wed, May 13, 2015 at 10:01 AM, Joe Witt <jo...@gmail.com> wrote:
>
> > All,
> >
> > Yesterday I had a chance to talk to a really cool startup with awesome
> > developers who gave some great feedback on nifi. One of the things
> > they mentioned was how much they loved the UI. In fact they said if
> > they hadn't seen the reference to the UI they would have said
> > 'interesting' and moved on but not really followed up.
> >
> > The point they made is we should make it as easy as possible to get
> > from landing on the apache nifi webpage to having an up and running
> > instance of NiFi for them to get to start playing with the UI.
> >
> > I'd like to put this out there to get a sense of how people see this
> > being most effectively done.
> >
> > They mentioned Vagrant. We've also had some folks mention and
> > contribute references to docker images. Other ideas might be
> > providing a live/running site where people could just immediately
> > start gaining familiarity with nifi.
> >
> > Each of these have different pros/cons and it is unclear how to do
> > these in apache effective ways.
> >
> > Look forward to ideas you all may have or thoughts on what other
> > effective approaches projects have taken.
> >
> > Thanks
> > Joe
> >
>
Re: From apache nifi (incubating) site to running nifi in fewest
clicks...
Posted by Dan Bress <db...@onyxconsults.com>.
I agree, while NiFi has a lot of magic under the covers, the most impressive thing to new people is how easy you can configure and control that magic via the UI. I think showing off this capability as soon as possible is the best way to attract new users.
If there was a way to have a live demo linked from the site, or even just an image/movie showing how easy it is to add processors, link them together and quickly have a working dataflow, I think people would understand the benefits of NiFi more quickly.
Dan Bress
Software Engineer
ONYX Consulting Services
________________________________________
From: Matt Gilman <ma...@gmail.com>
Sent: Wednesday, May 13, 2015 10:08 AM
To: dev@nifi.incubator.apache.org
Subject: Re: From apache nifi (incubating) site to running nifi in fewest clicks...
For those with OSX we could make the latest convenience binaries available
with homebrew [1]. I needed to test something using ActiveMQ last week and
found it available there. Two commands and I had a running instance locally
(with default settings), but we could certainly do something similar.
[1] http://brew.sh/
On Wed, May 13, 2015 at 10:01 AM, Joe Witt <jo...@gmail.com> wrote:
> All,
>
> Yesterday I had a chance to talk to a really cool startup with awesome
> developers who gave some great feedback on nifi. One of the things
> they mentioned was how much they loved the UI. In fact they said if
> they hadn't seen the reference to the UI they would have said
> 'interesting' and moved on but not really followed up.
>
> The point they made is we should make it as easy as possible to get
> from landing on the apache nifi webpage to having an up and running
> instance of NiFi for them to get to start playing with the UI.
>
> I'd like to put this out there to get a sense of how people see this
> being most effectively done.
>
> They mentioned Vagrant. We've also had some folks mention and
> contribute references to docker images. Other ideas might be
> providing a live/running site where people could just immediately
> start gaining familiarity with nifi.
>
> Each of these have different pros/cons and it is unclear how to do
> these in apache effective ways.
>
> Look forward to ideas you all may have or thoughts on what other
> effective approaches projects have taken.
>
> Thanks
> Joe
>
Re: From apache nifi (incubating) site to running nifi in fewest clicks...
Posted by Matt Gilman <ma...@gmail.com>.
For those with OSX we could make the latest convenience binaries available
with homebrew [1]. I needed to test something using ActiveMQ last week and
found it available there. Two commands and I had a running instance locally
(with default settings), but we could certainly do something similar.
[1] http://brew.sh/
On Wed, May 13, 2015 at 10:01 AM, Joe Witt <jo...@gmail.com> wrote:
> All,
>
> Yesterday I had a chance to talk to a really cool startup with awesome
> developers who gave some great feedback on nifi. One of the things
> they mentioned was how much they loved the UI. In fact they said if
> they hadn't seen the reference to the UI they would have said
> 'interesting' and moved on but not really followed up.
>
> The point they made is we should make it as easy as possible to get
> from landing on the apache nifi webpage to having an up and running
> instance of NiFi for them to get to start playing with the UI.
>
> I'd like to put this out there to get a sense of how people see this
> being most effectively done.
>
> They mentioned Vagrant. We've also had some folks mention and
> contribute references to docker images. Other ideas might be
> providing a live/running site where people could just immediately
> start gaining familiarity with nifi.
>
> Each of these have different pros/cons and it is unclear how to do
> these in apache effective ways.
>
> Look forward to ideas you all may have or thoughts on what other
> effective approaches projects have taken.
>
> Thanks
> Joe
>
Re: From apache nifi (incubating) site to running nifi in fewest clicks...
Posted by es...@gmail.com.
Lots and lots of folks are using docker these days. Existing Amazon AMI's would be cool too. Actually, I think docker files our projects or whatever you call them run in Amazon now as well.
A
Sent from my iPhone
> On May 13, 2015, at 7:01 AM, Joe Witt <jo...@gmail.com> wrote:
>
> All,
>
> Yesterday I had a chance to talk to a really cool startup with awesome
> developers who gave some great feedback on nifi. One of the things
> they mentioned was how much they loved the UI. In fact they said if
> they hadn't seen the reference to the UI they would have said
> 'interesting' and moved on but not really followed up.
>
> The point they made is we should make it as easy as possible to get
> from landing on the apache nifi webpage to having an up and running
> instance of NiFi for them to get to start playing with the UI.
>
> I'd like to put this out there to get a sense of how people see this
> being most effectively done.
>
> They mentioned Vagrant. We've also had some folks mention and
> contribute references to docker images. Other ideas might be
> providing a live/running site where people could just immediately
> start gaining familiarity with nifi.
>
> Each of these have different pros/cons and it is unclear how to do
> these in apache effective ways.
>
> Look forward to ideas you all may have or thoughts on what other
> effective approaches projects have taken.
>
> Thanks
> Joe