Over the past decade advancements in microcode functionality for storage arrays have been impressive. Vendors add function and correct errors on installed arrays with frequent new versions of microcode, increasing the useful life of those systems. However before new releases of microcode can be applied to arrays attached to a virtualization engine, the combination of storage and virtualization engine must be certified as working correctly. Virtualization vendors must be careful to walk a fine line.
Often, certification of new microcode can take many months, bringing change management to a halt within IT storage infrastructures supported by the virtualization device. If this process extends out beyond 90 days, business is impacted in a meaningful way.
Sometimes virtualization vendors may invoke FUD (fear, uncertainty and doubt), arguing the best way to maintain data integrity is to stay within that vendor's product set, and delay certification of competitive arrays. This gamesmanship will not go away; however the bottom line is users want heterogeneity. As with other practices that damage business relationships, delaying new microcode release certification (deliberately or otherwise) will eventually backfire on the vendor.
Action Item: The demonstration of certification speed, transparency and quality will emerge as major points of differentiation. Vendors who put forth standards of certification, invest in managing certification cycles and do so in an expeditious manner will gain a leg up.
Footnotes:
