Eucalyptus 3.0 Advances Private Cloud Availability
As cloud deployments continue to grow, so too are the requirements for high availability and stability. That's the direction that open source private cloud vendor Eucalyptus is headed with their new 3.0 release.
- Navigating Your IT Career
- Exploring the Private Cloud for Your Organization
- IT Manager's Guide to Social Networking
"We really feel that this is a big step forward in terms of the mission criticality of the applications running in the cloud and being able to serve the most demanding requirements," Marten Mickos, CEO of Eucalyptus told InternetNews.com.
Mickos explained that in Eucalyptus 3.0 there are now multiple controllers for high-availability. The controllers are web services that help to orchestrate the real time operation of a Eucalyptus cloud.
In terms of deployment, Mickos said that there are a lot of configuration options for high-availability in Eucalyptus 3.0. Deployments can me made across two or more racks with separate controllers on each. The high-availability feature will detect networking, compute, memory and hardware failures and then fail-over to a working stable node.
"You don't need to double the entire Eucalyptus installation, what you're doubling are the the high-availability controllers in the installation," Mickos said. "Eucalpytus as a product is a set of web services and we're applying high-availability to the mission critical part of those web services."
High-availability is limited however by distance and is not a solution for geographically separated cloud deployments.
"That's a goal for the future," Mickos said. "But when you're doing fail-over longer distances that's disaster recovery and the distance introduces latency, which isn't good for high-availability."
Mickos added that high-availability on Eucalyptus 3.0 works instantly without noticeable delay.
In addition to high-availability are improved resource management capabilities for setting quotes and limits on cloud assets. The Eucalyptus system does not however have an auto-scaling feature, though Mickos added that is a roadmap item for future releases.
In addition to the technical changes in Eucalyptus 3.0, the new release is also part of the Eucalyptus' new model for licensing. In 2009, Eucalyptus added a commercial version to their product lineup. The commercial version was not open source. With Eucalptyus 3.0, Mickos explained that there is now only one branch of Eucalyptus development and it's open source.
Mickos said that there is now just the Eucalyptus Cloud Platform and for paying customers there are some additional plugins that are available under commercial license. Those additional plugins include the ability to run a VMware ESX server as part of a Eucalytpus cloud deployment.
"The change speeds up our development pace and we can now come out with releases faster than we've done before," Mickos said. "We're also making sure that the product is very plugin friendly."
Moving forward, Mickos said that there will be a version 3.1 and 3.2 for Eucalyptus and there is a robust roadmap of features still to come, including autoscaling and usability improvements.