OCI engineering is working on developing Pure Storage support for OCI. We are always interested in discovering as many configurations as early as possible to refine our approach.
We are at the point where we have what we call a standalone datasource - basically, a Windows batch script that calls enough Java code to collect data from a device (in this case, via Pure's REST API), and build a zip file
If you are interesting in helping us move this project along by running this read only tool, ping me at ostiguy at netapp dot com.
There is a lot of overhead for us to run a beta datasource on multiple OCI versions (OCI 7.0.x and 7.1.x as examples), so we try to avoid it. Adding to that is our intent to do performance support shortly. Right now, I don't think we have plans to port this to 7.0.x, but I think if we were to, we'd want to wait until both Inventory and Perform support were fairly mature.
FYI, we have been steadily making progress, and we have inventory and performance support for Pure available as a beta patch for OCI 7.1.x.
Pure's REST API for performance is somewhat thin - mainly volume stats, and storage level stats, so nothing currently for disk or node statistics.
On the inventory side, we are pretty much there - we have customers seeing paths, as mapping and masking is good. Thin provisioning numbers look solid. Storage alias reporting is implemented for auto resoluton of hosts.
This is 97% of what you should see with the current Pure support in OCI, and as it will ship in the next OCI 7.1.x maintenance release and data source service pack.
This is a scrubbed screenshot, but it shows a bug where the array throughput numbers are preposterous - we were reporting bytes per sec as MBps, thus the ludicrous throughput. This bug has been fixed.
From a performance standpoint, we are only able to get volume and some array level stats - no disk stats, and no controller utilization stats.
This is a REST API datasource - OCI just needs read only credentials, and HTTPS connectivity to the array - create one datasource per Pure array. Honestly, we haven't really run into an Pure array yet we don't support - we have seen a mix of 4.0.x through 4.5.x firmware work.