Bug 1926629

Summary: [RFE] Configure the IP address for the monitoring stack components
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Francesco Pantano <fpantano>
Component: CephadmAssignee: Adam King <adking>
Status: CLOSED ERRATA QA Contact: Rahul Lepakshi <rlepaksh>
Severity: high Docs Contact: Karen Norteman <knortema>
Priority: urgent    
Version: 5.0CC: almartin, ceph-eng-bugs, epuertat, fpantano, gfidente, johfulto, jolmomar, sangadi, vereddy
Target Milestone: ---Keywords: FutureFeature, RFE
Target Release: 5.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ceph-16.2.6-1.el8cp Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-04-04 10:19:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1820257, 1839169    

Description Francesco Pantano 2021-02-09 09:08:41 UTC
Description of problem:

When the dashboard is  deployed using cephadm, a monitoring stack (node_exporter, prometheus, alertmanager, grafana) can be applied to the cluster, resulting in multiple components deployed according the provided spec definition.
However, even though we're able to push a specific json config through cephadm, we need to be able to specify the ip address on the network the component belongs to, or the daemon will bind on *::<port>, which is a problem from a security point of view, preventing them to be deployed in the OpenStack context (both in standalone and HA config).
The Ceph Dashboard component already provides (via the mgr) a way to support multiple instances on different ip addresses [1], but this is not true for the other monitoring stack components.  
This represents a gap compared to ceph-ansible [2][3][4].

[1] https://docs.ceph.com/en/latest/mgr/dashboard/#host-name-and-port
[2] https://github.com/ceph/ceph-ansible/blob/master/roles/ceph-grafana/templates/grafana.ini.j2#L24
[3] https://github.com/ceph/ceph-ansible/blob/master/roles/ceph-prometheus/templates/prometheus.yml.j2
[4] https://github.com/ceph/ceph-ansible/blob/master/roles/ceph-prometheus/templates/alertmanager.yml.j2


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Ernesto Puerta 2021-03-02 13:29:27 UTC
*** Bug 1792902 has been marked as a duplicate of this bug. ***

Comment 3 Sebastian Wagner 2021-04-26 11:18:41 UTC
5.1 as discussed with Francesco

Comment 7 Sebastian Wagner 2021-06-10 12:19:46 UTC
*** Bug 1927716 has been marked as a duplicate of this bug. ***

Comment 16 errata-xmlrpc 2022-04-04 10:19:53 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: Red Hat Ceph Storage 5.1 Security, Enhancement, and Bug Fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:1174