The Azure cloud infrastructure has become a common place for users to deploy virtual machines on the cloud due to its flexibility, ease of deployment, and cost benefits. Microsoft has expanded Azure to include a marketplace with thousands of certified, open source, and community software applications and developer services, pre-configured for Microsoft Azure. This tutorial covers deploying the Hortonworks Sandbox offering via the Azure Marketplace.
Go to Microsoft Azure Marketplace and enter “Hortonworks” into the search bar. Submit, and the Hortonworks Sandbox product should appear as shown in this screenshot.
Select the Hortonworks Sandbox product and its Overview will display. Click on Get It Now to start the setup process.
If prompted, sign in to Azure Marketplace. Afterward, you’ll be asked to confirm your selection, as shown below.
An explanation of the Hortonworks Sandbox will come on the screen. When ready to begin the deployment process, select Create from the bottom of the screen.
Fill out some basic sandbox configuration settings. Scroll down for an explanation of the different fields.
The different fields:
Note: Make sure to write down or remember your username and password. If using SSH, ensure you have the corresponding private key. Otherwise, you will not be able to log in to the machine.
The next step is to choose a size for the virtual machine. It is recommended to use a machine with A4 specifications, or higher.
Optional settings to configure. You can safely leave these at their defaults.
Look over the summary and continue when ready.
Alright, we’re ready to deploy! Review the offer details and purchase when ready.
Once the offer is submitted by selecting Purchase, the sandbox will take a few minutes to set up and deploy. After deployment is complete, we can move on to connecting to the sandbox.
Once the machine is deployed, it’s overview will appear on the screen. Find the sandbox’s public IP address and click on it.
Clicking on the IP address will bring up the IP configuration panel. Select Static as the Assignment, and then make sure to save your changes. This will keep the sandbox from changing IP addresses each time it’s rebooted.
SSH tunneling allows us a way to port forward securely, without actually opening the machine’s ports for the entire world to access. Follow these steps to access the endpoints of your Azure deployment from your computer.
Use your favorite editor and edit your
~/.ssh/config file. For example:
Enter the following configuration, replacing the HostName IP with the public IP of your instance. More forwardings can be entered via the LocalForward directive similar to the ones displayed here.
Note: Spacing and capitalization is important.
Host azureSandbox Port 22 User azure HostName 188.8.131.52 LocalForward 8080 127.0.0.1:8080 LocalForward 8888 127.0.0.1:8888 LocalForward 9995 127.0.0.1:9995 LocalForward 9996 127.0.0.1:9996 LocalForward 8886 127.0.0.1:8886 LocalForward 10500 127.0.0.1:10500 LocalForward 4200 127.0.0.1:4200 LocalForward 2222 127.0.0.1:2222
Save and close the file. Now SSH into the Azure machine by using the Host alias we just configured, which will connect us automatically using the IP address we specified in the config file. You’ll be asked for a password, which is the one you set during initial configuration on Azure.
That’s it! Keep this SSH connection open for the duration of your interaction with the sandbox on Azure.
Now that you’ve port forwarded by following the tutorial linked above, you can explore the sandbox as you see fit. Point your browser to http://localhost:8888 for the sandbox’s splash screen.
Fill out the form and hit Submit to access the sandbox.
SSH tunneling allows us a way to port forward securely, without actually opening the machine’s ports for the entire world to access.
Now that you’ve got HDP up and running, check out our other tutorials to learn how to leverage its power.