Bug 1415779
Summary: | [RFE] Support for Intel iCAS | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Neil Levine <nlevine> |
Component: | Ceph-Installer | Assignee: | Andrew Schoen <aschoen> |
Status: | CLOSED NOTABUG | QA Contact: | Tejas <tchandra> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 2.2 | CC: | adeza, agk, aschoen, ceph-eng-bugs, dmick, gmeno, hnallurv, nthomas, sankarshan, seb |
Target Milestone: | rc | Keywords: | FutureFeature |
Target Release: | 3.* | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-08-21 14:10:38 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: |
Description
Neil Levine
2017-01-23 17:13:52 UTC
Good news! per dgallowa According to the "Product and Performance Information" portion on https://www-ssl.intel.com/content/www/us/en/software/intel-cache-acceleration-software-performance.html , they used Intel P3700s to use for benchmarking. All the smithi have that exact model SSD in them. would you please break this RFE into smaller bits with Seb? FWIW ceph-disk does not provision devices, it formats pre-existing block devices for Ceph. The creation of the block device itself is outside of the scope of ceph-disk. In other words, as long as ceph-ansible knows how to provision the block device, it can be used as an argument to ceph-disk with no modification. Harish we moved it FWIW, looked briefly at this today. It uses a custom utility to associate an SSD/NVMe device with a traditional block device, and creates a new block device "/dev/intelcasN-M" to use as the cached device path. Is there an error when running ceph-disk prepare /dev/intelcasN-M ? I've no idea. I haven't actually run any code. Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. Regards, Giri Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. Regards, Giri Level setting the severity of this defect to "Low" with a bulk update. Pls refine it to a more closure value, as defined by the severity definition in https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity |