This Quick Start guide is for readers who are new to the use of virtual machines, Apache Ambari, and/or the Apache Hadoop component stack, who would like to install and use a small local Hadoop cluster. The instructions are for a local host machine running OS X.

The following instructions cover Here is an overview of the four main steps for installing Ambari and HDP using VirtualBox and Vagrant:

1. Install VirtualBox and Vagrant. (Installation only needs to be done once unless you want to upgrade VirtualBox and/or Vagrant.)
2. Install and start one or more Linux virtual machines. Each machine represents Start one or more VMs, each representing a node in a cluster.
3. DownloadOn one of the virtual machines, download, install, and deploy the version of Ambari you wish to use.
4. From Using Ambari, deploy the version of HDP you wish to use. 

When you complete the example in this Quick Start, you should have a three-node cluster of virtual machines running Ambari 2.4.1.0 and HDP 2.5.0 (unless you specify different repository versions).

Once VirtualBox and Vagrant are installed, steps 2 through Once VirtualBox and Vagrant have been installed, steps 2 through 4 can be done multiple times ( to change versions, create a larger cluster, etc.)and so on. There is no need to repeat step 1 unless you want to upgrade VirtualBox and/or Vagrant later.

Note: these steps have been were most recently tested on MacOS 10.9.5.

Install VirtualBox and Vagrant

VirtualBox allows you to run multiple operating systems (inside multiple virtual machines) at the same time. Your Mac is the "host" machine, and the virtual machines are called "guest" machines.

In this Quick Start you will use VirtualBox to run Linux nodes within VirtualBox on OS X:   consider iterating the image

Image Removed

Vagrant is a tool that makes it easier to work with virtual machines. It helps automate the work of setting up, running, and removing virtual machine environments. Using Vagrant, you can install and run a preconfigured cluster environment with Ambari and the HDP stack.

...

Clone the ambari-vagrant GitHub repository into a convenient folder on your Mac. From the command-line:

git clone https://github.com/u39kun/ambari-vagrant.git

11.6, El Capitan.

Terminology

A virtual machine, or VM, is a software program that exhibits the behavior of a separate computer and is capable of running applications and programs within its own environment.

A virtual machine is often called a guest, because it runs within another computing environment--usually known as the host. For example, if you install three Linux VMs on a Mac, the Mac is the host machine; the three Linux VMs are guests.

Multiple virtual machines can exist within a single host at one time. In the following examples, one or more virtual machines run on a host machine running OS X. OS X is the primary operating system. The virtual machines (guests) are installed under OS X. The virtual machines run Linux in separate environments on OS X. Thus, your Mac is the "host" machine, and the virtual machines that run Ambari and Hadoop are called "guest" machines.

Prerequisites

You will need the following resources for this Quick Start:

• A solid internet connection, preferably with at least 5 MB available download bandwidth.
• If you are installing the VMs on a Mac, at least 16 GB of memory (assuming 3 GB per VM)

Install VirtualBox and Vagrant

VirtualBox is a software virtualization package that installs on an operating system as an application. It allows you to run multiple virtual machines at the same time. In this Quick Start you will use VirtualBox to run Linux nodes within VirtualBox on OS X:

Image Added

Vagrant is a tool that makes it easier to work with virtual machines. It helps automate the work of setting up, running, and removing virtual machine environments. Using Vagrant, you can install and run a preconfigured cluster environment with Ambari and the HDP stack.

1. Download and install VirtualBox from https://www.virtualbox.org/wiki/Downloads. This Quick Start has been tested on version 5.1.6.
   
   
2. Download and install Vagrant from https://www.vagrantup.com/downloads.html.
   

3. Clone the ambari-vagrant GitHub repository into a convenient folder on your Mac. Navigate to the folder, and enter the following command from the terminal:

   Code Block
   git clone https://github.com/u39kun/ambari-vagrant.git

   The repository contains scripts for setting up Ambari virtual machines on several Linux distributions.
   
   

4. Add virtual machine hostnames and addresses to the /etc/hosts file on your computer. The following command copies a set of host names and addresses from ambari-vagrant/append-to-etc-hosts.txt to the end of the /etc/hosts files:

   Code Block
   sudo -s 'cat ambari-vagrant/append-to-etc-hosts.txt >> /etc/hosts'

