Re: Not able to run metron.

2017-11-22 Thread Simon Elliston Ball
Just FYI, that’s a little outdated, Ubuntu builds are now included in the hortonworks distribution, but if you want to build from source the advice there very much applies. > On 22 Nov 2017, at 13:19, Otto Fowler wrote: > > Btw: If you have ubuntu clusters, have you seen : > https://communi

Re: Not able to run metron.

2017-11-22 Thread Otto Fowler
Btw: If you have ubuntu clusters, have you seen : https://community.hortonworks.com/articles/88843/manually-installing-apache-metron-on-ubuntu-1404.html On November 22, 2017 at 08:17:41, Otto Fowler (ottobackwa...@gmail.com) wrote: I build on mac, and have : -- node v6.10.2 -- npm 3.10.10 for

Re: Not able to run metron.

2017-11-22 Thread Otto Fowler
I build on mac, and have : -- node v6.10.2 -- npm 3.10.10 for my node versions. On November 22, 2017 at 08:05:02, Simon Elliston Ball ( si...@simonellistonball.com) wrote: Sorry, you’re right, you do need ansible. Make sure the version is EXACTLY the version in the docs. Simon On 22 Nov 2017

Re: Not able to run metron.

2017-11-22 Thread Simon Elliston Ball
Sorry, you’re right, you do need ansible. Make sure the version is EXACTLY the version in the docs. Simon > On 22 Nov 2017, at 13:03, Otto Fowler wrote: > > You DO need ansible for full_dev deployment. > You do need Docker installed and running > > > > On November 22, 2017 at 07:51:47, Paw

Re: Not able to run metron.

2017-11-22 Thread Otto Fowler
You DO need ansible for full_dev deployment. You do need Docker installed and running On November 22, 2017 at 07:51:47, Pawel Bialasiewicz (pa...@evengx.com) wrote: Here is the output: platform-info.sh Metron 0.4.2 -- * master -- commit 8022f2c8c4e9018a15a4f04d0a66f8bc0ea653c3 Author: merriman

Re: Not able to run metron.

2017-11-22 Thread Pawel Bialasiewicz
Here is the output: platform-info.sh Metron 0.4.2 -- * master -- commit 8022f2c8c4e9018a15a4f04d0a66f8bc0ea653c3 Author: merrimanr Date: Tue Nov 21 13:46:35 2017 -0600 METRON-1319 Column Metadata REST service should use default indices on empty input (merrimanr) closes apache/metron#843 --

Re: Not able to run metron.

2017-11-22 Thread zeo...@gmail.com
You will need docker to be installed. In theory this should work across any *nix distro, but the instructions provided are most thoroughly tested on macOS endpoints so I always like to clarify. I know in the past I had some bumps with spinning it up on CentOS just due to lack of testing. Can you

Re: Not able to run metron.

2017-11-22 Thread Simon Elliston Ball
You shouldn’t need ansible for the full-dev build, but you will need maven, docker and an up-to-date nodejs and npm package to do the actual build. I would recommend against using the OS provided nodejs and go with the packages from nodesource instead. The full-dev build is also the best start

Re: Not able to run metron.

2017-11-22 Thread Pawel Bialasiewicz
Thank you for the answer Zeolla! As for now lets focus on the vagrant spin up. Correct me if I'm wrong: the vagrant full-dev install should work on any linux distro that has: Vagrant, Virtualbox, Ansible, git, Maven, vagrant-hostmanager. I'm have all of those things installed on a fresh install

Re: Not able to run metron.

2017-11-22 Thread zeo...@gmail.com
Sorry - I didn't answer one of your questions. Yes, I am able to build metron-config and full-dev is working fine for me from master. Jon On Wed, Nov 22, 2017 at 7:11 AM zeo...@gmail.com wrote: > It looks like you have two issues - one related to having java_home unset, > and one with an old v

Re: Not able to run metron.

2017-11-22 Thread zeo...@gmail.com
It looks like you have two issues - one related to having java_home unset, and one with an old version of npm. I would suggest focusing on the Vagrant spin-up, as it is the easiest to get running. Are you running this on a CentOS 6 machine, or are you referring to the full-dev VM's CentOS 6 OS?

Not able to run metron.

2017-11-22 Thread Pawel Bialasiewicz
Hi, I have been trying to run Metron in many ways and all of the deployment methods failed: 1) Bare metal –-> [Issue 1320] 2) AWS –-> [Issue 1318] 3) Vagrant –-> [Issue 1327] So currently I'm out of options. All the deployments methods failed. Is the all of documentation outdated, or mayb