Juju Charm - Ceph Dashboard
Go to file
Peter Sabaini 723e009d6b Remove unused tox target
The func-dev target is unused and indeed fails since we don't define
any dev bundles.

func-test-pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/1137

Signed-off-by: Peter Sabaini <peter.sabaini@canonical.com>
Change-Id: I9993b8d8bc55fa1b4c7d61931bfdb6ee4ee3c7b4
2023-09-26 17:20:26 +02:00
src Adds dashboard enablement/deferral logic improvements 2023-09-12 12:57:48 +05:30
tests Doc: fix functest link 2023-09-19 10:29:49 +02:00
unit_tests Fixes SSL conflicts between relation and config data. 2023-08-21 15:42:49 +05:30
.flake8 Initial cut of ceph-dashboard charm 2021-06-24 13:14:57 +00:00
.gitignore Initial cut of ceph-dashboard charm 2021-06-24 13:14:57 +00:00
.gitreview fix .gitreview repo reference 2022-10-19 11:38:55 -04:00
.jujuignore Initial cut of ceph-dashboard charm 2021-06-24 13:14:57 +00:00
.stestr.conf Initial cut of ceph-dashboard charm 2021-06-24 13:14:57 +00:00
.zuul.yaml Updates for jammy enablement 2022-04-11 07:58:18 +02:00
LICENSE Initial cut of ceph-dashboard charm 2021-06-24 13:14:57 +00:00
README.md Remove note about tech-preview state 2023-02-28 09:25:28 -05:00
actions.yaml Add delete user action 2021-09-13 08:59:23 +00:00
build-requirements.txt Migrate to charmhub 2022-02-08 15:05:00 +01:00
charmcraft.yaml Add 2023.2 Bobcat support 2023-08-03 13:49:02 -04:00
config.yaml Add SAML support to ceph-dashboard 2022-04-07 11:20:01 -03:00
copyright Add copyright file 2021-09-13 10:04:54 +00:00
metadata.yaml Merge "Add docs key and point at Discourse" 2023-08-30 15:00:24 +00:00
osci.yaml Doc: fix functest link 2023-09-19 10:29:49 +02:00
rename.sh Migrate to charmhub 2022-02-08 15:05:00 +01:00
requirements-dev.txt Initial cut of ceph-dashboard charm 2021-06-24 13:14:57 +00:00
requirements.txt Pin operator library 2022-10-19 17:44:31 +02:00
test-requirements.txt Use unittest.mock instead of mock 2021-12-16 10:26:24 +00:00
tox.ini Remove unused tox target 2023-09-26 17:20:26 +02:00



The ceph-dashboard charm deploys the Ceph Dashboard, a built-in web-based Ceph management and monitoring application. It works in conjunction with the openstack-loadbalancer charm, which in turn utilises the hacluster charm.



This section covers common and/or important configuration options. See file config.yaml for the full list of options, along with their descriptions and default values. See the Juju documentation for details on configuring applications.


Sets the URL of the Grafana API when using embedded graphs. See Embedded Grafana dashboards.


Sets the hostname or address of the public endpoint used to access the dashboard.


Sets whether certain password restrictions are enforced when a user is created or changes their password.


There are a number of password-* options which impose constraints on which passwords can be used. These options are ignored unless enable-password-policy is set to 'True'.


We are assuming a pre-existing Ceph cluster.

Deploy ceph-dashboard as a subordinate to the ceph-mon charm:

juju deploy ceph-dashboard
juju add-relation ceph-dashboard:dashboard ceph-mon:dashboard

TLS is a requirement for this charm. Enable it by adding a relation to the vault application:

juju add-relation ceph-dashboard:certificates vault:certificates

See Managing TLS certificates in the OpenStack Charms Deployment Guide for more information on TLS.

Note: This charm also supports TLS configuration via charm options ssl_cert, ssl_key, and ssl_ca.

Load balancer

The dashboard is accessed via a load balancer using VIPs and implemented via the openstack-loadbalancer and hacluster charms:

