First off, create a virtual environment and install the Horizon dependencies:

$ git clone
$ cd horizon
$ python tools/

We will refer to the folder you are now in as <HORIZON_DIR>. If you want more details on how to install Horizon, you can have a look at the Horizon documentation, especially their quickstart tutorial.

Then, you need to install Watcher Dashboard on the server running Horizon. To do so, you can issue the following commands:

$ git clone
$ cd watcher-dashboard
$ pip install -e .

We will refer to the folder you are now in as <DASHBOARD_DIR>.

The next step is now to register the Watcher Dashboard plugins against your Horizon. To do so, you can execute the tools/

$ ./tools/ . <HORIZON_DIR>

This script will then create the needed symlinks within Horizon so that it can load the Watcher plugin when it starts.

If you wish to have Horizon running being an Apache server, do not forget to start the service via the following command:

$ sudo service apache2 restart

For more details on how to configure Horizon for a production environment, you can refer to their online installation guide.

DevStack setup

Add the following to your DevStack local.conf file

enable_plugin watcher-dashboard

Unit testing

First of all, you have to create an environment to run your tests in. This step is actually part of the script which creates and maintains a clean virtual environment.

Here below is the basic command to run Watcher Dashboard tests:

$ ./

The first time you will issue the command above, you will be asked if you want to create a virtual environment. So unless you have installed everything manually (in which case you should use the -N flag), you need to accept

Integration testing

Before being able to run integration tests, you need to have a Horizon server running with Watcher Dashboard plugin configured. To do so, you can run a test server using the following command:

$ ./ --runserver

By default, integration tests expect to find a running Horizon server at http://localhost:8000/ but this can be customized by editing the watcher_dashboard/test/integration_tests/horizon.conf configuration file. Likewise, this Horizon will be looking, by default, for a Keystone backend at http://localhost:5000/v2.0. So in order to customize its location, you will have to edit watcher_dashboard/test/ by updating the OPENSTACK_KEYSTONE_URL variable.

To run integration tests:

$ ./ --integration

You can use PhantomJS as a headless browser to execute your integration tests. On an Ubuntu distribution you can install it via the following command:

$ sudo apt-get install phantomjs

Then you can run your integration tests like this:

$ ./ --integration --selenium-headless

Please note that these commands are also available via tox.


As of the Mitaka release, the dashboard for watcher is now maintained outside of the Horizon codebase, in this repository.


You can enable policies on Watcher Optimization panel, by updating in the <HORIZON_DIR>/openstack_dashboard/ configuration file the following parameters

POLICY_FILES = { … ‘infra-optim’: ‘watcher_policy.json’, }

You can also update the file <HORIZON_DIR>/openstack_dashboard/conf/watcher_policy.conf to customize your policies.