Bug 2149533
| Summary: | [RFE - Stretch Cluster] Provide way for Cephadm orch to deploy new Monitor daemons with "crush_location" attribute | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Pawan <pdhiran> |
| Component: | Cephadm | Assignee: | Adam King <adking> |
| Status: | CLOSED ERRATA | QA Contact: | Vinayak Papnoi <vpapnoi> |
| Severity: | high | Docs Contact: | Akash Raj <akraj> |
| Priority: | unspecified | ||
| Version: | 5.3 | CC: | adking, akraj, cephqe-warriors, msaini, tserlin, vereddy |
| Target Milestone: | --- | ||
| Target Release: | 6.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ceph-17.2.6-31.el9cp | Doc Type: | Enhancement |
| Doc Text: |
.Users can set the crush location for a Ceph Monitor to replace tiebreaker monitors
With this release, users can set the crush location for a monitor deployed on a host. It should be assigned in the mon specification file.
.Example
----
service_type: mon
service_name: mon
placement:
hosts:
- host1
- host2
- host3
spec:
crush_locations:
host1:
- datacenter=a
host2:
- datacenter=b
- rack=2
host3:
- datacenter=a
----
This is primarily added to make the replacing of a tiebreaker monitor daemon in stretch clusters deployed by Cephadm, more feasible. Without this change, users would have to manually edit the files written by Cephadm to deploy the tiebreaker monitor, as the tiebreaker monitor is not allowed to join without declaring its crush location.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-06-15 09:16:25 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: | 2192813 | ||
|
Comment 13
errata-xmlrpc
2023-06-15 09:16:25 UTC
|