5. Use the vagrant command to create a private key to use with Ambari:

   Code Block
   vagrant

   The vagrant command displays Vagrant command information, and then it creates a private key in the file ~/.vagrant.d/insecure_private_key.
   

Start Linux Virtual Machines

The ambari-vagrant directory (cloned from GitHub) contains several subdirectories, each for a specific Linux distribution. Each subdirectory has scripts and configuration files for running Ambari and HDP on that version of Linux.

To start one or more virtual machines:

1.  Change your current directory to ambari-vagrant:

   Code Block
   cd ambari-vagrant

   If you run an ls command on the ambari-vagrant directory, you will see subdirectories for several different operating systems and operating system versions.
   
   

2. cd into the OS subdirectory for the OS you wish to use. CentOS is recommended, because it is quicker to launch than other operating systems.
   
   The remainder of this example uses CentOS 7.0 . (To install and use a different version or distribution of Linux, specify the other directory name in place of centos7.0.)

   Code Block
   cd centos7.0

   Important: All VM vagrant commands operate within your current directory. Be sure to run them from the local (Mac) subdirectory associated with the VM operating system that you have chosen to use. If you attempt to run a vagrant command from another directory, it will not find the VM.
   
   

   Copy the private key into the directory associated with the chosen operating system.
   For this example, which uses centos7.0 , issue the following command:

   Code Block
   cp ~/.vagrant.d/insecure_private_key .

3. (Optional) If you have at least 16 GB of memory on your Mac, consider increasing the amount of memory allocated to the VMs.
   Edit the following line in Vagrantfile , increasing allocated memory from 3072 to 4096 or more; for example:

   Code Block
   vb.customize ["modifyvm", :id, "--memory", 4096] # RAM allocated to each VM

4. Every virtual machine will have a directory called /vagrant inside the VM. This corresponds to the ambari-vagrant/<os> directory on your local computer, making it easy to transfer files back and forth between your host Mac and the virtual machine. If you have any files to access from within the VM, you can place them in this shared directory.
   
   

5. Start one or more VMs, using the ./up.sh command. Each VM will run one HDP node. Recommendation: if you have at least 16GB of RAM on your Mac and wish to run a small cluster, start with three nodes.

   Code Block
   ./up.sh <# of VMs to launch>

   For example, the following command starts 3 VMs:
   ./up.sh 3
   
   On an early 2013 MacBook Pro, 2.7 GHz core i7 and 16 GB RAM, this step takes five minutes. For CentOS 7.0, the hostnames are c7001, c7002, and c7003.
   
   Additional notes:
   - If you ran the VMs before and used vagrant destroy to remove the VM's, this is the step at which you would recreate and start the VMs.
   - The default Vagrantfile (in each OS subdirectory) can create up to 10 virtual machines.
   - The up.sh 3 command is equivalent to vagrant up c700{1..3}.
   - The fully-qualified domain name (FQDN) for each VM has the format <os-code>[01-10].ambari.apache.org, where <os-code> is c59 (CentOS 5.9), c64 (CentOS 6.4), etc. For example, c5901.ambari.apache.org will be the FQDN for node 01 running CentOS 5.9.
   - The IP address for each VM has the format 192.168.<os-subnet>.1[01-10], where <os-subnet> is 64 for CentOS 6.4, 70 for CentOS 7.0, and so on. For example, 192.168.70.101 will be the IP address for CentOS 7.0 node c7001.
   
   

6. Check the status of your VM(s), and review any errors. The following example shows the results of ./upsh 3 for three VMs running with CentOS 7.0:

   Code Block
   LMBP:centos7.0 lkg$ vagrant status Current machine states: c7001 running (virtualbox) c7002 running (virtualbox) c7003 running (virtualbox) c7004 not created (virtualbox) c7005 not created (virtualbox) c7006 not created (virtualbox) c7007 not created (virtualbox) c7008 not created (virtualbox) c7009 not created (virtualbox) c7010 not created (virtualbox)

   In the preceding list, three virtual machines are installed and running.
   
   

7. At this point, you can snapshot the VMs to have a fresh set of running machines to reuse if desired. This is especially helpful when installing Apache Ambari and the HDP stack for the first time; it allows you to back out to fresh VMs and reinstall Ambari and HDP if you encounter errors. For more information about snapshots, see the vagrant snapshot command in "Basic Vagrant Commands," later in this Quick Start. 

