Federation/Distributed Capacity has merit for specific types of workloads. It will be interesting to see the relationship of the type of content vs. performance.
Originally posted on Gigaom:
OnApp is one of the most interesting European cloud players, as it offers traditional hosting providers a way to fight Amazon(s amzn) by federating the spare capacity in their data centers — it also has more than 500 of these providers as customers around the world, so this is a serious endeavor. Now the company has launched version 3 of the OnApp Cloud platform, taking its distributed storage piece out of beta, improving its content delivery network offering and adding support for VMware hypervisors.
The VMware(s vmw) support is a big deal for OnApp as it helps the company’s service-provider customers better target the enterprise (OnApp already supported Xen and KVM hypervisors, and still intends to support Hyper-V). A new feature called Cloud Boot was introduced to automate the deployment of hypervisors, and there’s a new support console for cloud administrators and end users too.
But it’s the OnApp Storage piece that is particularly critical for the company, Kosten Metreweli, OnApp’s chief commercial officer, told me. This is partly because it solves performance problems for providers, but also because it lays the foundation for OnApp’s upcoming federated compute play.