This somewhat belated blog post is meant to clarify the past, present, and future development of the IBM Storage Driver for OpenStack. For over 4 years, ever since the OpenStack Folsom release (when Cinder was still part of Nova), IBM Storage Driver for OpenStack has been released by IBM to support the integration of IBM XIV and IBM DS8000 storage systems with OpenStack cloud environments. In parallel, the IBM SAN Volume Controller, IBM Storwize Family, and IBM FlashSystem V9000 storage systems were already included in the OpenStack community source code. Throughout this period, the IBM XIV and IBM DS8000 storage driver remained proprietary. However, as community standards called for opening the driver source code, a decision to incorporate the driver into the community code has been made.
We decided to take the dive into the open-source code in version 2.0.0 of IBM Storage Driver for OpenStack, aiming to include IBM FlashSystem A9000 and A9000R, IBM XIV, IBM Spectrum Accelerate (deployable software), and IBM DS8000 Family systems in the community source code for the OpenStack Ocata release.
The journey of opening the code has been a unique one, as most drivers start as open, and do not evolve from a closed source code. But the challenge was met, and, as we are actually nearing the next release of version 2.1.0, we can make a full use of countless benefits of any open source software. Among them are:
- Security, with multiple reviewers scanning the code, testing it, finding and fixing problems.
- Dynamic development environment, offering powerful code collaboration platforms, such as Gerrit and testing tools, such as Tox.
- Flexibility, allowing the users modify the software to fit their needs.
- Interoperability, breaking the boundaries of proprietary data formats.
- Robust support system with passionate communities of users and developers, providing excellent forums, mailing lists, wikis, documentation etc.
- Documentation available on the OpenStack website, rather than on IBM Knowledge Center.
Stay tuned for our next blog post when the community-based version 2.1.0 is released.
If you are looking for the driver’s up-to-date compatibility matrix, you can find it here.