Access Virtual Machines

Use the following steps when you want to access a running virtual machine:

1. To log on to a virtual machine, use the vagrant ssh command on your host machine, and specify the hostname; for example:

   Code Block
   LMBP:centos7.0 lkg$ vagrant ssh c7001 Last login: Tue Jan 12 11:20:28 2016 [vagrant@c7001 ~]$

   From this point onward, this terminal window is connected to the virtual machine until you exit the virtual machine. All commands go to the VM, not to your Mac.
   
   Recommendation: Open a second terminal window for your Mac. This is useful when accessing the Ambari Web UI. To distinguish between the two, terminal windows typically list the computer name or VM hostname on each command-line prompt and at the top of the terminal window.
   
   

2. When you first access the VM you will be logged in as user vagrant. Switch to the root user; be sure to include the space between "su" and "-":

   Code Block
   [vagrant@c7001 ~]$ sudo su - Last login: Sun Sep 25 01:34:28 AEST 2016 on pts/0 root@c7001:~#

If at any time you wish to return the terminal window to your host machine:

1. 1. Use the logout command to log out of root
   2. Use the exit command to return to your host machine (Mac)

At this point, the VMs are still running in the background. You can re-issue the vagrant ssh command later, to reconnect, or you can stop the virtual machines. For more information, see the vagrant snapshot command in "Basic Vagrant Commands," later in this Quick Start.

Install Ambari on the Virtual Machines

Prerequisites: Before installing Ambari, the following software packages must be installed on your VM:

# CentOS 6 (for CentOS 7, replace centos6 with centos7 in the repo URL)
# 
# to test public release 2.5.1
wget -O /etc/yum.repos.d/ambari.repo http://public-repo-1.hortonworks.com/ambari/centos6/2.x/updates/2.5.1.0/ambari.repo
yum install ambari-server -y
 
# Ubuntu 14 (for Ubuntu 16, replace ubuntu14 with ubuntu16 in the repo URL)
# to test public release 2.5.1
wget -O /etc/apt/sources.list.d/ambari.list http://public-repo-1.hortonworks.com/ambari/ubuntu14/2.x/updates/2.5.1.0/ambari.list
apt-key adv --recv-keys --keyserver keyserver.ubuntu.com B9733A7A07513CAD
apt-get update
apt-get install ambari-server -y
 
# SUSE 11 (for SUSE 12, replace suse11 with suse12 in the repo URL)
# to test public release 2.5.1
wget -O /etc/zypp/repos.d/ambari.repo http://public-repo-1.hortonworks.com/ambari/suse11/2.x/updates/2.5.1.0/ambari.repo
zypper install ambari-server -y

To install Ambari with default settings, set up and start ambari-server:

ambari-server setup -s
ambari-server start

To check Ambari Server status, issue the following command:
ambari-server status

After Ambari Server has started, launch a browser on your host machine (Mac). Access the Ambari Web UI at http://<hostname>.ambari.apache.org:8080. The <hostname> part of the URL specifies the VM where you installed Ambari; for example:

http://c7001.ambari.apache.org:8080

 Note: The Ambari Server can take some time to launch and be ready to accept connections. Keep trying the URL until you see the login page.

At this point, you can snapshot the VMs to have a cluster with Ambari installed, to rerun later if desired. This is especially helpful when installing Apache Ambari and the HDP stack for the first time; it allows you to back out to fresh VMs running Ambari, and reinstall a fresh HDP stack if you encounter errors. For more information about snapshots, see the vagrant snapshot command in "Basic Vagrant Commands," later in this Quick Start.

Install the HDP Stack

The following instructions describe basic steps for using Ambari to install HDP components.

1. On the Ambari screen, login using default username admin, password admin.

2. On the welcome page, choose "Launch Install Wizard."

3. Specify a name for your cluster, and then click Next.

4. On the Select Version page, choose which version of HDP to install, and then click Next.
   
   

5. On the Install Options page, complete the following steps:

   1. List the FQDNs of the virtual machines. For example:

      Code Block
      c7001.ambari.apache.org c7002.ambari.apache.org c7003.ambari.apache.org

      Alternatively, you can use a range expression:

      Code Block
      c70[01-03].ambari.apache.org

   2. Upload the insecure_private_key file that you created earlier: browse to the ambari-vagrant directory, navigate to the operating system folder for your VM's, and choose the key file.

   3. Change the SSH User Account to vagrant.

   4. Click "Register and Confirm."
      
      

