A distributed and scalable cloud

HP Helion Eucalyptus is highly scalable because of its distributed nature. The cloud level of the computing architecture is comprised of only two components and while used by many users, the transactions at each component are typically small. The node level may have many components, but each component only supports a few users, even though the transactions are larger. This distributed cloud architecture is flexible enough to support businesses of any size.

HP Helion Eucalyptus architecture diagram

HP Helion Eucalyptus components

Cloud components

HP Helion Eucalyptus is made up of five distinct components that can be distributed in various cloud computing architectures. The five components are grouped into three separate levels.

Cloud level

Cloud Controller (CLC)

The Cloud Controller (CLC) is a Java program that offers EC2-compatible SOAP and Query interfaces, as well as a Web interface to the outside world, for distribution within the cloud architecture. In addition to handling incoming requests, the CLC acts as the administrative interface for cloud management and performs high-level resource scheduling and system accounting. The CLC accepts user API requests from command-line interfaces like euca2ools or GUI-based tools like the Management Console and manages the underlying compute, storage, and network resources. Only one CLC can exist per cloud.

The CLC handles high-level:

  • Authentication
  • Accounting
  • Reporting
  • Quota management

Scalable Object Storage (SOS)

Scalable Object Storage (SOS) is the equivalent to AWS Simple Storage Service (S3). The SOS is pluggable service that allows infrastructure administrators the flexibility to implement scale-out storage on top of commodity resources using open source and commercial solutions that implement the S3 interface. HP Helion Eucalyptus provides a basic storage implementation, known as Walrus, which may suit evaluation and smaller cloud deployments. For large-scale and increased performance, users are encouraged to connect the SOS to dedicated storage solutions such as RiakCS or supported SAN devices.

Cluster level

Cluster Controller (CC)

A cluster is equivalent to an AWS availability zone, and a single HP Helion Eucalyptus cloud can have multiple clusters. The Cluster Controller (CC) acts as the front end for a cluster within an HP Helion Eucalyptus cloud and communicates with the Storage Controller (SC) and Node Controller (NC). The CC manages instance (i.e., virtual machines) execution and Service Level Agreements (SLAs) per cluster.

Storage Controller (SC)

The Storage Controller (SC) is equivalent to AWS Elastic Block Store (EBS). The SC communicates with the Cluster Controller (CC) and Node Controller (NC) within the distributed cloud architecture and manages block volumes and snapshots to the instances within its specific cluster. If an instance requires writing persistent data to memory outside of the cluster, it would need to write to the backend storage, which is available to any instance in any cluster. The SC interfaces with storage systems, including local, NFS, iSCSI, and SAN.

Node level

Node Controller (NC)

The Node Controller (NC) is part of the Node level of the cloud computing architecture. It hosts the virtual machine instances and manages the virtual network endpoints. The NC downloads and caches images from Scalable Object Storage as well as creates and caches instances.