Metron Person Types...

[John <jo...@cephal.com>]

Hello Dev@Metron,

The other day Ryan mentioned that it might be nice to combine the build
step (run mvn) before deploying (ex. vagrant up), so people have one less
step to type/forget. And he mentioned there might be a jira out there for
maybe optionally combining the steps (I'm thinking it's METRON-78). Well, I
noticed the run.sh for amazon-ec2 already performs the mvn step before
deploying, but yeah, for the vagrant options we do have to run separate
commands today. Looks like there are some options for vagrant to run mvn on
the host (ex. triggers) or even for mvn to exec vagrant up... but it would
be neat to have reuse between this solution and the existing amazon-ec2
scripts (which does not use vagrant)... and I can off-line this convo to
the ticket, but this topic got me curious to the type of people that might
want to build and/or run Metron. Like, if someone just wanted to quickly
try out Metron I see on the github homepage they can just download the
binaries and not need mvn/git... but I'm guessing they still need vagrant
and/or ansible today. I tried to throw together a quick list of some of the
person types I could think of off the top of my head, but I'd love to get
some of your guys thoughts on the subject too...

*Quick Start Person: **"I just want a working copy of Metron so I can play
with it."*
1. Download & Run Metron (i.e. pre-built metron binary/vm/container, so no
mvn/git needed and maybe no vagrant/ansible someday).

*Real Metron:* *"I want to deploy Metron for real this time -- like
multi-node in the Cloud."*
2. Configure & Run Ansible Playbook (w/ pre-built metron, so no
mvn/git/vagrant needed).

*Developer: **"I want to help develop Metron."*
3. Fork/Clone Repo, Open in IDE, Edit Code, Run, Commit, PR, Close Ticket.
 (vagrant/ansible for running services single/multi-node locally/remotely).


Thanks,
John Stone

Re: Metron Person Types...

[John <jo...@cephal.com>]

This is great stuff! And I'll offline the Ansible+Maven convo to the ticket
and see if I can get something working here. Thanks David!

On Mon, May 9, 2016 at 2:21 PM, David Lyle <dl...@gmail.com> wrote:

