Introduction to the OpenStack Dashboard

Red Hat OpenStack Platform 15-Beta

An overview of the OpenStack dashboard graphical user interface

OpenStack Documentation Team

Abstract

This guide provides an outline of the options available in the OpenStack dashboard user interface.

Preface

This document provides an outline of the options available in the OpenStack dashboard graphical user interface.

Chapter 1. The OpenStack Dashboard

The OpenStack dashboard is a web-based graphical user interface for managing OpenStack services.

To access the browser dashboard, the dashboard service must be installed, and you must know the dashboard host name (or IP) and login password. The dashboard URL is:

http://HOSTNAME/dashboard/

Dashboard Login Screen

Chapter 2. The Admin Tab

The Admin tab provides an interface where administrative users can view usage and manage instances, volumes, flavors, images, projects, users, services, and quotas.

Note

The Admin tab displays in the main window only if you have logged in as a user with administrative privileges.

Admin Tab

The following options are available in the Admin tab:

Table 2.1. System Panel

Parameter NameDescription

Overview

View basic reports.

Resource Usage

Use the following tabs to view the following usages:

  • Usage Report - View the usage report.
  • Stats - View the statistics of all resources.

Hypervisors

View the hypervisor summary.

Host Aggregates

View, create, and edit host aggregates. View the list of availability zones.

Instances

View, pause, resume, suspend, migrate, soft or hard reboot, and delete running instances that belong to users of some, but not all, projects. Also, view the log for an instance or access an instance using the console.

Volumes

View, create, edit, and delete volumes, and volume types.

Flavors

View, create, edit, view extra specifications for, and delete flavors. Flavors are the virtual hardware templates in OpenStack.

Images

View, create, edit properties for, and delete custom images.

Networks

View, create, edit properties for, and delete networks.

Routers

View, create, edit properties for, and delete routers.

Floating IPs

View allocated floating IP addresses for all projects.

Defaults

View and edit the default quotas (maximum limits) for resources in the environment.

Metadata Definitions

Import, view, and edit metadata definition namespaces, and associate the metadata definitions with specific resource types.

System Information

Contains the following tabs:

  • Services - View a list of the services.
  • Compute Services - View a list of all Compute services.
  • Network Agents - View the network agents.
  • Block Storage Services - View a list of all Block Storage services.
  • Orchestration Services - View a list of all Orchestration services.

2.1. View Allocated Floating IP Addresses

You can use the Floating IPs panel to view a list of allocated floating IP addresses. This information can also be accessed using the command line:

$ nova list --all-tenants

Chapter 3. The Project Tab

The Project tab provides an interface for viewing and managing the resources of a project. Set a project as active in Identity > Projects to view and manage resources in that project.

Dashboard Tab

The following options are available in the Project tab:

Table 3.1. The Compute Tab

Parameter NameDescription

Overview

View reports for the project.

Instances

View, launch, create a snapshot from, stop, pause, or reboot instances, or connect to them through the console.

Volumes

Use the following tabs to complete these tasks:

  • Volumes - View, create, edit, and delete volumes.
  • Volume Snapshots - View, create, edit, and delete volume snapshots.

Images

View images, instance snapshots, and volume snapshots created by project users, and any images that are publicly available. Create, edit, and delete images, and launch instances from images and snapshots.

Access & Security

Use the following tabs to complete these tasks:

  • Security Groups - View, create, edit, and delete security groups and security group rules.
  • Key Pairs - View, create, edit, import, and delete key pairs.
  • Floating IPs - Allocate an IP address to or release it from a project.
  • API Access - View API endpoints, download the OpenStack RC file, download EC2 credentials, and view credentials for the logged-in project user.

Table 3.2. The Network Tab

Parameter NameDescription

Network Topology

View the interactive topology of the network.

Networks

Create and manage public and private networks and subnets.

Routers

Create and manage routers.

Trunks

Create and manage trunks. Requires the trunk extension enabled in OpenStack Networking (neutron).

Table 3.3. The Object Store Tab

Parameter NameDescription

Containers

Create and manage storage containers. A container is a storage compartment for data, and provides a way for you to organize your data. It is similar to the concept of a Linux file directory, but it cannot be nested.

Table 3.4. The Orchestration Tab

Parameter NameDescription

Stacks

Orchestrate multiple composite cloud applications using templates, through both an OpenStack-native REST API and a CloudFormation-compatible Query API.

Chapter 4. The Identity Tab

The Identity tab provides an interface for viewing and managing projects and users.

Identity Tab

The following options are available in the Identity tab:

  • Projects - View, create, edit, and delete projects/tenants, view project usage, add or remove users as project members, modify quotas, and set an active project.
  • Users - View, create, edit, disable, and delete users, and change user passwords. The Users tab displays only if you are logged in as a user with administrative privileges.

For more information on procedures to manage your cloud using the OpenStack Dashboard, see the following guides:

Chapter 5. Customizing the Dashboard

The OpenStack dashboard for Red Hat OpenStack Platform uses a default theme (RCUE), which is stored inside the horizon container. You can customize the look and feel of the OpenStack dashboard by adding your own theme to the container image and customizing certain dashboard parameters. This customization allows you to modify the following elements:

  • Logo
  • Site colors
  • Stylesheets
  • HTML title
  • Site branding link
  • Help URL
Note

To ensure continued support for modified OpenStack Platform container images, the resulting images must comply with the "Red Hat Container Support Policy".

5.1. Obtaining the horizon container image

You must obtain a copy of the horizon container image. You can pull this image either into the undercloud or a separate client system running podman. To pull the horizon container image, run the following command:

