All the sub-directories were the same, only the above two files were added in the HP one.
I believe quite strongly that you can use the HP firmwares to upgrade Brocade switches that are branded by other vendors.
As they are using the very same Brocade firmware that Brocade themself use, it might be hard for the vendors to change the switch that much.
It would be interesting to investigate if other vendors add something to make theirs not, but I have no way of acquiring such a firmware.
The EULA looks like a normal HP standard end user license agreement form. The HP ancillary.txt file contains this:
“This ancillary.txt file provides information as to how to obtain the open source or other third party licenses in this distribution. To obtain such licenses, run the following CLI command at the prompt, “opensource”.
This ancillary.txt file also provides the instructions for customers who require a copy of the
machine-readable GPL Source Code by written request. Upon your written request, HP will provide to You, for a fee covering the cost of distribution, a complete machine-readable copy of the GPL Source Code. Your written request for GPL Source Code can be sent via email to FC_Infrastructure_OpenSourceRequest@hp.com. In the request, include product name, version number, your name, and your shipping address. “
I really liked a post by the storage anarchist as it quite eloquently explains what is happening and a great benefit of VAAI. Granted the post primarily speaks about the eraze part and I’m not that knowledgeable about VAAI itself to tell if there are any other features – but there is – at least according to this article on vmetc.com. This does not focus on the same two features that the anarchist mentioned. Maybe the storage anarchist did not want to mention all of these other features because they actually do work quite well for arrays that are behind the VSP.