Operations Guide
- 1 Operations Overview
- 2 Tutorials
- 3 Third-Party Integrations
- 4 Managing Identity
- 5 Managing Compute
- 6 Managing ESX
- 7 Managing Block Storage
- 8 Managing Object Storage
- 9 Managing Networking
- 10 Managing the Dashboard
- 11 Managing Orchestration
- 12 Managing Monitoring, Logging, and Usage Reporting
- 13 System Maintenance
- 14 Backup and Restore
- 15 Troubleshooting Issues
10 Managing the Dashboard
Information about managing and configuring the Dashboard service.
10.1 Configuring the Dashboard Service #
Horizon is the OpenStack service that serves as the basis for the HPE Helion OpenStack dashboards.
The dashboards provide a web-based user interface to HPE Helion OpenStack services including Compute, Volume Operations, Networking, and Identity.
Along the left side of the dashboard are sections that provide access to Project and Identity sections. If your login credentials have been assigned the 'admin' role you will also see a separate Admin section that provides additional system-wide setting options.
Across the top are menus to switch between projects and menus where you can access user settings.
10.1.1 Dashboard Service and TLS in HPE Helion OpenStack #
By default, the Dashboard service is configured with TLS in the input model (ardana-input-model). You should not disable TLS in the input model for the Dashboard service. The normal use case for users is to have all services behind TLS, but users are given the freedom in the input model to take a service off TLS for troubleshooting or debugging. TLS should always be enabled for production environments.
Make sure that horizon_public_protocol and
horizon_private_protocol are both be set to use https.
10.2 Changing the Dashboard Timeout Value #
The default session timeout for the dashboard is 1800 seconds or 30 minutes. This is the recommended default and best practice for those concerned with security.
As an administrator, you can change the session timeout by changing the value of the SESSION_TIMEOUT to anything less than or equal to 14400, which is equal to four hours. Values greater than 14400 should not be used due to Keystone constraints.
Warning
Increasing the value of SESSION_TIMEOUT increases the risk of abuse.
10.2.1 How to Change the Dashboard Timeout Value #
Follow these steps to change and commit the Horizon timeout value.
Log in to the Cloud Lifecycle Manager.
Edit the Dashboard config file at
~/openstack/my_cloud/config/horizon/local_settings.pyand, if it is not already present, add a line forSESSION_TIMEOUTabove the line forSESSION_ENGINE.Here is an example snippet, in bold:
SESSION_TIMEOUT = <timeout value> SESSION_ENGINE = 'django.contrib.sessions.backends.db'
Important
Do not exceed the maximum value of 14400.
Commit the changes to git:
git add -A git commit -a -m "changed Horizon timeout value"
Run the configuration processor:
cd ~/openstack/ardana/ansible ansible-playbook -i hosts/localhost config-processor-run.yml
Update your deployment directory:
cd ~/openstack/ardana/ansible ansible-playbook -i hosts/localhost ready-deployment.yml
Run the Dashboard reconfigure playbook:
cd ~/scratch/ansible/next/ardana/ansible ansible-playbook -i hosts/verb_hosts horizon-reconfigure.yml