A major new feature in this release is its high availability (HA) capability. It is designed to allow no single point of failure –if a system crashes due to any reason, Eucalyptus 3 will immediately trigger a failover to a “hot spare” service that is running concurrently on a different physical machine. This information is then propagated internally to reflect the change while showing no signs of underlying failure to the external world.
“Implementing HA was the obvious next major evolution for Eucalyptus,” said Eucalyptus CEO Mårten Mickos in a blog post. “Originally, our project to develop HA was intended for a few customers who were asking for it early on. But as we dove deeper into the topic, it turned out that a majority of our users needed this feature.”
Eucalyptus 3 also features enhancements to its resource access controls (RAC), which allow admins to tune user group management, perform in-depth cost tracking, and benefit from detailed visibility of cloud usage throughout an enterprise. RAC features include implementation support for the Amazon Web Services (AWS) Identity and Access Management (IAM) API and new service-level management mechanisms. It can also automatically map identities from enterprise LDAP and Active Directory (AD) servers to Eucalyptus accounts, groups, and users. And it includes expanded account and resource reporting interfaces for integration with existing data center chargeback and billing systems.
Eucalyptus 3 also includes cloud storage resource and platform enhancements, such as: Boot from EBS, NetAPP and JBOD SAN drivers, and support for VMware 4.1, RHEL 6.0 and KVM.
The HA capabilities of Eucalyptus may be able to keep this open source option in a competitive position against other IaaS offerings. But, how much demand is out there? Does a HA mechanism make you consider implementing private cloud more than before? If you’ve implemented a private cloud, would you upgrade to Eucalyptus 3 because of this feature?]]>