Before you can install and configure the dashboard, meet the requirements in . When you install the dashboard with only OpenStack Object Storage and Identity, the dashboard does not show projects and is unusable. For more information about how to deploy the dashboard, see deployment topics in the developer documentation. Install the dashboard on the node that can contact the Identity service as root: # apt-get install apache2 memcached libapache2-mod-wsgi openstack-dashboard # yum install memcached python-memcached mod_wsgi openstack-dashboard # zypper install memcached python-python-memcached apache2-mod_wsgi openstack-dashboard openstack-dashboard-test The openstack-dashboard-ubuntu-theme package prevents translations, several menus, and the network map from rendering correctly. Remove this package: # apt-get remove --purge openstack-dashboard-ubuntu-theme To install the Apache package: # apt-get install openstack-dashboard-apache This command installs and configures Apache correctly, provided that the user asks for it during the debconf prompts. The default SSL certificate is self-signed, and it is probably wise to have it signed by a root Certificate Authority (CA). Modify the value of CACHES['default']['LOCATION'] in /etc/openstack-dashboard/local_settings.py/etc/openstack-dashboard/local_settings/srv/www/openstack-dashboard/openstack_dashboard/local/local_settings.py to match the ones set in /etc/memcached.conf/etc/sysconfig/memcached. Open /etc/openstack-dashboard/local_settings.py /etc/openstack-dashboard/local_settings and look for this line: CACHES = \ {'default': {'BACKEND': 'django.core.cache.backends.memcached.MemcachedCache', 'LOCATION': '127.0.0.1:11211'}} The address and port must match the ones set in /etc/memcached.conf/etc/sysconfig/memcached. If you change the memcached settings, you must restart the Apache web server for the changes to take effect. You can use options other than memcached option for session storage. Set the session back-end through the SESSION_ENGINE option. To change the timezone, use the dashboard or edit the /etc/openstack-dashboard/local_settings/etc/openstack-dashboard/local_settings.py/srv/www/openstack-dashboard/openstack_dashboard/local/local_settings.py file. Change the following parameter: TIME_ZONE = "UTC" Update the ALLOWED_HOSTS in local_settings.py to include the addresses from which you want to access the dashboard. Edit /etc/openstack-dashboard/local_settings/etc/openstack-dashboard/local_settings.py/srv/www/openstack-dashboard/openstack_dashboard/local/local_settings.py: ALLOWED_HOSTS = ['localhost', 'my-desktop'] This guide assumes that you are running the dashboard on the controller node. You can easily run the dashboard on a separate server by changing the appropriate settings in local_settings.py. Edit /etc/openstack-dashboard/local_settings/etc/openstack-dashboard/local_settings.py/srv/www/openstack-dashboard/openstack_dashboard/local/local_settings.py and change OPENSTACK_HOST to the host name of your Identity service: OPENSTACK_HOST = "controller" Configure Apache: # cp /etc/apache2/conf.d/openstack-dashboard.conf.sample \ /etc/apache2/conf.d/openstack-dashboard.conf # a2enmod rewrite;a2enmod ssl;a2enmod wsgi By default, the openstack-dashboard package enables a database as a session store. Before you continue, you can either: Change the session store. See Set up session storage in the Cloud Administrator Guide. Complete the database session store set up. See Initialize and configure the database. Ensure that the SELinux policy of the system is configured to allow network connections to the HTTP server: # setsebool -P httpd_can_network_connect on Start the Apache web server and memcached: # service apache2 start # service memcached start # chkconfig apache2 on # chkconfig memcached on # service httpd start # service memcached start # chkconfig httpd on # chkconfig memcached on # service apache2 restart # service memcached restart You can now access the dashboard at http://controller/horizon https://controller/ http://controller/dashboard http://controller. Log in with credentials for any user that you created with OpenStack Identity.