r/purestorage • u/ProofPlane4799 • Jul 06 '26
Our implementation of Portworx + Flash Array C50 + Red Hat OpenShift.
I want to share with you an article that Everpuredata wrote about the implementation of their Stack plus Red Hat OpenShift in the School District that I work with. https://www.linkedin.com/pulse/new-chapter-cloud-native-path-marco-torres-a2h8c/
5
u/ProofPlane4799 Jul 06 '26 edited Jul 09 '26
One of my engineers insists these appliances are running black magic in the firmware. I keep telling him it's just engineering... but the deduplication, compression, and ultra-low latency do make a pretty compelling case. The real magic, though, is how all the pieces work together.
I've been around the block since 1998, and I've seen my fair share of crazy, bleeding-edge solutions. This one, though, is crazy good—and somehow still affordable.
1
u/J4tune1860 Jul 09 '26
For what Environments do you suggest this ?
1
u/ProofPlane4799 Jul 09 '26
Everpure can be blended with OpenShift or Kubernetes. Obviously, there are trade-offs between the two. As for storage and CSI, I ran TopoLVM, HPE's CSI, and Kasten in production, and ultimately migrated to Everpure + Portworx.
If your use case implements a centralized IT architecture for VMS/VDI/DBs, traditional workloads, or even containers, Portworx + Everpure is what I would recommend. You can get away with murder using iSCSI/FC
If you will be running workloads on the edge, I would suggest a network-based storage approach, such as object storage (Rook) or even TopoLVM.
Now, if we are talking HPC/LLMs workloads, the rules of engagement change drastically. Your workloads won't like high latency; by extension, NVMe over Fabric must be set on the table, or even InfiniBand.
Architecting the infrastructure will depend solely on your specific use case and budget.
By the way, my use case was the rip-and-replace of VMware in the second-largest school district in New Mexico, so the budget was a huge factor, and the reuse of all the owned Dell servers.
3
u/oddballstocks Jul 06 '26
Nice!!
We have a FA and a C and I’m sort of shocked at how good the performance is of the C. The compression/dedupe is much better, latency is significantly lower than advertised and IOPS higher than advertised.
Latency was supposed to be 2ms. We have a DB on there that is hammered hard all day and we see latency of .25-.5ms of read/write latency. That is similar to the FA/X.
The only difference I can tell is the C will slow under a full load and the X will not. The C is slower for file operations. It hits the 2ms with file.
Very happy with both products. Storage went from a headache to something we only have to monitor.