> Hi John,
>
> METRON-78 was originally conceived as a ticket to add the Maven build step
> to the Ansible scripts. I think that makes the most sense as they're run in
> the case of EC2 or Vagrant or Production Deployment. I'd happily help get
> this one closed out. It gets me about once per week.
>
> You're right, I don't actually see a way to try out Metron currently
> without having the build tools (at the very least, Maven, Ansible, and
> Vagrant) locally. That said, I do agree about the use cases/user roles you
> described and I think we have a basic (but could be improved) set of images
> that handle them.
>
> Quick Start Person -> metron-deployment/vagrant/codelab-platform (Could get
> away with only Ansible and Vagrant if you pulled the code from
> https://github.com/apache/incubator-metron/releases/tag/codelab-v1.0)
> Real Metron -> Modified version of
> metron-deployment/inventory/metron_example
> Developer (Metron Platform) -> metron-deployment/quick-dev-platform
> Developer (Metron Deployment) -> metron-deployment/full-def-platform
>
> I'm not sure I have answered your question, but the above descrbes my
> thinking on the different images.
>
> Thanks!
>
> -D...
>
>
>
>
> On Sat, May 7, 2016 at 7:58 PM, John <jo...@cephal.com> wrote:
>
> > Hello Dev@Metron,
> >
> > The other day Ryan mentioned that it might be nice to combine the build
> > step (run mvn) before deploying (ex. vagrant up), so people have one less
> > step to type/forget. And he mentioned there might be a jira out there for
> > maybe optionally combining the steps (I'm thinking it's METRON-78).
> Well, I
> > noticed the run.sh for amazon-ec2 already performs the mvn step before
> > deploying, but yeah, for the vagrant options we do have to run separate
> > commands today. Looks like there are some options for vagrant to run mvn
> on
> > the host (ex. triggers) or even for mvn to exec vagrant up... but it
> would
> > be neat to have reuse between this solution and the existing amazon-ec2
> > scripts (which does not use vagrant)... and I can off-line this convo to
> > the ticket, but this topic got me curious to the type of people that
> might
> > want to build and/or run Metron. Like, if someone just wanted to quickly
> > try out Metron I see on the github homepage they can just download the
> > binaries and not need mvn/git... but I'm guessing they still need vagrant
> > and/or ansible today. I tried to throw together a quick list of some of
> the
> > person types I could think of off the top of my head, but I'd love to get
> > some of your guys thoughts on the subject too...
> >
> > *Quick Start Person: **"I just want a working copy of Metron so I can
> play
> > with it."*
> > 1. Download & Run Metron (i.e. pre-built metron binary/vm/container, so
> no
> > mvn/git needed and maybe no vagrant/ansible someday).
> >
> > *Real Metron:* *"I want to deploy Metron for real this time -- like
> > multi-node in the Cloud."*
> > 2. Configure & Run Ansible Playbook (w/ pre-built metron, so no
> > mvn/git/vagrant needed).
> >
> > *Developer: **"I want to help develop Metron."*
> > 3. Fork/Clone Repo, Open in IDE, Edit Code, Run, Commit, PR, Close
> Ticket.
> >  (vagrant/ansible for running services single/multi-node
> locally/remotely).
> >
> >
> > Thanks,
> > John Stone
> >
>

Re: Metron Person Types...

[David Lyle <dl...@gmail.com>]

Hi John,

METRON-78 was originally conceived as a ticket to add the Maven build step
to the Ansible scripts. I think that makes the most sense as they're run in
the case of EC2 or Vagrant or Production Deployment. I'd happily help get
this one closed out. It gets me about once per week.

You're right, I don't actually see a way to try out Metron currently
without having the build tools (at the very least, Maven, Ansible, and
Vagrant) locally. That said, I do agree about the use cases/user roles you
described and I think we have a basic (but could be improved) set of images
that handle them.

Quick Start Person -> metron-deployment/vagrant/codelab-platform (Could get
away with only Ansible and Vagrant if you pulled the code from
https://github.com/apache/incubator-metron/releases/tag/codelab-v1.0)
Real Metron -> Modified version of
metron-deployment/inventory/metron_example
Developer (Metron Platform) -> metron-deployment/quick-dev-platform
Developer (Metron Deployment) -> metron-deployment/full-def-platform

I'm not sure I have answered your question, but the above descrbes my
thinking on the different images.

Thanks!

-D...




On Sat, May 7, 2016 at 7:58 PM, John <jo...@cephal.com> wrote:

> Hello Dev@Metron,
>
> The other day Ryan mentioned that it might be nice to combine the build
> step (run mvn) before deploying (ex. vagrant up), so people have one less
> step to type/forget. And he mentioned there might be a jira out there for
> maybe optionally combining the steps (I'm thinking it's METRON-78). Well, I
> noticed the run.sh for amazon-ec2 already performs the mvn step before
> deploying, but yeah, for the vagrant options we do have to run separate
> commands today. Looks like there are some options for vagrant to run mvn on
> the host (ex. triggers) or even for mvn to exec vagrant up... but it would
> be neat to have reuse between this solution and the existing amazon-ec2
> scripts (which does not use vagrant)... and I can off-line this convo to
> the ticket, but this topic got me curious to the type of people that might
> want to build and/or run Metron. Like, if someone just wanted to quickly
> try out Metron I see on the github homepage they can just download the
> binaries and not need mvn/git... but I'm guessing they still need vagrant
> and/or ansible today. I tried to throw together a quick list of some of the
> person types I could think of off the top of my head, but I'd love to get
> some of your guys thoughts on the subject too...
>
> *Quick Start Person: **"I just want a working copy of Metron so I can play
> with it."*
> 1. Download & Run Metron (i.e. pre-built metron binary/vm/container, so no
> mvn/git needed and maybe no vagrant/ansible someday).
>
> *Real Metron:* *"I want to deploy Metron for real this time -- like
> multi-node in the Cloud."*
> 2. Configure & Run Ansible Playbook (w/ pre-built metron, so no
> mvn/git/vagrant needed).
>
> *Developer: **"I want to help develop Metron."*
> 3. Fork/Clone Repo, Open in IDE, Edit Code, Run, Commit, PR, Close Ticket.
>  (vagrant/ansible for running services single/multi-node locally/remotely).
>
>
> Thanks,
> John Stone
>