Back to bug 2151189
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat One Jira (issues.redhat.com) | 2022-12-06 10:05:35 UTC | Link ID | Red Hat Issue Tracker RHCEPH-5742 | |
| Francesco Pantano | 2022-12-06 10:07:23 UTC | Link ID | Ceph Project Bug Tracker 58184 | |
| Francesco Pantano | 2022-12-06 10:20:39 UTC | CC | alfrgarc, gfidente, johfulto, ltoscano | |
| Francesco Pantano | 2022-12-06 10:36:44 UTC | Blocks | 2071977 | |
| Red Hat Bugzilla | 2023-01-01 05:37:32 UTC | Assignee | adking | nobody |
| Red Hat Bugzilla | 2023-01-01 08:29:02 UTC | Docs Contact | asriram | |
| Red Hat Bugzilla | 2023-01-01 08:37:33 UTC | QA Contact | msaini | |
| Alasdair Kergon | 2023-01-04 04:33:20 UTC | Assignee | nobody | adking |
| Alasdair Kergon | 2023-01-04 04:42:26 UTC | QA Contact | msaini | |
| James E. LaBarre | 2023-01-09 13:51:43 UTC | CC | jlabarre | |
| John Fulton | 2023-01-09 14:01:29 UTC | Link ID | Github ceph/ceph/pull/49555 | |
| Francesco Pantano | 2023-03-29 17:39:00 UTC | Status | NEW | POST |
| CC | adking | |||
| Flags | needinfo?(adking) | |||
| Adam King | 2023-03-29 18:34:20 UTC | Status | POST | ASSIGNED |
| Flags | needinfo?(adking) | |||
| Adam King | 2023-03-31 20:09:56 UTC | Depends On | 2180567 | |
| Ken Dreyer (Red Hat) | 2023-04-12 13:55:13 UTC | Status | ASSIGNED | MODIFIED |
| Fixed In Version | ceph-17.2.6-5.el9cp | |||
| Ken Dreyer (Red Hat) | 2023-04-12 13:55:57 UTC | Flags | needinfo?(vereddy) | |
| CC | vereddy | |||
| Veera Raghava Reddy | 2023-04-12 14:05:30 UTC | Flags | needinfo?(vereddy) | |
| errata-xmlrpc | 2023-04-12 14:08:03 UTC | Status | MODIFIED | ON_QA |
| Manisha Saini | 2023-04-26 20:07:44 UTC | Flags | needinfo?(adking) | |
| Adam King | 2023-04-26 20:12:40 UTC | Flags | needinfo?(adking) | |
| Manisha Saini | 2023-04-26 20:15:54 UTC | Status | ON_QA | VERIFIED |
| Akash Raj | 2023-05-03 06:23:49 UTC | Flags | needinfo?(adking) | |
| CC | akraj | |||
| Docs Contact | akraj | |||
| Adam King | 2023-05-03 18:31:11 UTC | Flags | needinfo?(adking) | |
| Doc Type | If docs needed, set a value | Enhancement | ||
| Doc Text | Feature: crush_device_class can now be specified per path inside an OSD spec. It is also supported to provide these per path crush_device_classes along with a service wide crush_device_class for the OSD service. In those cases the service wide setting will be considered a default and path specific settings will take priority. For example, this spec service_type: osd service_id: osd_using_paths placement: hosts: - Node01 - Node02 crush_device_class: hdd spec: data_devices: paths: - path: /dev/sdb crush_device_class: ssd - path: /dev/sdc crush_device_class: nvme - /dev/sdd db_devices: paths: - /dev/sde wal_devices: paths: - /dev/sdf would set the crush_device_class for an OSD deployed on /dev/sdb to ssd, the one on /dev/sdc would be set to nvme, and the one on /dev/sdd would get the default hdd defined in the service wide crush_device_class specified earlier in the spec before the paths. Reason: To allow users more flexibility with crush_device_class settings when deploying OSDs through cephadm. Result: Users can now specify per path crush_device_class settings when deploying OSDs using a spec file through cephadm. |
|||
| Akash Raj | 2023-05-08 02:35:43 UTC | Blocks | 2192813 | |
| Akash Raj | 2023-05-18 05:45:19 UTC | Doc Text | Feature: crush_device_class can now be specified per path inside an OSD spec. It is also supported to provide these per path crush_device_classes along with a service wide crush_device_class for the OSD service. In those cases the service wide setting will be considered a default and path specific settings will take priority. For example, this spec service_type: osd service_id: osd_using_paths placement: hosts: - Node01 - Node02 crush_device_class: hdd spec: data_devices: paths: - path: /dev/sdb crush_device_class: ssd - path: /dev/sdc crush_device_class: nvme - /dev/sdd db_devices: paths: - /dev/sde wal_devices: paths: - /dev/sdf would set the crush_device_class for an OSD deployed on /dev/sdb to ssd, the one on /dev/sdc would be set to nvme, and the one on /dev/sdd would get the default hdd defined in the service wide crush_device_class specified earlier in the spec before the paths. Reason: To allow users more flexibility with crush_device_class settings when deploying OSDs through cephadm. Result: Users can now specify per path crush_device_class settings when deploying OSDs using a spec file through cephadm. | .`crush_device_class` can now be specified per path in an OSD specification With this release, to allow users more flexibility with `crush_device_class` settings when deploying OSDs through Cephadm, `crush_device_class`, you can specify per path inside an OSD specification. It is also supported to provide these per-path `crush_device_classes` along with a service-wide `crush_device_class` for the OSD service. In cases of service-wide `crush_device_class`, the setting is considered as default, and the path-specified settings take priority. .Example ---- service_type: osd service_id: osd_using_paths placement: hosts: - Node01 - Node02 crush_device_class: hdd spec: data_devices: paths: - path: /dev/sdb crush_device_class: ssd - path: /dev/sdc crush_device_class: nvme - /dev/sdd db_devices: paths: - /dev/sde wal_devices: paths: - /dev/sdf ---- |
| errata-xmlrpc | 2023-06-15 09:08:15 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2023-06-15 09:16:25 UTC | Resolution | --- | ERRATA |
| Status | RELEASE_PENDING | CLOSED | ||
| Last Closed | 2023-06-15 09:16:25 UTC | |||
| errata-xmlrpc | 2023-06-15 09:17:10 UTC | Link ID | Red Hat Product Errata RHSA-2023:3623 |
Back to bug 2151189