Back to bug 2184761
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat One Jira (issues.redhat.com) | 2023-04-05 16:08:13 UTC | Link ID | Red Hat Issue Tracker RHCEPH-6384 | |
| Adam King | 2023-04-05 17:18:09 UTC | Flags | needinfo? | |
| Status | NEW | ASSIGNED | ||
| Geo Jose | 2023-04-07 15:49:25 UTC | CC | gjose | |
| Shravan Kumar Tiwari | 2023-04-14 12:24:57 UTC | Flags | needinfo?(adking) | |
| CC | adking, shtiwari | |||
| Adam King | 2023-04-14 12:58:29 UTC | Flags | needinfo?(adking) | |
| Veera Raghava Reddy | 2023-04-26 15:15:05 UTC | CC | vereddy | |
| Adam King | 2023-04-28 16:23:12 UTC | Status | ASSIGNED | POST |
| errata-xmlrpc | 2023-05-01 02:45:55 UTC | Status | POST | MODIFIED |
| Fixed In Version | ceph-16.2.10-169.el8cp | |||
| CC | tserlin | |||
| Status | MODIFIED | ON_QA | ||
| Mohit Bisht | 2023-05-11 08:52:58 UTC | Status | ON_QA | VERIFIED |
| Ranjini M N | 2023-05-17 12:10:40 UTC | Docs Contact | lysanche | |
| Flags | needinfo?(adking) | |||
| CC | rmandyam | |||
| Adam King | 2023-05-17 13:40:04 UTC | Doc Type | If docs needed, set a value | Enhancement |
| Flags | needinfo?(adking) | |||
| Doc Text | Feature: Users can set the crush_device_class in an OSD spec, which will get cephadm to mark all OSDs created based off of that spec as being that crush device class Reason: Previously, users would manually have to set the crush device class after the OSDs are made. This should allow streamlining the process. Result: The crush_device_class can now be set in an OSD spec. That looks like service_type: osd service_id: osd_with_crush_device_class placement: hosts: - Node01 - Node02 crush_device_class: ssd spec: data_devices: paths: - <block devices> db_devices: paths: - <db-devices> wal_devices: paths: - <wal-devices> which would set all the OSDs created based on that spec to have crush device class "ssd" |
|||
| Ranjini M N | 2023-05-19 07:10:58 UTC | Blocks | 2203283 | |
| Ranjini M N | 2023-05-19 11:47:55 UTC | Doc Text | Feature: Users can set the crush_device_class in an OSD spec, which will get cephadm to mark all OSDs created based off of that spec as being that crush device class Reason: Previously, users would manually have to set the crush device class after the OSDs are made. This should allow streamlining the process. Result: The crush_device_class can now be set in an OSD spec. That looks like service_type: osd service_id: osd_with_crush_device_class placement: hosts: - Node01 - Node02 crush_device_class: ssd spec: data_devices: paths: - <block devices> db_devices: paths: - <db-devices> wal_devices: paths: - <wal-devices> which would set all the OSDs created based on that spec to have crush device class "ssd" | .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_ ---- |
| errata-xmlrpc | 2023-05-23 00:01:44 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2023-05-23 00:19:10 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2023-05-23 00:19:10 UTC | |||
| errata-xmlrpc | 2023-05-23 00:19:46 UTC | Link ID | Red Hat Product Errata RHBA-2023:3259 |
Back to bug 2184761