6. On the Confirm Hosts page, Ambari displays installation status.
   If you see a yellow banner with the following message, click on the link to review warnings:

   Image Added
   See the Troubleshooting section (later on this page) for more information.
   
   
7. When all host checks pass, close the warning window:
   Image Added
   
   
8. Click Next to continue:
9. On the Choose Services page, uncheck any components that you do not expect to use. If any are required for selected components, Ambari will request to add them back in.
10. On the Assign Masters screen, choose hosts or simply click Next to use default values.
11. On the Assign Slaves and Clients screen, choose hosts or simply click Next to use default values.
12. On the Customize Services screen
    1. Review services with warning notes, such as Hive and Ambari Metrics in the following image:
       Image Added
    2. Specify missing property values (such as admin passwords) as directed by the installation wizard. When all configurations have been addressed, click Next.
       
       
13. On the Review screen, review the service definitions, and then click Next.
    
    
14. The Install, Start and Test page shows deployment status. This step takes a while; on an early 2013 MacBook Pro, 2.7 GHz core i7 and 16 GB RAM, this step takes 45 minutes.
    
    
15. When the cluster installs successfully, you can snapshot the VMs to have a fresh cluster with Ambari and HDP installed, to rerun later if desired. This allows you to experiment with the cluster and quickly restore back to a previous state if you wish. For more information about snapshots, see the vagrant snapshot command in "Basic Vagrant Commands," later in this Quick Start.

Troubleshooting

This subsection describes a few error conditions that might occur during Ambari installation and HDP cluster deployment:

Confirm Hosts

If you see an error similar to the following on the Confirm Hosts page of the Ambari installation wizard, click the link to see the warnings:
     'Some warnings were encountered while performing checks against the 3 registered hosts above. Click here to see the warnings."

ntpd Error

On the Host Checks window, the following warning indicates that you need to start ntpd on each host:

Image Added
To start the services, for each VM navigate to a terminal window (on your Mac, vagrant ssh <VM-name>). Issue the following commands:

service ntpd start
service ntpd status

You should see messages confirming that ntpd is running. Navigate back to the Host Checks window of the Ambari installation wizard and click Rerun Checks. When all checks complete successfully, click Close to continue the installation process.

Install, Start and Test

If the Install, Start and Test step fails with the following error during DataNode deployment: 

Error: Package: snappy-devel-1.0.5-1.el6.x86_64 (HDP-UTILS-1.1.0.20) 
Requires: snappy(x86-64) = 1.0.5-1.el6 
Installed: snappy-1.1.0-3.el7.x86_64 (@anaconda/7.2)

Run the following commands under the root account on each VM:

yum remove -y snappy-1.1.0-3.el7.x86_64
yum install snappy-devel -y

Stopping and Restarting Virtual Machines

Hadoop is a complex ecosystem with a lot of status checks and cross-component messages. This can make it challenging to halt and restart several VMs and restore them later without warnings or errors.

Recommendations

If you would like to save state for a period of time and you plan to stop using your Mac during that time, if you sleep your Mac the cluster should continue from where it left off after you wake the Mac.

When stopping a set of VMs--if you don't need to save cluster state--it can be helpful to stop all services first, stop ambari-server (ambari-server stop), and then issue a Vagrant halt or suspend command.

When restarting a cluster after halting or taking a snapshot, check Ambari server status and restart it if necessary:

   ambari-server status
   ambari-server start

After logging into the Ambari Web UI, expect to see alert warnings or errors due to timeout conditions. Check the associated messages to determine whether they might affect your use of the virtual cluster. If so, it can be helpful to stop and restart one or more associated components.

Reference: Basic Vagrant Commands

The following table lists several common Vagrant commands. For more information, see Vagrant Command-Line Interface documentation.

Recommendation: After you start the VMs--but before you run anything on the VMs–save a snapshot.  This allows you to restore the initial state of your VMs. This process is much faster than starting the VMs from scratch and then reinstalling Ambari and HDP. You can return to the initial state without destroying other named snapshots that you create later.

More information: https://www.vagrantup.com/docs/getting-started/teardown.html

