Browse Source

Expose the monitoring_stack network to cephadm

cephadm accepts a network parameter, which is used by the rendered spec
to identify the network address block used to deploy a given daemon.
This patch just exposes (like we've done for RGW and Ganesha) the
network where the monitoring stack components (node-exporter, prometheus
and alertmanager) should be bound.

Depends-On: I59a74797dc97540b7553a3e74f67e23e6ccc8f6d
Change-Id: Icc779d7d2608e5a8c1fbc68973a987a9c268244d
(cherry picked from commit 5369ff9bde)
changes/90/793690/1
Francesco Pantano 1 month ago
parent
commit
42f59769fe
1 changed files with 5 additions and 0 deletions
  1. +5
    -0
      deployment/cephadm/ceph-grafana.yaml

+ 5
- 0
deployment/cephadm/ceph-grafana.yaml View File

@ -114,6 +114,11 @@ resources:
tripleo_cephadm_node_exporter_container_image: {get_param: NodeExporterContainerImage}
tripleo_cephadm_prometheus_port: 9092
tripleo_cephadm_alertmanager_container_image: {get_param: AlertManagerContainerImage}
tripleo_cephadm_monitoring_address_block:
list_join:
- ','
- get_param: [ServiceData, net_cidr_map, {get_param: [ServiceNetMap, CephGrafanaNetwork]}]
outputs:
role_data:


Loading…
Cancel
Save