Feature #48822
closed
Add proper port management to mgr/cephadm
Added by Sebastian Wagner over 3 years ago.
Updated about 3 years ago.
Description
When thinking about co-locating daemons, we also have to think about the ports used by daemons:
- Automatically change ports, when deploying daemons? (MONs?)
- Prevent port conflicts in the scheduler (RGW)
- Expose which ports are used by which daemon in the orch CLI
- Allow co-location, if we don't have conflicts?
- Blocks Feature #47145: cephadm: Multiple daemons of the same service on single host added
cat montioring.yaml
service_type: prometheus
placement:
hosts:
- label: monitoring
---
service_type: node-exporter
---
service_type: alertmanager
placement:
hosts:
label: monitoring
---
service_type: grafana
placement:
hosts:
label: monitoring
ceph orch apply -i monitoring.yaml
Juan Miguel, do you need anything else?
- Blocks Feature #45996: adopted prometheus instance uses port 9095, regardless of original port number added
- Related to Feature #45652: cephadm: Allow user to select monitoring stack ports added
- Related to Feature #45876: cephadm: handle port conflicts gracefully added
- Status changed from New to Fix Under Review
- Assignee set to Sage Weil
- Pull request ID set to 39931
- Status changed from Fix Under Review to Closed
Also available in: Atom
PDF