openstack dashboard #13

  • By charmers
  • Latest version (#13)
  • precise
  • Stable
  • Edge

Description

The OpenStack Dashboard provides a full feature web interface for interacting
with instances, images, volumes and networks within an OpenStack deployment.

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-unit 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.

High Availability

The OpenStack Dashboard charm supports HA in-conjunction with the hacluster
charm:

juju deploy hacluster dashboard-hacluster
juju set openstack-dashboard vip="192.168.1.200"
juju add-relation openstack-dashboard dashboard-hacluster
juju add-unit -n 2 openstack-dashboard

After addition of the extra 2 units completes, the dashboard will be
accessible on 192.168.1.200 with full load-balancing across all three units.

Please refer to the charm configuration for full details on all HA config
options.

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.

Configuration

ssl_key
(string) Base64 encoded SSL key to use with certificate specified as ssl_cert.
openstack-origin
(string) Repository from which to install. May be one of the following: distro (default), ppa:somecustom/ppa, a deb url sources entry, or a supported Cloud Archive release pocket. Supported Cloud Archive sources include: cloud:precise-folsom, cloud:precise-folsom/updates, cloud:precise-folsom/staging, cloud:precise-folsom/proposed. Note that updating this setting to a source that is known to provide a later version of OpenStack will trigger a software upgrade.
distro
ubuntu-theme
(string) Use Ubuntu theme for the dashboard.
yes
vip_cidr
(int) Netmask that will be used for the Virtual IP
24
vip
(string) Virtual IP to use to front openstack dashboard ha configuration
webroot
(string) Directory where application will be accessible, relative to http://$hostname/.
/horizon
secret
(string) Secret for Horizon to use when securing internal data; set this when using multiple dashboard units.
ssl_cert
(string) Base64 encoded SSL certificate to install and use for API ports. . juju set swift-proxy ssl_cert="$(cat cert | base64)" \ ssl_key="$(cat key | base64)" . Setting this value (and ssl_key) will enable reverse proxying, point Swifts's entry in the Keystone catalog to use https, and override any certficiate and key issued by Keystone (if it is configured to do so).
vip_iface
(string) Network Interface where to place the Virtual IP
eth0
ha-mcastport
(int) Default multicast port number that will be used to communicate between HA Cluster nodes.
5410
debug
(string) Show Django debug messages.
no
offline-compression
(string) Use pre-generated Less compiled JS and CSS.
yes
default-role
(string) Default role for Horizon operations that will be created in Keystone upon introduction of an identity-service relation.
Member
ha-bindiface
(string) Default network interface on which HA cluster will bind to communication with the other members of the HA Cluster.
eth0