juju deploy -n 3 --config vip= openstack-loadbalancer
juju deploy hacluster openstack-loadbalancer-hacluster
juju add-relation openstack-loadbalancer:ha openstack-loadbalancer-hacluster:ha

Now add a relation between the openstack-loadbalancer and ceph-dashboard applications:

juju add-relation ceph-dashboard:loadbalancer openstack-loadbalancer:loadbalancer

Dashboard user

Credentials are needed to log in to the dashboard. Set these up by applying an action to any ceph-dashboard unit. For example, to create an administrator user called 'admin':

juju run-action --wait ceph-dashboard/0 add-user username=admin role=administrator

The command's output will include a generated password.

The dashboard can then be accessed on the configured VIP and on port 8443:

Embedded Grafana dashboards

To embed Grafana dashboards within the Ceph dashboard some additional relations are required (Grafana, Telegraf, and Prometheus are assumed to be pre-existing):

juju add-relation ceph-dashboard:grafana-dashboard grafana:dashboards
juju add-relation ceph-dashboard:prometheus prometheus:website
juju add-relation ceph-mon:prometheus prometheus:target
juju add-relation ceph-osd:juju-info telegraf:juju-info
juju add-relation ceph-mon:juju-info telegraf:juju-info

Grafana, Telegraf, and Prometheus should be related in the standard way:

juju add-relation grafana:grafana-source prometheus:grafana-source
juju add-relation telegraf:prometheus-client prometheus:target
juju add-relation telegraf:dashboards grafana:dashboards

When Grafana is integrated with the Ceph Dashboard it requires TLS, so add a relation to Vault (the grafana charm also supports TLS configuration via ssl_* charm options):

juju add-relation grafana:certificates vault:certificates

Important: Ceph Dashboard will (silently) fail to display Grafana output if the client browser cannot validate the Grafana server's TLS certificate. Either ensure the signing CA certificate is known to the browser or, if in a testing environment, contact the Grafana dashboard directly and have the browser accept the unverified certificate.

Grafana should be configured with the following charm options:

juju config grafana anonymous=True
juju config grafana allow_embedding=True

The grafana charm also requires the vonage-status-panel and grafana-piechart-panel plugins. The install_plugins configuration option should be set to include URLs from which these plugins can be downloaded. They are currently available from https://storage.googleapis.com/plugins-community. For example:

juju config grafana install_plugins="https://storage.googleapis.com/plugins-community/vonage-status-panel/release/1.0.11/vonage-status-panel-1.0.11.zip,https://storage.googleapis.com/plugins-community/grafana-piechart-panel/release/1.6.2/grafana-piechart-panel-1.6.2.zip"

Telegraf should be configured with the following charm option:

juju config telegraf hostname="{host}"

Note: The above command is to be invoked verbatim; no substitution is required.

Currently the dashboard does not autodetect the API endpoint of the Grafana service. It needs to be provided via a configuration option:

juju config ceph-dashboard grafana-api-url="https://<IP of grafana unit>:3000"

Prometheus alerting

To enable alerting for an existing Prometheus service add the following relations:

juju add-relation ceph-dashboard:prometheus prometheus:website
juju add-relation ceph-mon:prometheus prometheus:target
juju add-relation ceph-dashboard:alertmanager-service prometheus-alertmanager:alertmanager-service
juju add-relation prometheus:alertmanager-service prometheus-alertmanager:alertmanager-service

Ceph Object storage

To enable Object storage management of an existing Ceph RADOS Gateway service add the following relation:

juju add-relation ceph-dashboard:radosgw-dashboard ceph-radosgw:radosgw-user

Note: For Ceph versions older than Pacific the dashboard can only be related to a single ceph-radosgw application.


This section lists Juju actions supported by the charm. Actions allow specific operations to be performed on a per-unit basis. To display action descriptions run juju actions --schema ceph-dashboard. If the charm is not deployed then see file actions.yaml.

  • add-user
  • delete-user


The OpenStack Charms project maintains two documentation guides:


Please report bugs on Launchpad.