Back to bug 2053709
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat One Jira (issues.redhat.com) | 2022-02-11 19:43:42 UTC | Link ID | Red Hat Issue Tracker RHCEPH-3168 | |
| Red Hat One Jira (issues.redhat.com) | 2022-02-11 19:43:47 UTC | Link ID | Red Hat Issue Tracker RHCSDASH-668 | |
| Sunil Angadi | 2022-03-11 07:31:52 UTC | Severity | medium | high |
| Ernesto Puerta | 2022-04-25 10:34:17 UTC | Keywords | RFE | |
| Ernesto Puerta | 2022-05-04 15:16:57 UTC | Assignee | epuertat | nia |
| Status | NEW | POST | ||
| Link ID | Github ceph/ceph/pull/45116 | |||
| Red Hat Bugzilla | 2022-05-26 08:30:15 UTC | CC | ceph-qe-bugs | |
| Sunil Angadi | 2022-05-31 09:11:22 UTC | CC | nia | |
| Flags | needinfo?(nia) | |||
| Nizamudeen | 2022-05-31 09:28:05 UTC | Flags | needinfo?(nia) | |
| Nizamudeen | 2022-06-01 09:58:53 UTC | CC | tserlin | |
| Flags | needinfo?(nia) | |||
| Flags | needinfo?(nia) | |||
| errata-xmlrpc | 2022-06-17 23:02:13 UTC | Status | POST | MODIFIED |
| Fixed In Version | ceph-16.2.8-50.el8cp | |||
| Status | MODIFIED | ON_QA | ||
| Akash Raj | 2022-07-06 08:10:03 UTC | Fixed In Version | ceph-16.2.8-50.el8cp | ceph-16.2.8-58.el8cp |
| Status | ON_QA | MODIFIED | ||
| Status | MODIFIED | ON_QA | ||
| CC | skanta | |||
| QA Contact | sangadi | skanta | ||
| Depends On | 2101680 | |||
| Depends On | 2102549 | |||
| Status | ON_QA | ASSIGNED | ||
| CC | akraj | |||
| Blocks | 2102272 | |||
| Docs Contact | asriram | akraj | ||
| Flags | needinfo?(nia) | |||
| Ernesto Puerta | 2022-07-06 14:34:56 UTC | Status | ASSIGNED | POST |
| Nizamudeen | 2022-07-06 14:54:22 UTC | Flags | needinfo?(nia) | |
| Nizamudeen | 2022-07-06 14:55:56 UTC | Flags | needinfo?(skanta) needinfo?(sangadi) | |
| CC | sangadi | |||
| Status | POST | MODIFIED | ||
| Sunil Angadi | 2022-07-07 06:23:07 UTC | Fixed In Version | ceph-16.2.8-58.el8cp | ceph-16.2.8-68.el8cp |
| Status | MODIFIED | ON_QA | ||
| Status | ON_QA | VERIFIED | ||
| Flags | needinfo?(skanta) | |||
| Flags | needinfo?(akraj) | |||
| Flags | needinfo?(sangadi) | needinfo+ | ||
| Nizamudeen | 2022-07-07 06:45:01 UTC | Doc Text | Feature: Introducing Simple and Advanced mode for OSD Creation form Reason: To simplify osd deployment for the clusters with a more simpler deployment scenarios Result: Introduced three new options. 1. Cost/Capacity-optimized: All the available HDDs will be used to deploy OSDs. 2. Throughput-optimized: We support HDDs for data devices and SSDs for DB/WAL devices. 3. IOPS-optimized: All the available NVMEs will be used as data devices. | |
| Doc Type | If docs needed, set a value | Enhancement | ||
| Akash Raj | 2022-07-13 05:54:39 UTC | Flags | needinfo?(akraj) | |
| Akash Raj | 2022-07-14 03:30:31 UTC | Doc Text | Feature: Introducing Simple and Advanced mode for OSD Creation form Reason: To simplify osd deployment for the clusters with a more simpler deployment scenarios Result: Introduced three new options. 1. Cost/Capacity-optimized: All the available HDDs will be used to deploy OSDs. 2. Throughput-optimized: We support HDDs for data devices and SSDs for DB/WAL devices. 3. IOPS-optimized: All the available NVMEs will be used as data devices. | .User can now create OSDs in simple and advanced mode on the {storage-product} Dashboard With this release, to simplify OSD deployment for the clusters with simpler deployment scenarios, “Simple” and “Advanced” modes for OSD Creation are introduced. You can now choose from 3 new options: Cost/Capacity-optimized: All the available HDDs are used to deploy OSDs. Throughput-optimized: HDDs are supported for data devices and SSDs for DB/WAL devices. IOPS-optimized: All the available NVMEs are used as data devices. |
| Akash Raj | 2022-07-18 12:17:52 UTC | Doc Text | .User can now create OSDs in simple and advanced mode on the {storage-product} Dashboard With this release, to simplify OSD deployment for the clusters with simpler deployment scenarios, “Simple” and “Advanced” modes for OSD Creation are introduced. You can now choose from 3 new options: Cost/Capacity-optimized: All the available HDDs are used to deploy OSDs. Throughput-optimized: HDDs are supported for data devices and SSDs for DB/WAL devices. IOPS-optimized: All the available NVMEs are used as data devices. | .User can now create OSDs in simple and advanced mode on the {storage-product} Dashboard With this release, to simplify OSD deployment for the clusters with simpler deployment scenarios, “Simple” and “Advanced” modes for OSD Creation are introduced. You can now choose from 3 new options: Cost/Capacity-optimized: All the available HDDs are used to deploy OSDs. Throughput-optimized: HDDs are supported for data devices and SSDs for DB/WAL devices. IOPS-optimized: All the available NVMEs are used as data devices. See link:{operations-guide}#management-of-osds-using-the-ceph-orchestrator[_Management of OSDs using the Ceph Orchestrator_] for more details. |
| Akash Raj | 2022-08-09 07:55:24 UTC | Group | redhat | |
| Doc Text | .User can now create OSDs in simple and advanced mode on the {storage-product} Dashboard With this release, to simplify OSD deployment for the clusters with simpler deployment scenarios, “Simple” and “Advanced” modes for OSD Creation are introduced. You can now choose from 3 new options: Cost/Capacity-optimized: All the available HDDs are used to deploy OSDs. Throughput-optimized: HDDs are supported for data devices and SSDs for DB/WAL devices. IOPS-optimized: All the available NVMEs are used as data devices. See link:{operations-guide}#management-of-osds-using-the-ceph-orchestrator[_Management of OSDs using the Ceph Orchestrator_] for more details. | .User can now create OSDs in simple and advanced mode on the {storage-product} Dashboard With this release, to simplify OSD deployment for the clusters with simpler deployment scenarios, “Simple” and “Advanced” modes for OSD Creation are introduced. You can now choose from 3 new options: * Cost/Capacity-optimized: All the available HDDs are used to deploy OSDs. * Throughput-optimized: HDDs are supported for data devices and SSDs for DB/WAL devices. * IOPS-optimized: All the available NVMEs are used as data devices. See link:{operations-guide}#management-of-osds-using-the-ceph-orchestrator[_Management of OSDs using the Ceph Orchestrator_] for more details. |
||
| errata-xmlrpc | 2022-08-09 09:57:24 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2022-08-09 17:37:28 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2022-08-09 17:37:28 UTC | |||
| errata-xmlrpc | 2022-08-09 17:38:03 UTC | Link ID | Red Hat Product Errata RHSA-2022:5997 |
Back to bug 2053709