SolidFire recently announced the debut of two SDKs that facilitate integrating products with our storage technology.
I’ve been the Senior CloudStack Developer at SolidFire for four years now — focusing exclusively on Apache CloudStack and enabling it to deliver many of the benefits offered by SolidFire.
Once the Java and Python versions of the SolidFire SDK were getting close to “hitting the street,” I decided to spend a bit of time analyzing what it would take to replace the limited ad-hoc SolidFire SDKs I had been using in CloudStack with their full-blown, more powerful counterparts.
As a bit of background, CloudStack makes use of the Java programming language for production code and leverages Python for integration tests.
Since I have been writing code for CloudStack for several years now, I began to wonder what kind of an effort I should expect when it came to migrating to the new SDKs.
With regard to Java, I was pleasantly surprised that I was able to remove hundreds of lines of code that I had custom written. I replaced them with simpler lines, enabled by the SDK, that did not require that I personally handle the low-level details of interacting with the storage system’s REST-based interface.
There’s commonly a lot of detail involved in adding features to CloudStack in and of themselves, so it’s always nice to be able to remove some of the complexity from that codebase (and depend upon that complexity being handled properly by another component that you do not have to maintain).
In this situation, I migrated from an ad-hoc SDK that did not cover the entire breadth of functionality of the SolidFire system to one that covered all aspects of the API and hid its complexity from CloudStack.
Similarly, I successfully moved to the SolidFire SDK for Python for my CloudStack integration tests.
I recommend you take a look at the SolidFire SDKs (available currently for Python, Java, and C#.Net) whenever you have a need to integrate with our platform. They provide easy-to-use interfaces as well as enabling you to access and automate all aspects of your SolidFire cluster more quickly and efficiently than using SolidFire’s simple REST-based interface directly.