Pallav Kulshreshtha 63e278dc80 AMBARI-14084. Ambari Views : each view should have separate log file for better troubleshooting (Nitiraj Rathore via pallavkul)		9 years ago
..
src	63e278dc80 AMBARI-14084. Ambari Views : each view should have separate log file for better troubleshooting (Nitiraj Rathore via pallavkul)	9 years ago
cs-view.jpg	7f491baea3 AMBARI-9111: Various cleanup for CS view	10 years ago
pom.xml	e0bf50fdc0 AMBARI-14084 : ViewRegistry now looks for file view.log4j.properties using the view archive classloader and loads all the log4j properties in it using PropertyConfigurator. Separate log4j configuraiton files added to all core views. (Nitiraj Rathore via dipayanb)	9 years ago
readme.md	e2b8a0e92c AMBARI-11436. CapScheduler Auto-Create and Cluster association (Erik Bergenholtz via rlevas)	10 years ago

Capacity Scheduler View

Description

This View provides a UI to manage queues for the YARN Capacity Scheduler.

Requirements

Ambari 2.1.0 or later
YARN

Build

The view can be built as a maven project.

mvn clean install

The build will produce the view archive.

target/capacity-scheduler-???-SNAPSHOT.jar

Place the view archive on the Ambari Server and restart to deploy.

cp capacity-scheduler-???-SNAPSHOT /var/lib/ambari-server/resources/views/
ambari-server restart

Deploying the View

Use the Ambari Vagrant setup to create a cluster:

Deploy the Capacity Scheduler view into Ambari.

cp capacity-scheduler-???-SNAPSHOT /var/lib/ambari-server/resources/views/
ambari-server restart

From the Ambari Administration interface, create a view instance.

Property	Value
Details: Instance Name	CS_1
Details: Display Name	Queue Manager
Details: Description	Browse and manage YARN Capacity Scheduler queues
Properties: Ambari Cluster URL	http://c6401.ambari.apache.org:8080/api/v1/clusters/MyCluster
Properties: Operator Username	admin
Properties: Operator Password	password

http://c6401.ambari.apache.org:8080/#/main/views/CAPACITY-SCHEDULER/???/CS_1

Local Development

If you want to perform UI development without having to build and redeploy the view package, you can mount the build target output as a symlink to your vagrant instance. UI changes will be picked-up with a browser refresh.

After building and deploying the View, delete the view work directory on the Ambari Server.

cd /var/lib/ambari-server/resources/views/work
rm -rf CAPACITY-SCHEDULER\{0.3.0\}/

Create a symlink from the vagrant machine running your Ambari Server to your local machine.

ln -s /vagrant/ambari/contrib/views/capacity-scheduler/target/classes/ CAPACITY-SCHEDULER\{0.3.0\}

Restart Ambari Server, login and browse to the view.

ambari-server restart
http://c6401.ambari.apache.org:8080/#/main/views/CAPACITY-SCHEDULER/0.3.0/CS_1

If you modify the view UI code on your machine and re-build, the UI will pickup the changes on browser refresh.