Bug 2184761
| Summary: | [cee/sd][cephadm] addition of osd spec crush_device_class feature | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Milind <milverma> |
| Component: | Cephadm | Assignee: | Adam King <adking> |
| Status: | CLOSED ERRATA | QA Contact: | Mohit Bisht <mobisht> |
| Severity: | medium | Docs Contact: | lysanche |
| Priority: | unspecified | ||
| Version: | 5.3 | CC: | adking, cephqe-warriors, gjose, rmandyam, shtiwari, tserlin, vereddy |
| Target Milestone: | --- | ||
| Target Release: | 5.3z3 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | ceph-16.2.10-169.el8cp | Doc Type: | Enhancement |
| Doc Text: |
.Users can now set `crush_device_class` in OSD specification
Previously, users would manually set the `crushdevice_class` after the OSDs were made.
With this release, users can set the `crush_device_class` in an OSD specification, which gets `cephadm` to mark all OSDs created based on that specification as being that crush device class.
.Syntax
[source,subs="verbatim,quotes"]
----
service_type: osd
service_id: _SERVICE_ID_OF_OSD_
placement:
hosts:
- _HOSTNAME_01_
- _HOSTNAME_01_
crush_device_class: _CRUSH_DEVICE_CLASS_(SSD/HDD)
spec:
data_devices:
paths:
- _DATA_DEVICES_
db_devices:
paths:
- _DB_DEVICES_
wal_devices:
paths:
- _WAL_DEVICES_
----
|
Story Points: | --- |
| Clone Of: | 2124441 | Environment: | |
| Last Closed: | 2023-05-23 00:19:10 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: | 2203283 | ||
|
Description
Milind
2023-04-05 16:06:45 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 (Red Hat Ceph Storage 5.3 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/RHBA-2023:3259 |