Quantcast
Channel: Hortonworks » All Replies
Viewing all articles
Browse latest Browse all 3435

Reply To: Sharing Sandbox

$
0
0

Francis:

The Hortonworks Sandbox is freely available to all. We encourage you to share the Sandbox with your colleagues.

If you’re using VirtualBox, you can export the state of your Sandbox and share the resulting files with your colleagues. They can import them on their own workstations and use them locally. After shutting down your Sandbox, go to File > Export and follow the prompts. Your colleagues can use the File > Import dialogs to import your copy of the Sandbox onto their workstations.

If you’re asking if it’s possible for your colleagues to access the copy of the Sandbox running on your workstation, that’s a bit more tricky, but it is possible. When we ship the Sandbox, it’s configured to use a type of network that is visible only to your workstation. It’s possible to change the network configuration of your VM and make the various service ports visible to your colleagues. This is fairly advanced, and will require some changes in how you and your team follow the tutorials or make use of the Sandbox.

I’m assuming in this response that you are using VirtualBox, and that your network supports DHCP, and that your local security policies do not require any special software to be running on servers like the Sandbox.

First, shutdown the Sandbox. It’s always good to have your VM shutdown when making significant changes to its settings in VirtualBox. Right click on the Sandbox in the main window, and select “Settings”. Go to Network. You will note the Network Type is “NAT”. Change this to “Bridged” and save your results.

After making this change, your VM will startup and act as if it is on the same network as your workstation. Thus, it will request it’s own DHCP address. After making this change, you’ll need to find out what IP has been assigned to the VM; you can do that by logging in on the VirtualBox console (user: root, password: hadoop), and running this command

# ifconfig eth0

Note the IP address. This may change every time you start the Sandbox, so you may have to perform this step and the IP every time you restart the Sandbox.

All the services must now be accessed using this IP address (e.g. 192.168.0.101), instead of “localhost” as the tutorials indicate. Thus, the Hue interface is accessed via http://192.168.0.101:8000/, the Oozie console is at http://192.168.0.101:11000/oozie/, and so forth.

Further, to login remotely to your Sandbox, instead of “ssh -p 2222 root@localhost“, you must now use “ssh root@192.168.0.101“. Note the change in the ssh port number from 2222; it’s no longer necesary to use a special port number, and from “localhost” to “192.168.0.101”.

Hopefully, this will get you and your team started and working with the many features of the Hortonworks Sandbox.

Best regards,

Bryce Ryan


Viewing all articles
Browse latest Browse all 3435

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>