iCAS is a disk caching technology provided by Intel for free to all users who buy their SSDs. It can create a partition on a local SSD to be used as a cache for OSDs.
The iCAS managemnt tool is proprietary but the driver itself is under the GPL.
To support the feature, we need to:
* expose options that the user defines via ceph-ansible
* enable ceph-disk to provision the caching device with relevant flags
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.
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