Github user mmiklavc commented on the issue:
https://github.com/apache/metron/pull/1261
@ottobackwards - yeah, that's probably reasonable. The base HDP image
create option would be an additional improvement to existing functionality.
---
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/1261
The base option is like quick dev, but quick dev also had metron installed,
so starting it involved replacing the bits that where in there, we didn't
maintain quick dev ansible w/o the metron
Github user mmiklavc commented on the issue:
https://github.com/apache/metron/pull/1261
@ottobackwards I like @justinleet's suggestion on having a base option. I'd
imagine what we could have is a mechanism that allows you to build an image
with just HDP of a specific version, and
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/1261
I think spellcheck is integrated into travis, so what we _can_ do is make
shellcheck a build dependency and execute it through maven in the poms
---
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/1261
@mmiklavc I have it integrated into IntelliJ, though it isn't as obvious as
java errors
---
Github user JonZeolla commented on the issue:
https://github.com/apache/metron/pull/1261
@mmiklavc probably at some point. I assume it would require some cleanup
for various scripts at the same time.
---
Github user mmiklavc commented on the issue:
https://github.com/apache/metron/pull/1261
@JonZeolla - would it make sense to add ShellCheck to Travis? Seems like a
lot of potentially useful detail here.
---
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/1261
@nickwallen Done
---
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/1261
@nickwallen, yeah, I did prompts as I went along debugging. I was
thinking that folks may not like them.
I'll parameterize things.
---
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/1261
hey @ottobackwards - I am still wrapping my head around this, but one small
nit is that I don't like all the confirmation prompts. With the prompts I have
to constantly check back to ensure it
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/1261
If you create an issue for your vagrant base machine with our hadoop /
ambari already in it, you can assign it to me. @justinleet
---
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/1261
It is possible to imagine a number of scenarios, including that, but also
needing to build with new hadoop versions ( can't loose build from scratch ).
There are a number of things we
Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/1261
In the interest of pure (and almost certainly incredibly ignorant)
speculation, along the lines of the vagrant cloud, is it theoretically possible
to save off a base image that has the Hadoop
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/1261
anyone have any ideas of the best way to time these things?
---
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/1261
We could also use more tags, for example I may want to skip building the
java, but not skip building the RPMs. Think of a dev flow -> I make my change,
run my local tests and want to spin up
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/1261
@nickwallen That is an option, but not something I would pick as the goal
from the outset if you know what I mean.
---
Github user JonZeolla commented on the issue:
https://github.com/apache/metron/pull/1261
I'm going to take a stab at a further look next week. For now I gave it a
quick run-up and it was successful.
---
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/1261
If we go this approach, why not just replace the existing "Full Dev"
environments (both centos and ubuntu) rather than add new environments to
support, test, and keep in-sync?
---
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/1261
@mmiklavc That is basically correct. Except that the ansible version is
2.5, since it only applies to this build, and allows for the yaml log
formatting.
Also, in the latest
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/1261
@nickwallen I did not think of that. I was improving the process that
stands today. I think in a world where the posted image exists, we would still
want the ability to try the latest ( to
Github user mmiklavc commented on the issue:
https://github.com/apache/metron/pull/1261
@ottobackwards thanks for the submission. Per recent community comments, it
sounds like we could use some improvements to how our build/deploy dep versions
interact with other tooling that may
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/1261
Valiant effort @ottobackwards . I am just wondering how much easier this
really makes it?
Have you thought about just publishing a Metron Demo image to Vagrant
Cloud? Does that
22 matches
Mail list logo