If you have favorite ways of starting and stopping VMs running a Hadoop cluster, please feel free to share them in the Comments section. Thanks!

...

Edit the /etc/hosts file on your computer so that you will be able to resolve hostnames for the VMs:

sudo -s 'cat ambari-vagrant/append-to-etc-hosts.txt >> /etc/hosts'

Create a private key to use with Ambari.
The vagrant command displays Vagrant command information, and then it creates a private key in the file ~/.vagrant.d/insecure_private_key.

vagrant

Start Linux Virtual Machines

The ambari-vagrant directory (cloned from GitHub) contains several subdirectories, each for a specific Linux distribution. Each subdirectory has scripts and configuration files for running Ambari and HDP on that version of Linux.

To start one or more virtual machines:

...

 Change your current directory to ambari-vagrant:

cd ambari-vagrant

You will see subdirectories for different OS’s.

...

cd into the OS subdirectory for the OS you wish to use. CentOS 6.4 is recommended, because it is quicker to launch than other OS's.
The remainder of this Quick Start uses CentOS 6.4. To install and use another version or distribution of Linux, specify the other directory name in place of centos6.4

cd centos6.4

Important: All VM-focused vagrant commands operate within your current directory. Be sure to run them from the Mac subdirectory associated with the operating system you're using. If you attempt to run a Vagrant command from another directory, it will not find the VM.

...

Copy the private key into your OS directory:

cp ~/.vagrant.d/insecure_private_key .

...

(Optional) If you have at least 16 GB of memory on your Mac, consider increasing the amount of memory allocated to the VMs. Edit the following line in Vagrantfile, increasing 3072 to 4096 or more:

vb.customize ["modifyvm", :id, "--memory", 3072] # RAM allocated to each VM

...

Start one or more VMs, using the ./up.sh command. Each VM will run one HDP node.
Three nodes can run well if you have 16GB of RAM on your Mac.

./up.sh <# of VMs to launch>

...

Check the status of your VM(s). The following example shows the results of ./upsh 3 for CentOS 6.4:

hw100:centos6.4 lkg$ vagrant status

Current machine states:
c6401                     running (virtualbox)
c6402                     running (virtualbox)
c6403                     running (virtualbox)
c6404                     not created (virtualbox)
c6405                     not created (virtualbox)
c6406                     not created (virtualbox)
c6407                     not created (virtualbox)
c6408                     not created (virtualbox)
c6409                     not created (virtualbox)
c6410                     not created (virtualbox)

(You can use the vagrant init command to initialize your current directory as a Vagrant environment, but this step should already be handled by the preceding steps.)

...

Next, log into one of your VMs. For example:

vagrant ssh c6401

From this point onward, this terminal window will operate within the VM until you exit the VM. All commands will go to the VM, not your Mac.
Tip: Open a second terminal window for submitting commands on your Mac. This will be useful when accessing the Ambari Web UI. You can tell which window you're in by looking at the terminal prompt: your VM will list the OS name; your Mac will list your Mac's computer name.

...

When you first access the VM you will be logged in as user vagrant. Change to root user:

sudo su -

...

Install Ambari

Prerequisites: Before installing Ambari, the following software must be installed on your VM:

1. From the terminal window on your VM (where the main ambari service should run?), download the Ambari repository. The following commands download Ambari version 2.2.1.0 and install ambari-server:

   OS	Commands
   CentOS 6	wget -O /etc/yum.repos.d/ambari.repo http://public-repo-1.hortonworks.com/ambari/centos6/2.x/updates/2.2.1.0/ambari.repo yum install ambari-server -y
   CentOS 7	wget -O /etc/yum.repos.d/ambari.repo http://public-repo-1.hortonworks.com/ambari/centos7/2.x/updates/2.2.1.0/ambari.repo yum install ambari-server -y
   Ubuntu 12	wget -O /etc/apt/sources.list.d/ambari.list http://public-repo-1.hortonworks.com/ambari/ubuntu12/2.x/updates/2.2.1.0/ambari.list apt-key adv --recv-keys --keyserver keyserver.ubuntu.com B9733A7A07513CAD apt-get update apt-get install ambari-server -y
   Ubuntu 14	wget -O /etc/apt/sources.list.d/ambari.list http://public-repo-1.hortonworks.com/ambari/ubuntu14/2.x/updates/2.2.1.0/ambari.list apt-key adv --recv-keys --keyserver keyserver.ubuntu.com B9733A7A07513CAD apt-get update apt-get install ambari-server -y

   Note: to run a different version of Ambari, specify the repo URL for the version.

