Comment 4 for bug 1499334

@Thomas,

Got ya, thanks! To be honest, the bottom line is that regardless if there are legal issues or not, OpenStack has always made a point of fully open-source, NOT just the components in tree; everything about it.

This introduces a confusing case that goes against that philosophy. It also introduces a case where as you say it's a regression because we go from being full open source to now having a component that is proprietary. Seems like a step in the wrong direction IMHO.

The trick is that even though that patch was landed late in the cycle, it seems there were quite a few changes during feature freeze, so the revert is a bit of mess in terms of merge-conflicts, making things slightly more difficult unless we just remove the NetApp drivers altogether which I certainly don't like the idea of doing.

I've asked some folks from NetApp to take a look at fixing up the merge conflicts, we'll see what happens.