metron-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "" <>
Subject Re: Metron Installation on an Ambari-Managed Cluster?
Date Sat, 25 Mar 2017 11:13:56 GMT
Just to add onto this, that is a feature I have similarly been looking for
but my environment hasn't matured enough yet for me to push the topic.

I've been installing various versions of master in my hardware environment
using Ansible, but ever since the Ambari mpack I have been doing it more

On a similar note, I think we can help to reduce outdated documentation
like this by moving it to GitHub, which is on my to do list.


On Sat, Mar 25, 2017, 1:34 AM Otto Fowler <> wrote:

> I am looking for a fully scriptable solution, where I don’t have to go into
> ambari, such as running the ansible playbook.
> Before I would run build and playbook from docker.
> On March 24, 2017 at 19:34:12, Matt Foley ( wrote:
> is much more recent. It should still work, but I’m not sure how RPM
> generation has changed, especially after David’s changes in METRON-671
> (Refactor Ansible deployment to use Ambari). Of course the two scenarios
> are different (your link is about installing Metron AFTER fully installing
> HDP, while this link is about installing it all together), but they use
> essentially the same steps.
> The above linked article does have a lot of cruft based on working around
> previously-existing bugs that have now been fixed, so if something looks
> like it’s already been done, or doesn’t make sense, it may be okay to
> ignore.
> The one thing both articles do that just isn’t necessary, is make you
> install/run Docker and do the RPM build on the cluster. I routinely do the
> Docker-based RPM build on my Mac, and move only the RPMs to the install
> directory used by the Metron MPack for Ambari (/localrepo/) on the Metron
> nodes.
> So if the Docker RPM build is the main impediment, try doing that.
> --Matt
> On 3/24/17, 2:03 PM, "Otto Fowler" <> wrote:
> I have used
> as
> a guide in the past, but it is out of date,
> I don’t think it can possibly work with docker rpm build now.
> Does anyone have any ideas what it would take to get this workflow working
> again?


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message