6 posts • joined 8 Jul 2013
Do you think those CPUs in storage arrays are there just to help keep the HBAs cozy and warm? It takes compute power to run a real array and host IO directed at it and probably more so for a virtual array. There's no free lunch! You'll have to take your existing compute needs and then add the storage load onto that. You aren't going to be able to squeeze VSAN into an already fully loaded compute farm. You can try, but you'd better have your resume freshened up first or a forgiving manager with the Dell rep's number on speed dial.
Re: Dynamic provisioning
The majority of companies have similar daily/weekly io usage patterns. The cloud providers have to build based on peak usage. A bit like highways. Not everyone works 8-5 but enough do that the highways are built to accommodate that. You'll be paying for cloud providers to overbuild as well. Just like the rest of the IT world does. No free lunches.
Need another source
Big players in storage generally require dual sources for drives. Until another 2.5inch 600g 15k rpm drive comes around from another source I don't expect to see a shelf of them on many vendors' price lists.
Re: Am i the only one
Maybe it's not your age. The CRTs have all disappeared. :)
Re: what, more hardware on a monolithic processing scheme?
You are apparently misinformed. NetApp has been breaking out processes from Kahuna for years to get better use of cores. In my experience, almost every 8.x release has been a bit better in utilizing cores. Perhaps you're thinking of VNX2 which finally uses those multicore procs unlike the VNX they sold people as recently as August.
NetApp has had synchronous replication for years in 7-mode.
This sounds like it will make it easier for EMC's frenemy Cisco to bring the EMC stack further into Cloupia. Why would you want to automate the storage stack when you can bring it into the whole stack? I also heard mention of management but what of measurement and reporting? Will performance and reporting APIs for EMCs wide array of products be exposed so third parties won't need a proxy?
I get there's the file/object aspect of ViPR but that might be exposed by Openstack anyway won't it? It seems like EMC saw itself being painted into a corner with their many closed APIs and figured they'd have to open up to play in the new private cloud datacenter so they might as well productize it. Hence ViPR.
Everyone else who isn't already open with their APIs is probably thinking the same thing but EMC likes to pre-announce products far ahead of reality so they look visionary.