...
You will see subdirectories for different OS’s. “cd” into the OS that you want to test. centos6.4 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.4
./up.sh <# of VMs to launch>
|
...
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.
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:
Code Block |
---|
cd ambari-vagrant/ambari 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):
Code Block |
---|
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/), 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.