- Import the virtual machine into VMware or VirtualBox
Power on the virtual machine. The completed boot-up screen looks like the following example which includes the IP address:
NOTE: Your IP address will be different from the above screenshot. However, please capture this IP address as it will be needed in subsequent steps.
Once the VM is started, log into the VM or SSH from the host machine using a terminal utility such as Putty on Windows or the Terminal App on macOS.
VMware: ssh root@[IP_ADDRESS]
VirtualBox: ssh root@localhost –p 2222
VirtualBox uses localhost instead of IP address as all the ports have been setup to forward:
NOTE: Please do not change the port numbers pre-configured in the VirtualBox OVA.
- Once started, login to the VM or SSH from your host machine using below credential:
deployscript to download, install, and configure the environment. There are different options for deploying the Quick Start environment. Choose the desired option:
Components included in deployment:
- The deployment details will be available via the deploy.log
tail –f /var/log/deploy.log
A successful deployment will result in a response with text similar to example below:
If you see "DEMO DEPLOYMENT FAILED" error, please review deploy.log. The OVA will need to be imported again and re-run the deploy CLI.
Type below CLI to check the environment status:
You can access the following urls and ports using Chrome to access the BlueTalon management components and Zeppelin to execute queries against the different data platforms:
NOTE: For VMware, please use IP address you received when you first powered on the VM. For VirtualBox, please use "localhost" in the browser.
- BlueTalon Policy Configuration User Interface: localhost:8111 or IP:8111
- BlueTalon Audit User Interface: localhost:8112 or IP:8112
- CDH: localhost:8080 or IP:8080
- HDP: localhost:9090 or IP:9090 (since 8080 is taken by Ambari)
IMPORTANT: DO NOT power off the VM by selecting Shut Down (VMware) or Power Off (VirtualBox) menu. This may result in corrupted VM. It's always the best practice to take snapshot and pause or suspend the VM.