Re: What about Blade Servers?
IP based storage (f.e NFS) never had anything to do with FCOE. It was legitimate before, it is legitimate now and it has a different use case.
You use IP based storage when you want fine grained file based access as well as large amounts of data shared as read-write between multiple compute endpoints as files. It can be used in some cases where dedicated per-endpoint storage is needed and can even deliver higher cost efficiency. However, it requires significantly more qualified sysadmin workforce when used this way. In the days when I still ran IT, you used to get < 5% of candidates having a basic understanding of how to use NFS on a Unix system and < 1% knowing advanced stuff like autofs. In any case - FCOE does not apply here. It has nothing to do with the requirements and it does not implement anything from what you would need to deliver this use case.
FCOE (and FC proper for that matter) as well as other block storage use case have little or no sharing between endpoints with VM images being a prime example. When you instantiate a VM image you do not have 20 systems in need of read-write access to it. Even if you use Copy-On-Write you still have a strict read-only master and separate journal for each VM.
The article the way it is written makes conjectures based on failure of protocols and solutions designed for use case A to do use case B and vice versa. Surprise, surprise, a round peg failed to fit in a square hole. Of course it will not. However, based on the fact that it will not you cannot declare the peg dead or the hole dead.