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 starting point if you’re looking for an environment to test extensions or contributions to the platform, though I would make sure you give it plenty of RAM (16GB is a good starting point for the VM I find, so you may need to adjust the Vagrantfile). In a ‘real’ environment, the best way to install is through the Mpack method on an existing Ambari install. I would not recommend using ansible at all. It is extremely sensitive to ansible version number and very brittle as a result because ansible apis keep changing from build to build. Simon > On 22 Nov 2017, at 12:21, Pawel Bialasiewicz <pa...@evengx.com> wrote: > > 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 of Ubuntu 16 LTS. > And it still crashes with the output that I included in the Issue 1327. > > Pawel > > > > On Wed, Nov 22, 2017 at 1:11 PM, zeo...@gmail.com <zeo...@gmail.com > <mailto:zeo...@gmail.com>> wrote: > 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? Also, you have noted that this affects > version 0.4.0, but the latest release is 0.4.1, is that accurate? Have you > retried the `vagrant up` after your npm upgrade and a npm` cache clean`? > > Jon > > On Wed, Nov 22, 2017 at 7:01 AM Pawel Bialasiewicz <pa...@evengx.com > <mailto:pa...@evengx.com>> wrote: > 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 maybe I should use a more specific > branch(other then master)? > > Can somebody confirm that it is currently possible to build metron-config? It > fails for me in every deployment. > > Any help would be appreciated. > -- > Jon > >
