Project

General

Profile

Feature #45565

cephadm: A service should provide information about itself

Added by Volker Theile 9 months ago. Updated 7 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
cephadm
Target version:
% Done:

0%

Source:
Development
Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:

Description

As a normal user of Ceph without having much insight of the development and its inner life i expect that a fresh deployed service give me some hints and information about itself that i need to work with.

Think about a user deploys a Grafana service to a specific node. The first thing he wants to know after it has been finished is some information about the service. In the special case of Grafana, Alertmanager, Prometheus and all other existing or coming services that provide a UI, this might be the information how to reach it, e.g. by providing the IP address of the host/node or the URL of the UI of this service. I don't expect that every user knows that Grafana is running on port 3000 or Alertmanager on 9093.

Ideally each service should provide self explaining information/metadata that are helpful for users/admins.


Related issues

Related to Orchestrator - Bug #45876: cephadm: handle port conflicts gracefully New

History

#1 Updated by Sebastian Wagner 9 months ago

  • Description updated (diff)

#2 Updated by Sebastian Wagner 9 months ago

  • Project changed from mgr to Orchestrator
  • Category changed from orchestrator to cephadm

#3 Updated by Sebastian Wagner 8 months ago

  • Related to Bug #45876: cephadm: handle port conflicts gracefully added

#4 Updated by Sebastian Wagner 7 months ago

See DaemonDescription's service_url

Also available in: Atom PDF