@Sunile Manjee, sure. My approach is more of a workaround than a solution, but I'll do my best to describe it here.
I followed these steps while the VM was still running with Ambari and HDP deployed (the point at which the error occurred).
Make a backup copy of the Vagrantfile in incubator-metron-Metron_0.1BETA_rc7/deployment/vagrant/singlenode-vagrant/
Edit Vagrantfile so that ansible uses the metron_install.yml file instead of the metron_full_install.yml file:
Near the end of the file, change the line with ansible.playbook = "../../playbooks/metron_full_install.yml"
to
ansible.playbook = "../../playbooks/metron_install.yml"
Then save your changes.
From the deployment/vagrant/singlenode-vagrant directory, issue the following command:
vagrant provision
(If the VM is stopped/halted you'd probably want to use vagrant up instead. It shouldn't hurt to run vagrant up; if it isn't needed it will let you know.)
At this point the Metron installation playbook stepped through nine blocks of instructions; looks they're called "plays". You can see the list in the metron_install.yml file, and you can look in the roles directory for a better understanding of the tasks associated with the role in each play (hadoop_setup, mysql-server, etc.).
When the provisioning finished I could see all four topologies in the Storm UI but I didn't see any data. I'd gotten an error during the hadoop_setup role (under hosts: hadoop_client) so I re-ran that part by making a backup copy of metron_install.yml, removing everything except the hadoop_client section from the original file, and running vagrant provision again. A little while later I started seeing data in the Metron UI -- great to see it!
I hope I've remembered everything; let me know if any of it isn't clear.
... View more
