diff --git a/doc/common/section_dashboard_sessions.xml b/doc/common/section_dashboard_sessions.xml index f40ba88683..ef16a7e70f 100644 --- a/doc/common/section_dashboard_sessions.xml +++ b/doc/common/section_dashboard_sessions.xml @@ -9,12 +9,12 @@ >Django sessions framework to handle user session data. However, you can use any available session back end. You customize the session back end through the - SESSION_ENGINE setting in your - - /etc/openstack-dashboard/local_settings - local_settings.py/usr/share/openstack-dashboard/openstack_dashboard/local/local_settings.py - file. + SESSION_ENGINE setting in your local_settings file + (on Fedora/RHEL/CentOS: + /etc/openstack-dashboard/local_settings, on Ubuntu: + local_settings.py and on openSUSE: /usr/share/openstack-dashboard/openstack_dashboard/local/local_settings.py). + The following sections describe the pros and cons of each option as it pertains to deploying the dashboard.
@@ -129,13 +129,12 @@ CACHES = { prompt to exit MySQL. - In the /etc/openstack-dashboard/local_settings.py - /etc/openstack-dashboard/local_settings - /usr/share/openstack-dashboard/openstack_dashboard/local/local_settings.py - file, change these options: + In the local_settings file + (on Fedora/RHEL/CentOS: + /etc/openstack-dashboard/local_settings, on Ubuntu: + local_settings.py and on openSUSE: /usr/share/openstack-dashboard/openstack_dashboard/local/local_settings.py), + change these options: SESSION_ENGINE = 'django.core.cache.backends.db.DatabaseCache' DATABASES = { 'default': { @@ -150,10 +149,7 @@ DATABASES = { } - After configuring the local_settings.py - /etc/openstack-dashboard/local_settings + After configuring the local_settings as shown, you can run the manage.py syncdb command to populate this newly-created database. @@ -165,8 +161,8 @@ Installing indexes ... DEBUG:django.db.backends:(0.008) CREATE INDEX `django_session_c25c2c28` ON `django_session` (`expire_date`);; args=() No fixtures found. - - If you want to avoid a warning when you restart + + On Ubuntu: If you want to avoid a warning when you restart apache2, create a blackhole directory in the dashboard directory, as follows: # sudo mkdir -p /var/lib/dash/.blackhole @@ -174,12 +170,19 @@ No fixtures found. Restart Apache to pick up the default site and symbolic link settings: - # /etc/init.d/apache2 restart - # service httpd restart - # service apache2 restart + On Ubuntu: + # /etc/init.d/apache2 restart + + On Fedora/RHEL/CentOS: + # service httpd restart + # service apache2 restart + + On openSUSE: + # systemctl restart apache2.service + - - Restart the nova-api service to ensure that the + + On Ubuntu, restart the nova-api service to ensure that the API server can connect to the dashboard without error: # sudo restart nova-api