2. To install Ambari with default settings, set up and start ambari-server:

   Code Block
   ambari-server setup -s ambari-server start

   For more information about installation options, see Ambari User Guides.

3. (Optional) For frontend developers only: see "Frontend Development" (later on this page) for extra setup instructions.

4. Once Ambari Server is started, access the Ambari Web UI at http://<hostname>.ambari.apache.org:8080. For example:

   Code Block
   http://c6401.ambari.apache.org:8080

   The URL depends on the OS and the node where you installed Ambari. 
   Note: The Ambari Server can take some time to launch and be ready to accept connections. Keep trying the URL until you see the login page.

5. Login using default username admin, password admin.

6. Choose "Launch Install Wizard."

7. Name your cluster.

8. On the Install Options page, list 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

9. Upload the insecure_private_key file that you created earlier.

10. Specify non-root SSH user vagrant.

11. Follow the onscreen instructions to install your cluster.

Install the HDP Stack

Next, install HDP on your cluster.

http://docs.hortonworks.com/HDPDocuments/Ambari-2.2.1.0/bk_Installing_HDP_AMB/content/ch_Deploy_and_Configure_a_HDP_Cluster.html

Choose which HDP version,  Choose services, Assign master and slave processes, Customize services (here I assigned admin/admin to Hive and Oozie)

Timeline for installing HDP, and mac hardware

Troubleshooting

Other tips:

• yum failed? install yum on your VMs.
  
• Ambari message about THPs? fix transparent huge page setting in /etc/rc.loca (CentOS7)
• ntpd not installed?

Basic Vagrant Commands

Taking Snapshots

A Vagrant snapshot saves the current state of a VM, so that you can re-run the VM from the same point at a future time.

Vagrant makes it easy to take snapshots of the entire cluster.
First, install the snapshot plugin:

vagrant plugin install vagrant-vbox-snapshot --plugin-version=0.0.2

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 c64[04-10] in Vagrantfile so that the snapshot commands only operate on c64[01-03].
Note: Upon resuming a snapshot, you may find that time-sensitive services may be down (e.g, HBase RegionServer is down, etc.)

Tip: After starting the VMs but before you do anything on the VMs, run "vagrant snapshot take init".  This way, you can go back to the initial state of the VMs by running "vagrant snapshot go init"; this only takes seconds (much faster than starting the VMs up from scratch by using up.sh or "vagrant up").  Another advantage of this is that you can always go back to the initial state without destroying other named snapshots that you created.

Misc

To test OS’s other than what’s currently in the ambari-vagrant repo, please see http://www.vagrantbox.es/ for 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.

Pre-Configured Development Environment

Simply edit Vagrantfile to launch a VM with all the tools necessary to build Ambari from source.

cd ambari-vagrant/centos6.4
vi Vagrantfile  <- uncomment the line with "dev-bootstrap.sh"
vagrant up c6401

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

Frontend Development

You can use this set up to develop and test out Ambari Web frontend code against a real Ambari Server on a multi-node environment.

On the host machine:

cd ambari-vagrant/centos6.4
git clone https://git-wip-us.apache.org/repos/asf/ambari.git ambari
cd ambari/ambari-web
npm install
brunch w

On c6401 (where Ambari Server is installed):

cd /usr/lib/ambari-server
mv web web-orig
ln -s /vagrant/ambari/ambari-web/public web
ambari-server restart

With this setup, whenever you change the content of ambari-web files (under ambari-vagrant/ambari/) on the host machine, brunch will pick up changes in the background and update ambari-vagrant/ambari/ambari-web/public.  Because of the symbolic link, the changes are automatically picked up by Ambari Server.  All you have to do is hit refresh on the browser to see the frontend code changes reflected.

Not seeing code changes as expected?  If you have run the maven command to build Ambari previously, you will see files called app.js.gz and vendor.js.gz under the public folder.  You need to delete these files for the frontend code changes to be effective, as the app.js.gz and vendor.js.gz files take precedence over app.js and vendor.js, respectively.