THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
$ ./up.sh <# of VMs to launch>
For example, ./up.sh 3 starts 3 VMs. 3 seems to be a good number with 16GB of RAM.
You can specify up to 10 (if your computer can handle it!)
VMs will have the FQDN <os-code>01-10.ambari.apache.org, where <os-code> is c59 (CentOS 5.9), c64 (CentOS 6.4), etc.
E.g., c5901.ambari.apache.org, c6401.ambari.apache.org, etc.
VMs will have the IP address 192.168.<os-subnet>.101-10, where <os-subnet> is 59 for CentOS 5.9, 64 for CentOS 6.4, etc.
E.g., 192.168.59.101, 192.168.64.101, etc.
Modifying RAM for the VMs
Each VM is allocated 2GB of RAM. These can be chaged by editing Vagrantfile. To change the RAM allocation, modify the following line:
vb.customize id, "--memory", 2048
Testing Ambari
Logg into <os-code>01 (e.g., c6401).
$ vagrant ssh c6401
...
$ vagrant status
Shows which VMs are running, suspended, etc.
Advanced
Modifying RAM for the VMs
Each VM is allocated 2GB of RAM. These can be chaged by editing Vagrantfile. To change the RAM allocation, modify the following line:
vb.customize id, "--memory", 2048
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.
...