Meeting in the middle ground is a good strategy in life, but is it a good strategy for choosing an OpenStack® storage solution? When shopping for an OpenStack storage solution, you have to choose from these options:

  • Commodity storage solution
  • Vendor X with Cinder driver
  • Vendor Y with Cinder and Swift in two different namespaces
  • DDN with Cinder/Glance/Manila/Swift/HDFS from a single appliance (doing more with less)


Lessons Learned the Hard Way

Being a cloud architect for a public cloud provider a couple of years ago taught me how unpredictable both users and workload could be. Here are some lessons that can help in choosing your next OpenStack solution:

  1. Always choose a flexible storage appliance. Business requirements today can be only for hosting VMs, but this is the cloud. People are still figuring out how to use it. Build something for the future. Objects are the future, and we need to keep this in consideration.
  2. Make sure it’s been tested today at PB scale. Trust me: you don’t want to go with a vendor who provides 10TB and PB from the same solution. One size doesn’t fit all.
  3. Check that unified access is enabled. As I mentioned earlier, objects are the future, and unified access is the way to go. Learn more about how DDN unifies object and file workflows.
  4. Verify that it supports efficient analytics workload. Today, HDFS-capable storage is becoming a must in most data analytics workflows, so why not leverage the same storage solution to do data analytics? The most efficient and economical decision is the one that avoids the cost of moving data.

Clearly, many details are involved, but the main takeaway is that you need to go with a vendor who has been breathing performance for their whole life. Everything they do should be bigger and better than their competitors.

DDN gives it all to you with no need for compromises. To learn more, check out our OpenStack and Hadoop® solution pages, or if you are attending the next OpenStack Summit in Barcelona, click here to arrange for a time to meet.

  • Abdulrahman Alkhamees
  • Abdulrahman Alkhamees
  • Date: October 4, 2016