Child pages
  • Quick Start Guide

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Updated examples to use Centos 6.8.


You will see subdirectories for different OS’s. “cd” into the OS that you want to test. centos6.48 is recommended as this is quicker to launch than other OS's.
Now you can start VMs with the following command:

Code Block
cd centos6.48
cp ~/.vagrant.d/insecure_private_key .
./ <# of VMs to launch>

For example, 3 starts 3 VMs. 3 seems to be a good number with 16GB of RAM without taxing the system too much.
With the default Vagrantfile, you can specify up to 10 (if your computer can handle it; you can even add more).
VMs will have the FQDN <os-code>[01-10], where <os-code> is c59 (CentOS 5.9), c64 c68 (CentOS 6.48), etc.
E.g.,,, etc.
VMs will have the IP address 192.168.<os-subnet>.1[01-10], where <os-subnet> is 59 for CentOS 5.9, 64 68 for CentOS 6.48, etc.
E.g.,,, etc.
Note that 3 command is equivalent to doing something like: vagrant up c640c680{1..3}

Testing Ambari

If it is your first time running a vagrant command, run:


Log into the VM:

Code Block
vagrant ssh c6401c6801

Note that this logs you in as user vagrant. Once you are logged in, you can run:


Once Ambari Server is started, hit (URL depends on the OS being tested) from your browser on your local computer.
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

Alternatively, you can use a range expression:

Code Block


vagrant up <vm name>
Starts a specific VM. 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
For example: vagrant up c6406c6806

vagrant destroy -f
Destroys all VMs launched from the current directory (deletes them from disk as well)
You can optionally specify a specific VM to destroy


vagrant ssh host
Starts a SSH session to the host. For example: vagrant ssh c6401c6801

vagrant status
Shows which VMs are running, suspended, etc.


This enables the “vagrant snapshot” command. Note that the above installs vesion 0.0.2. if you install the latest plugin version 0.0.3 does not allow taking snapshots of the whole cluster at the same time (you have to specify a VM name).
Run vagrant snapshot to see the syntax.
Note that the plugin tries to take a snapshot of all VMs configured in Vagrantfile. If you are always using 3 VMs, for example, you can comment out c64c68[04-10] in Vagrantfile so that the snapshot commands only operate on c64c68[01-03].
Note: Upon resuming a snapshot, you may find that time-sensitive services may be down (e.g, HBase RegionServer is down, etc.)


Update /etc/krb5.conf on the KDC host. e.g. if your realm is EXAMPLE.COM and kdc host is

Code Block
    admin_server =
    kdc =

Restart Kerberos services. e.g. for Centos/RedHat


Code Block
cd ambari-vagrant/centos6.48
vi Vagrantfile  <- uncomment the line with ""
vagrant up c6401c6801

To build from source, follow the instructions in Ambari Development.


Code Block
cd ambari-vagrant/centos6.48
git clone ambari
cd ambari/ambari-web
npm install
brunch w

On c6401 c6801 (where Ambari Server is installed):