THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Note that this logs you in as user "vagrant". Once you are logged in, you can run:
$ sudo su -
to make yourself root. Ambari offers many installation options (see ), but to get up and running quickly with default settings, you can run the following:
| Code Block |
|---|
# yum install |
...
# yum install ambari-server -y |
...
# ambari-server setup -s |
...
# ambari-server start |
Once Ambari Server is started, hit http://c6401.ambari.apache.org:8080
(URL depends on the OS being tested) on from your browser from on your local computer. Ambari Web should come up.
Note that Ambari Server can take some time to fully come up and ready to accept connections. Keep hitting the URL until you get the login page.
Once you are at the login page, login with the default username admin and password admin.
On the Install Options page, use the FQDNs of the VMs. For example:
| Code Block |
|---|
c6401.ambari.apache.org
c6402.ambari.apache.org
c6403.ambari.apache.org
|
Alternatively, you can use a range expression:
| Code Block |
|---|
c64[01-03].ambari.apache.org
|
Specify the Note: To test SSH install of Ambari Agent, use the non-root SSH user vagrant, and upload insecure_private_key file that you copied earlier when prompted in the Install Wizardas the private key.
Follow the onscreen instructions to install your cluster.
When done testing, run "vagrant destroy -f" to purge the VMs.
Basic VM Operations
$ vagrant up <vm name>
Starts a specific VM. up.sh is a wrapper for this call.
Note: if you don’t specify the <vm name> parameter, it will try to start 10 VMs
You can run this if you want to start more VMs after you already called up.sh
For example: vagrant up c6406
...
$ vagrant status
Shows which VMs are running, suspended, etc.
...
Modifying RAM for the VMs
Each VM is allocated 2GB of RAM. These can be chaged changed by editing Vagrantfile. To change the RAM allocation, modify the following line:
| Code Block |
|---|
vb.customize ["modifyvm", :id, "--memory", 2048] |
Misc
All VMs launched will have a directory called /vagrant inside the VM. This maps to the ambari-vagrant/<os> directory on your local computer. You can use this shared directory mapping to push files, etc.
If you want to test OS’s other than what’s currently in the ambari-vagrant repo, please see http://www.vagrantbox.es/ for all the readily available OS images you can test. Note that Ambari currently works on RHEL 5/6, CentOS 5/6, Oracle Linux 5/6, SUSE 11, and SLES 11. Ubuntu support is work in progress.