Skip to content
Juju Charm - OpenStack dashboard
Branch: master
Clone or download
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
actions Add security-checklist action Mar 13, 2019
charmhelpers Sync charm-helpers to enable Ubuntu Disco Apr 5, 2019
hooks Fix websso path formatting May 7, 2019
lib Update tox.ini files from release-tools gold copy Sep 9, 2016
scripts Sync scripts/. Apr 9, 2013
templates Fix incorrect policy rules May 3, 2019
tests Add security-checklist action Mar 13, 2019
unit_tests Add option to hide/show consistency groups tab Mar 19, 2019
.gitignore Enable Xenial Queens amulet tests at gate Mar 2, 2018
.gitreview OpenDev Migration Patch Apr 19, 2019
.project Rebase on trunk Feb 24, 2014
.pydevproject Rebase on trunk Feb 24, 2014
.stestr.conf Replace ostestr with stestr in testing framework. Mar 7, 2019
.zuul.yaml Added tox environment for gathering coverage Mar 1, 2019
LICENSE Re-license charm as Apache-2.0 Jul 3, 2016
Makefile Tests dir no longer need copy of charmhelpers Oct 10, 2018
README.md Allow custom theme install Jul 12, 2018
actions.yaml Add security-checklist action Mar 13, 2019
charm-helpers-hooks.yaml Update charm-helpers-hooks.yaml and sync ch Feb 12, 2019
config.yaml Add option to hide/show consistency groups tab Mar 19, 2019
copyright Re-license charm as Apache-2.0 Jul 3, 2016
hardening.yaml Disable apache mod_status when hardening apache Sep 15, 2017
icon.svg Update charm icon Aug 2, 2017
metadata.yaml Update series metadata Apr 5, 2019
requirements.txt Update requirements Oct 3, 2018
revision added syslog functionality Feb 3, 2014
setup.cfg Add project infomation into setup.cfg Jan 9, 2019
test-requirements.txt Replace ostestr with stestr in testing framework. Mar 7, 2019
tox.ini Replace ostestr with stestr in testing framework. Mar 7, 2019

README.md

Overview

The OpenStack Dashboard provides a Django based web interface for use by both administrators and users of an OpenStack Cloud.

It allows you to manage Nova, Glance, Cinder and Neutron resources within the cloud.

Usage

The OpenStack Dashboard is deployed and related to keystone:

juju deploy openstack-dashboard
juju add-relation openstack-dashboard keystone

The dashboard will use keystone for user authentication and authorization and to interact with the catalog of services within the cloud.

The dashboard is accessible on:

http(s)://service_unit_address/horizon

At a minimum, the cloud must provide Glance and Nova services.

SSL configuration

To fully secure your dashboard services, you can provide a SSL key and certificate for installation and configuration. These are provided as base64 encoded configuration options::

juju set openstack-dashboard ssl_key="$(base64 my.key)" \
    ssl_cert="$(base64 my.cert)"

The service will be reconfigured to use the supplied information.

HA/Clustering

There are two mutually exclusive high availability options: using virtual IP(s) or DNS. In both cases, a relationship to hacluster is required which provides the corosync back end HA functionality.

To use virtual IP(s) the clustered nodes must be on the same subnet such that the VIP is a valid IP on the subnet for one of the node's interfaces and each node has an interface in said subnet. The VIP becomes a highly-available API endpoint.

At a minimum, the config option 'vip' must be set in order to use virtual IP HA. If multiple networks are being used, a VIP should be provided for each network, separated by spaces. Optionally, vip_iface or vip_cidr may be specified.

To use DNS high availability there are several prerequisites. However, DNS HA does not require the clustered nodes to be on the same subnet. Currently the DNS HA feature is only available for MAAS 2.0 or greater environments. MAAS 2.0 requires Juju 2.0 or greater. The clustered nodes must have static or "reserved" IP addresses registered in MAAS. The DNS hostname(s) must be pre-registered in MAAS before use with DNS HA.

At a minimum, the config option 'dns-ha' must be set to true and at least one of 'os-public-hostname', 'os-internal-hostname' or 'os-internal-hostname' must be set in order to use DNS HA. One or more of the above hostnames may be set.

The charm will throw an exception in the following circumstances: If neither 'vip' nor 'dns-ha' is set and the charm is related to hacluster If both 'vip' and 'dns-ha' are set as they are mutually exclusive If 'dns-ha' is set and none of the os-{admin,internal,public}-hostname(s) are set

Whichever method has been used to cluster the charm the 'secret' option should be set to ensure that the Django secret is consistent across all units.

Keystone V3

If the charm is being deployed into a keystone v3 enabled environment then the charm needs to be related to a database to store session information. This is only supported for Mitaka or later.

Use with a Load Balancing Proxy

Instead of deploying with the hacluster charm for load balancing, its possible to also deploy the dashboard with load balancing proxy such as HAProxy:

juju deploy haproxy
juju add-relation haproxy openstack-dashboard
juju add-unit -n 2 openstack-dashboard

This option potentially provides better scale-out than using the charm in conjunction with the hacluster charm.

Custom Theme

This charm supports providing a custom theme as documented in the [themes configuration]. In order to enable this capability the configuration options 'ubuntu-theme' and 'default-theme' must both be turned off and the option 'custom-theme' turned on.

Once the option is enabled a custom theme can be provided via a juju resource. The resource should be a .tgz file with the contents of your custom theme. If the file 'local_settings.py' is included it will be sourced.

juju attach-resource openstack-dashboard theme=theme.tgz 

Repeating the attach-resource will update the theme and turning off the custom-theme option will return to the default.

You can’t perform that action at this time.