$ sudo podman pull registry.access.redhat.com/rhosp15/openstack-horizon

You can now use this image as a basis for a modified image.

5.2. Obtaining the RCUE theme

The horizon container image is configured to use the Red Hat branded RCUE theme by default. You can use this theme as a basis for your own theme and extract a copy from the container image.

Make a directory for your theme:

$ mkdir ~/horizon-themes
$ cd ~/horizon-themes

Start a container that executes a null loop. For example, run the following command:

$ sudo podman run --rm -d --name horizon-temp registry.access.redhat.com/rhosp15/openstack-horizon /usr/bin/sleep infinity

Copy the RCUE theme from the container to your local directory:

$ sudo podman cp -a horizon-temp:/usr/share/openstack-dashboard/openstack_dashboard/themes/rcue .

Kill the container:

$ sudo podman kill horizon-temp

You should now have a local copy of the RCUE theme.

5.3. Creating your own theme based on RCUE

To use RCUE as a basis, copy the entire RCUE theme directory rcue to a new location, for example mytheme:

$ cp -r rcue mytheme

To change a theme’s colors, graphics, fonts, among others, edit the files in mytheme. When editing this theme, check for all instances of rcue and ensure you change them to the new mytheme name. This includes paths, files, and directories.

5.4. Creating a file to enable your theme and customize the dashboard

To enable your theme in the dashboard container, you must create a file to override the AVAILABLE_THEMES parameter. Create a new file called _12_mytheme_theme.py in the horizon-themes directory and add the following content:

AVAILABLE_THEMES = [('mytheme', 'My Custom Theme', 'themes/mytheme')]

The 12 in the file name ensures this file is loaded after the RCUE file, which uses 11, and overrides the AVAILABLE_THEMES parameter.

You can also set custom parameters in the _12_mytheme_theme.py file. For example:

SITE_BRANDING

Set the HTML title that appears at the top of the browser window. For example:

SITE_BRANDING = "Example, Inc. Cloud"
SITE_BRANDING_LINK

Changes the hyperlink of the theme’s logo, which normally redirects to horizon:user_home by default. For example:

SITE_BRANDING_LINK = "http://example.com"

5.5. Generating a modified horizon image

Once your custom theme is ready, you can create a new container image that enables and uses your theme. Use a dockerfile to generate a new container image using the original horizon image as a basis. The following is an example of a dockerfile:

FROM registry.access.redhat.com/rhosp15/openstack-horizon
MAINTAINER Acme
LABEL name="rhosp15/openstack-horizon-mytheme" vendor="Acme" version="0" release="1"
COPY mytheme /usr/share/openstack-dashboard/openstack_dashboard/themes/mytheme
COPY _12_mytheme_theme.py /etc/openstack-dashboard/local_settings.d/_12_mytheme_theme.py
RUN sudo chown horizon:horizon /etc/openstack-dashboard/local_settings.d/_12_mytheme_theme.py

Save this file in your horizon-themes directory as dockerfile.

To use the dockerfile to generate the new image, run the following command:

sudo podman build . -t "192.168.24.1:8787/rhosp15/openstack-horizon-mytheme:0-1"

The -t option names and tags the resulting image. It uses the following syntax:

[LOCATION]/[NAME]:[TAG]
LOCATION
This is usually the location of the container registry that the overcloud eventually pulls uses to pull images. In this instance, you will push this image to the undercloud’s container registry, so set this to the undercloud IP and port.
NAME
For consistency, this is usually the same name as the original container image followed by the name of your theme. In this case, it is rhosp15/openstack-horizon-mytheme.
TAG
The tag for the image. Red Hat uses the version and release labels as a basis for this tag and it is usually a good idea to follow this convention. If you generate a new version of this image, increment the release (e.g. 0-2).

Push the resulting image to the undercloud’s container registry:

$ podman push 192.168.24.1:8787/rhosp15/openstack-horizon-mytheme:0-1
Important

If updating or upgrading Red Hat OpenStack Platform, you must reapply the theme to the new horizon image and push a new version of the modified image to the undercloud.

5.6. Using the modified container image in the overcloud

To use the resulting container image with your overcloud deployment, edit the environment file that contains the list of container image locations. This environment file is usually named overcloud-images.yaml.

Edit the DockerHorizonConfigImage and DockerHorizonImage parameters to point to your modified container image. For example:

parameter_defaults:
  ...
  DockerHorizonConfigImage: 192.0.2.5:8787/rhosp15/openstack-horizon-mytheme:0-1
  DockerHorizonImage: 192.0.2.5:8787/rhosp15/openstack-horizon-mytheme:0-1
  ...

Save this new version of the overcloud-images.yaml file.

5.7. Editing puppet parameters

The director provides a set of horizon parameters you can modify using environment files. You can also use the ExtraConfig hook to set Puppet hieradata. For example, the default help URL points to https://access.redhat.com/documentation/en/red-hat-openstack-platform. You can modify this URL with the following environment file content:

parameter_defaults:
  ExtraConfig:
    horizon::help_url: "http://openstack.example.com"

5.8. Deploying an overcloud with a customized Dashboard

To deploy the overcloud with your dashboard customizations, include the following environment files:

  • The environment file with your modified container image locations.
  • The environment file with additional dashboard modifications.
  • Any other environment files relevant to your overcloud’s configuration.

For example:

$ openstack overcloud deploy --templates \
    -e /home/stack/templates/overcloud-images.yaml \
    -e /home/stack/templates/help_url.yaml \
    [OTHER OPTIONS]

Legal Notice

Copyright © 2019 Red Hat, Inc.
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.