Wow, I didn't realize that never got finalized/merged.  Looks like there is
a failure in travis on that PR, if you get that wrapped up I would think we
should take another look at that and maybe get it merged.  It has been a
while but I recall I was pretty happy with it after my review cycle with
you.

- Jon Zeolla
zeo...@gmail.com


On Wed, Apr 10, 2019 at 9:17 AM Otto Fowler <ottobackwa...@gmail.com> wrote:

> These issues are the reason https://github.com/apache/metron/pull/1261 was
> done.  It would be nice if we could get by them.
>
>
> On April 10, 2019 at 08:13:04, Dale Richardson (tigerqu...@outlook.com)
> wrote:
>
> Older pre-req versions are mentioned at:
>
>
> https://metron.apache.org/current-book/metron-deployment/vagrant/codelab-platform/index.html
> Metron – Developer Image for Apache Metron on Virtualbox<
>
> https://metron.apache.org/current-book/metron-deployment/vagrant/codelab-platform/index.html
> >
>
> Developer Image for Apache Metron on Virtualbox. This image is a fully
> functional Metron installation that has been pre-loaded with Ambari, HDP
> and Metron.
> metron.apache.org
>
>
> https://metron.apache.org/current-book/metron-deployment/vagrant/full-dev-platform/index.html
> Metron – Full Development Platform<
>
> https://metron.apache.org/current-book/metron-deployment/vagrant/full-dev-platform/index.html
> >
>
> Full Development Platform. This project fully automates the provisioning
> and deployment of Apache Metron and all necessary prerequisites on a
> single, virtualized host running on Virtualbox.
> metron.apache.org
>
>
>
> https://metron.apache.org/current-book/metron-deployment/vagrant/quick-dev-platform/index.html
> Metron – Quick Development Platform<
>
> https://metron.apache.org/current-book/metron-deployment/vagrant/quick-dev-platform/index.html
> >
>
> Quick Development Platform. This project fully automates the provisioning
> and deployment of Apache Metron and all necessary prerequisites on a
> single, virtualized host running on Virtualbox.
> metron.apache.org
>
>
>
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=68718548
>
> Metron Install on Ubuntu/Debian single-node VM with Vagrant and Ambari -
> Metron - Apache Software Foundation - cwiki.apache.org<
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=68718548>
> Contributed by Umesh Kaushik < umesh.kaus...@bhujang.net > Introduction.
> These instructions are for an Ubuntu host, with occasional comments about
> how to do similar tasks in CentOS.
> cwiki.apache.org
>
> Which links to
> https://gist.github.com/dpalomar/96b826dac5c2e8b62cbf4c86dbd1c9df
>
>
>
> ________________________________
> From: Michael Miklavcic <michael.miklav...@gmail.com>
> Sent: Wednesday, 10 April 2019 4:15 AM
> To: dev@metron.apache.org
> Subject: Re: Problems with Dev deployment.
>
> Where are you seeing 2.0.0.2 for Ansible? Should be 2.4.0+ now.
>
> https://github.com/apache/metron/blob/master/metron-deployment/development/centos6/README.md
>
>
>
> On Tue, Apr 9, 2019, 6:59 PM Michael Miklavcic <
> michael.miklav...@gmail.com>
>
> wrote:
>
> > That would be awesome man! Yes, Jira tickets for every change. I don't
> > recall off the top of my head the version - I'll have to look when I get
> > back in front of a computer.
> >
> > On Tue, Apr 9, 2019, 6:56 PM Dale Richardson <tigerqu...@outlook.com>
> > wrote:
> >
> >> Hi Michael,
> >> Yep that was the issue, looks like "brew install ansible" configures
> >> ansible for python 3. Happy to patch the documentation with updated
> >> install instructions (I will add the MacOS Mojave Drive permission issue
> >> as well). Do you know if the minimum ansible version requirement has
> >> changed at all? (some documentation lists it as 2.0.0.2 or 2.2.2.0). Do
> >> you guys usually put in a Jira to cover small documentation changes at
> all?
> >>
> >> Regards,
> >> Dale.
> >> ________________________________
> >> From: Otto Fowler <ottobackwa...@gmail.com>
> >> Sent: Sunday, 7 April 2019 1:40 PM
> >> To: dev@metron.apache.org
> >> Subject: Re: Problems with Dev deployment.
> >>
> >> Can you pull down
> >>
>
> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fmetron%2Fpull%2F1261&amp;data=02%7C01%7C%7Cc00c98c5300d45adf8c508d6bbab3180%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636902741276312736&amp;sdata=oylL4njlCkTYaLsyLYl44Zy8%2BoZoB4HVBCb5F2vgxng%3D&amp;reserved=0
> >> and try?
> >> That should eliminate any env. issues.
> >>
> >> I’ll update it to latest master now.
> >>
> >>
> >>
> >> On April 7, 2019 at 08:33:52, Dale Richardson (tigerqu...@outlook.com)
> >> wrote:
> >>
> >> Hi Folks,
> >> I've been walking through some of the documentations on building and
> >> deploying the Metron development image.
> >> I am building Metron version 0.7. The deployment appears to go OK up
> until
> >> the Ambari deployment stage, and then I get the following error:
> >>
> >>
> >> SyntaxError: invalid syntax
> >>
> >> INFO interface: detail: The full traceback is:
> >>
> >> Traceback (most recent call last):
> >>
> >> File
> >>
> >>
>
> "/usr/local/Cellar/ansible/2.7.9/libexec/lib/python3.7/site-packages/ansible/executor/task_executor.py",
>
> >> line 140, in run
> >>
> >> res = self._execute()
> >>
> >> File
> >>
> >>
>
> "/usr/local/Cellar/ansible/2.7.9/libexec/lib/python3.7/site-packages/ansible/executor/task_executor.py",
>
> >> line 612, in _execute
> >>
> >> result = self._handler.run(task_vars=variables)
> >>
> >> File
> >>
> >>
>
> "/usr/local/Cellar/ansible/2.7.9/libexec/lib/python3.7/site-packages/ansible/plugins/action/normal.py",
>
> >> line 46, in run
> >>
> >> result = merge_hash(result, self._execute_module(task_vars=task_vars,
> >> wrap_async=wrap_async))
> >>
> >> File
> >>
> >>
>
> "/usr/local/Cellar/ansible/2.7.9/libexec/lib/python3.7/site-packages/ansible/plugins/action/__init__.py",
>
> >> line 742, in _execute_module
> >>
> >> (module_style, shebang, module_data, module_path) =
> >> self._configure_module(module_name=module_name, module_args=module_args,
> >> task_vars=task_vars)
> >>
> >> File
> >>
> >>
>
> "/usr/local/Cellar/ansible/2.7.9/libexec/lib/python3.7/site-packages/ansible/plugins/action/__init__.py",
>
> >> line 178, in _configure_module
> >>
> >> environment=final_environment)
> >>
> >> File
> >>
> >>
>
> "/usr/local/Cellar/ansible/2.7.9/libexec/lib/python3.7/site-packages/ansible/executor/module_common.py",
>
> >> line 973, in modify_module
> >>
> >> environment=environment)
> >>
> >> File
> >>
> >>
>
> "/usr/local/Cellar/ansible/2.7.9/libexec/lib/python3.7/site-packages/ansible/executor/module_common.py",
>
> >> line 791, in _find_module_utils
> >>
> >> recursive_finder(module_name, b_module_data, py_module_names,
> >> py_module_cache, zf)
> >>
> >> File
> >>
> >>
>
> "/usr/local/Cellar/ansible/2.7.9/libexec/lib/python3.7/site-packages/ansible/executor/module_common.py",
>
> >> line 538, in recursive_finder
> >>
> >> tree = ast.parse(data)
> >>
> >> File
> >>
> >>
>
> "/usr/local/opt/python/Frameworks/Python.framework/Versions/3.7/lib/python3.7/ast.py",
>
> >> line 35, in parse
> >>
> >> return compile(source, filename, mode, PyCF_ONLY_AST)
> >>
> >> File "<unknown>", line 230
> >>
> >> except requests.ConnectionError, e:
> >>
> >> ^
> >>
> >> MacOS Mojava (Version 10.14.3)
> >> VirtualBox version 5.2.26
> >> Vagrant version 2.2.4
> >>
> >> ansible 2.7.9
> >> config file =
> >>
> /Users/user/work/metron/metron-deployment/development/centos6/ansible.cfg
> >> ansible python module location =
> >>
> >>
> /usr/local/Cellar/ansible/2.7.9/libexec/lib/python3.7/site-packages/ansible
> >> executable location = /usr/local/bin/ansible
> >> python version = 3.7.2 (default, Feb 12 2019, 08:15:36) [Clang 10.0.0
> >> (clang-1000.11.45.5)]
> >>
> >>
> >>
> >> Python2 version is 2.7.16
> >>
> >> commit 2263983761e77b7eec52f70f5e8f8001bac83125 (HEAD, tag:
> >> apache-metron_0.7.0-release, tag: apache-metron-0.7.0-rc1,
> >> origin/Metron_0.7.0)
> >>
> >> Does anybody have any suggestions on how to proceed?
> >>
> >> Thanks,
> >> Dale.
> >>
> >
>

Reply via email to