Project

General

Profile

Feature #45652

cephadm: Allow user to select monitoring stack ports

Added by Juan Miguel Olmo Martínez about 1 year ago. Updated 28 days ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
cephadm/monitoring
Target version:
-
% Done:

0%

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

Description

User must be able to change the ports settings for the monitoring stack

We can continue using as default:

port_map = {
    "prometheus": [9095],  # Avoid default 9090, due to conflict with cockpit UI
    "node-exporter": [9100],
    "grafana": [3000],
    "alertmanager": [9093, 9094],
}


Related issues

Related to Orchestrator - Bug #45876: cephadm: handle port conflicts gracefully New
Related to Orchestrator - Feature #45996: adopted prometheus instance uses port 9095, regardless of original port number New
Related to Orchestrator - Feature #48822: Add proper port management to mgr/cephadm Closed
Duplicates Orchestrator - Bug #50359: Configure the IP address for the monitoring stack components Resolved

History

#1 Updated by Sebastian Wagner about 1 year ago

  • Description updated (diff)
  • Category changed from cephadm to cephadm/monitoring

#2 Updated by Sebastian Wagner about 1 year ago

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

#3 Updated by Sebastian Wagner 7 months ago

  • Related to Feature #45996: adopted prometheus instance uses port 9095, regardless of original port number added

#4 Updated by Sebastian Wagner 4 months ago

  • Related to Feature #48822: Add proper port management to mgr/cephadm added

#5 Updated by Sebastian Wagner 28 days ago

  • Duplicates Bug #50359: Configure the IP address for the monitoring stack components added

#6 Updated by Sebastian Wagner 28 days ago

  • Status changed from New to Duplicate

Also available in: Atom PDF