Github user justinleet commented on the issue:
https://github.com/apache/incubator-metron/pull/436
I'm +1. I was just waiting for the EC2 component, but was able to get
quick-dev, etc. spun up without issue.
---
If your project is set up for it, you can reply to this email and have
Github user ottobackwards commented on the issue:
https://github.com/apache/incubator-metron/pull/436
I am +1. I have been working downstream and building off of this for a
bit, and been able to get quick and full up with everything started. I have
some things that I would like to
Github user nickwallen commented on the issue:
https://github.com/apache/incubator-metron/pull/436
That's great, @mmiklavc. I am also a +1. I was able to test this
successfully on Quick Dev and Full Dev.
---
If your project is set up for it, you can reply to this email and have
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/436
Thanks for all the help! I intend to merge this in tomorrow afternoon.
@ottobackwards, @justinleet, I wanted to make sure you two were good. I also
want to make sure there's no other
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/436
Thanks @mmiklavc!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and
Github user mmiklavc commented on the issue:
https://github.com/apache/incubator-metron/pull/436
Looks like everything came up correctly for me in AWS. So +1 to that part
of it.
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/436
@mmiklavc - Exactly. We were wanting to make sure that @nickwallen was
having environmental issues.
---
If your project is set up for it, you can reply to this email and have your
Github user mmiklavc commented on the issue:
https://github.com/apache/incubator-metron/pull/436
@dlyle65535 is the test for EC2 to just verify everything spins up as
normal? Any additional specific items to test or smoke test?
---
If your project is set up for it, you can reply to
Github user mmiklavc commented on the issue:
https://github.com/apache/incubator-metron/pull/436
@dlyle65535 fyi I'm deploying to ec2 right now. I'll update shortly.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/436
@justinleet - Accepted. Thanks.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user justinleet commented on the issue:
https://github.com/apache/incubator-metron/pull/436
@dlyle65535 METRON-745 is in (as I'm sure you can tell from the conflict
list). I already incorporated the Kibana map changes, so you should just be
able to accept master's version.
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/436
@justinleet - that last commit adds the quotation requiremnt to the tool
tip.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/436
@nickwallen - I pushed up a changeset that will address both your points.
For 1, I added a test to ambari-setup to fail if FATAL appears in stdout.
Making sure the EC2 build doesn't run
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/436
Good news, I think I found the issue with the failing tests. The Maven
reported "duplicated" dependencies weren't. I've replaced them. Travis will
tell.
@nickwallen - I did see
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/436
@nickwallen - For your first issue, I think we're hitting a transient issue
with Ambari where ambari-setup -s completes successfully but Ambari won't
actually start. I'll see if I can
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/436
@nickwallen - I had run EC2 testing a bunch and it worked post at least as
well as it did prior (sometimes AWS zigs when it should zag). But, I have made
a quite few changes since my
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/436
Travis failure. Upsetting. This came in with my latest Master merge. Don't
fail locally with Travis command line. Log below. It's in unrelated code. Any
ideas?
>
Github user nickwallen commented on the issue:
https://github.com/apache/incubator-metron/pull/436
I have been able to launch "Quick Dev" with deployment report. Thanks for
the fix @dlyle65535
I have been fighting a bit with the AWS deployment. I ran into two issues.
Github user ottobackwards commented on the issue:
https://github.com/apache/incubator-metron/pull/436
I'm fine with that. Just being up front on the change is enough from now.
Troubleshooting this may be a big user issue generator
---
If your project is set up for it, you can
Github user ottobackwards commented on the issue:
https://github.com/apache/incubator-metron/pull/436
you point on blueprints reminds me that this kind of obsoletes the
'deploying metron on an ambari managed cluster' wiki page, and that page is
very valuable
---
If your project is
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/436
@ottobackwards - thanks for that! Let's do make sure the end result is
something you can use. Also remember that this is steps 1 and 2 of an at least
4 step improvement, so perhaps once
Github user ottobackwards commented on the issue:
https://github.com/apache/incubator-metron/pull/436
No, I don't have a problem with the ansible decision. And I don't even
mean for this feedback to hold up this PR. I just think it is harder to
troubleshoot and work with it since
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/436
@nickwallen - last commit fixed deployment report for Quick Dev. Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/436
@ottobackwards - I don't agree that automation breaks with this. It is
different though. If you're building automation now, you'd probably want to
leverage Ambari Blueprints.
Github user ottobackwards commented on the issue:
https://github.com/apache/incubator-metron/pull/436
If someone is doing what the old workflow is ( just from the command line -
not opening ambari until everything is done ) they will never see anything but
the fail, please fix and
Github user justinleet commented on the issue:
https://github.com/apache/incubator-metron/pull/436
@dlyle65535 @ottobackwards Can we link the various Ambari logs so they're
visible on the local machine? Anything that blows up in the UI should blow up
in the logs, which means
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/436
That's good feedback @ottobackwards. Post build errors will now surface in
Ambari. I don't know what to do about the build. Any errors would eventually
pop up on your screen. Is there
Github user ottobackwards commented on the issue:
https://github.com/apache/incubator-metron/pull/436
I can offer a slightly different perspective on this PR, from the pov of
someone working downstream ( i rebased on it ), and who has been working on
adding things to the spec and
Github user justinleet commented on the issue:
https://github.com/apache/incubator-metron/pull/436
@dlyle65535 Perfect, thanks. I'm going to go ahead and just make that
change and test in 745. If this goes in first, 745 just takes its dashboard
changes entirely. In the less likely
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/436
@nickwallen - glad of that, I did see that I was still using a stale
inventory for quick-dev which worked, but without the report. I've got a fix
for that in test now.
---
If your
Github user nickwallen commented on the issue:
https://github.com/apache/incubator-metron/pull/436
I was able to start over on "Quick Dev" and get it running. Maybe I wasn't
patient enough on the first run.
It still did not show the deployment report, so I'm not sure if it
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/436
There's a checkbox in the widget config:
That needs to be checked
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/436
Chill guys, I'm trying to get a screenshot. ;)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user nickwallen commented on the issue:
https://github.com/apache/incubator-metron/pull/436
> but I don't know what made the map not work to fix it?
Technically, we had two versions of the dashboard. Maybe the "legacy"
dashboard deployed via Ansible using elasticdump
Github user justinleet commented on the issue:
https://github.com/apache/incubator-metron/pull/436
@dlyle65535 @nickwallen I'm not sure what the exact fix was with the
dashboard. Either approach to fixing will work for me, but I don't know what
made the map not work to fix it?
---
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/436
@nickwallen - it did need to change. The map didn't work. It does now. If
@justinleet finds it easier to duplicate that change in his work, he can do so,
otherwise, he should build on
Github user nickwallen commented on the issue:
https://github.com/apache/incubator-metron/pull/436
> @justinleet - wrt the Dashboard changes, the map shows up. If you've
saved off a bunch of changes, you may want to clobber mine, but make sure the
map shows up when you're done.
Github user nickwallen commented on the issue:
https://github.com/apache/incubator-metron/pull/436
Something bad happened when I tried to run "Quick Dev" with the latest
code.
* I ran a `vagrant up` and the command completed successfully.
* But no "deployment report" was
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/436
@justinleet - wrt the Dashboard changes, the map shows up. If you've saved
off a bunch of changes, you may want to clobber mine, but make sure the map
shows up when you're done.
---
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/436
Resolved the merge conflicts from Master and addressed review comments.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/436
I'm working on those merge conflicts right now.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/436
@JonZeolla - makes sense, I've pushed that change.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user JonZeolla commented on the issue:
https://github.com/apache/incubator-metron/pull/436
Not a showstopper for me, but maybe worth a mention in `Upgrading.md` that
CentOS 6 shouldn't be used any longer. Note that `Upgrading.md` gets a bit of
a modification in METRON-752
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/436
From @JonZeolla - "Looks like Docker is a dependency now which rules out
CentOS 6 if we strictly follow the docker documentation. Was that expected or
would you assume people would opt
Github user ottobackwards commented on the issue:
https://github.com/apache/incubator-metron/pull/436
@dlyle65535 can you point to any documentation for the ambari api/functions
that we are using?
---
If your project is set up for it, you can reply to this email and have your
reply
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/436
@ottobackwards - sure, I used
[this](https://cwiki.apache.org/confluence/display/AMBARI/API+usage+scenarios%2C+troubleshooting%2C+and+other+FAQs)
as a guide.
---
If your project is
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/436
This is ready for review. Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/436
@ottobackwards - that's correct. At that time the new boxes hadn't been
prepped. Sorry for the confusion, I had left that box uncheck in an effort to
communicate that. It should be good
Github user ottobackwards commented on the issue:
https://github.com/apache/incubator-metron/pull/436
David, after fetch and merge of your latest I can no longer vagrant up
full_dev
==> node1: Adding box 'new_base' (v0) for provider: virtualbox
node1: Downloading:
Github user ottobackwards commented on the issue:
https://github.com/apache/incubator-metron/pull/436
Well, if we don't want to put deployment things with the src, then ansible
is a more flexible and easier to use tool for certain tasks too. But we will
talk about it when I get it
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/436
No. It's not meant for that. If you want to build standalone, Maven is the
supported way.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user ottobackwards commented on the issue:
https://github.com/apache/incubator-metron/pull/436
Maybe we should add that line to the doc or create a script??
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user ottobackwards commented on the issue:
https://github.com/apache/incubator-metron/pull/436
ansible-playbook -v -i "localhost," -c local playbooks/metron_build.yml
now it is running and i'll see about the errors
---
If your project is set up for it, you can reply
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/436
Yeah, that seems like a good thing to try.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user ottobackwards commented on the issue:
https://github.com/apache/incubator-metron/pull/436
Do I have to create an inventory with my local machine name?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user ottobackwards commented on the issue:
https://github.com/apache/incubator-metron/pull/436
ansible-playbook -v playbooks/metron_build.yml
Using
/Users/ottofowler/src/apache/forks/incubator-metron/metron-deployment/ansible.cfg
as config file
[WARNING]:
Github user ottobackwards commented on the issue:
https://github.com/apache/incubator-metron/pull/436
I need to run the playbook though.
It doesn't match any hosts
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/436
Sure. It's vagrant up or ./run.sh. :) I run it as part of running full dev
or ec2.
What error are you getting?
Btw, to only build the rpms, you may can still do an
Github user ottobackwards commented on the issue:
https://github.com/apache/incubator-metron/pull/436
can you share your command line? Do you run it from /playbooks? does you
-i an inventory? Did you copy or create an ansible.cfg?
---
If your project is set up for it, you can
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/436
Yes, that works on my rig. Can you tell me a bit more about what you're
experiencing?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user ottobackwards commented on the issue:
https://github.com/apache/incubator-metron/pull/436
I want to run the playbook to just build the rpm's, not deploy. So just
metron_build
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/436
I am, for both full dev and ec2. What are you trying to do?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user ottobackwards commented on the issue:
https://github.com/apache/incubator-metron/pull/436
How are you running the playbook? I cannot get it to execute
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
63 matches
Mail list logo
