Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Add ceph/dashboard role (feature) #22

Open
sk4zuzu opened this issue Oct 20, 2023 · 0 comments
Open

Add ceph/dashboard role (feature) #22

sk4zuzu opened this issue Oct 20, 2023 · 0 comments
Milestone

Comments

@sk4zuzu
Copy link
Contributor

sk4zuzu commented Oct 20, 2023

  1. The Ceph dashboard itself can be easily enabled with such basic steps executed on mgrs (for example):
ceph config set mgr mgr/dashboard/ssl false
ceph dashboard set-pwd-policy-enabled false

ceph mgr module disable dashboard
ceph mgr module enable dashboard

ceph dashboard ac-user-create oneadmin -i- administrator <<< password

and then accessed at http://mgr-ip:8080/.

  1. We can reuse Prometheus and Grafana instances we deploy already in OpenNebula. To enable Prometheus module in Ceph:
ceph mgr module enable prometheus

then Prometheus config needs to be updated like so (the Ceph exporters run on mgrs on the 9283/TCP port):

global:
  scrape_interval: 5s
scrape_configs:
  - job_name: 'prometheus'
    static_configs:
      - targets: ['localhost:9090']
  - job_name: 'ceph'
    static_configs:
      - targets: ['localhost:9283']
  - job_name: 'node-exporter'
    static_configs:
      - targets: ['localhost:9100']
  1. Because we deploy our own Prometheus and Grafana instances already, there is little value in using ceph-dashboard role from ceph-ansible (which tries to install some components with docker / podman). Ideally all the above config could be implemented in a simple ceph/dashboard role in one-deploy 👍 .

☝️ 😌

@rsmontero rsmontero added this to the Release 7.0 milestone Apr 19, 2024
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants