Eucalyptus (computing)

Eucalyptus is a paid and open-source computer software for building Amazon Web Services (AWS)-compatible private and hybrid cloud computing environments, originally developed by the company Eucalyptus Systems. Eucalyptus is an acronym for Elastic Utility Computing Architecture for Linking Your Programs To Useful Systems. Eucalyptus enables pooling compute, storage, and network resources that can be dynamically scaled up or down as application workloads change. Mårten Mickos was the CEO of Eucalyptus. In September 2014, Eucalyptus was acquired by Hewlett-Packard and then maintained by DXC Technology. After DXC stopped developing the product in late 2017, AppScale Systems forked the code and started supporting Eucalyptus customers.

History

The software development had its roots in the Virtual Grid Application Development Software project, at Rice University and other institutions from 2003 to 2008.
Rich Wolski led a group at the University of California, Santa Barbara (UCSB), and became the chief technical officer at the company headquartered in Goleta, California before returning to teach at UCSB.

Eucalyptus software was included in the Ubuntu 9.04 distribution in 2009.
The company was formed in 2009 with $5.5 million in funding by Benchmark Capital to commercialize the software.

The co-founders of Eucalyptus were Rich Wolski (CTO), Dan Nurmi, Neil Soman, Dmitrii Zagorodnov, Chris Grzegorczyk, Graziano Obertelli and Woody Rollins (CEO).
Eucalyptus Systems announced a formal agreement with Amazon Web Services in March 2012.

Hewlett-Packard acquired Eucalyptus in September 2014, although by the end of 2016 its public cloud offering HPE Helion was shut down. Eucalyptus team was transferred to the HPE Enterprise Services division, which split away from HPE and merged with Computer Sciences Corporation forming DXC Technology on April 1, 2017. DXC chose to stop development and support of Eucalyptus in 2017, prompting AppScale Systems, led by members of the Eucalyptus founding team, to fork the code. AppScale Systems started commercially supporting and developing the software, which was renamed AppScale ATS, since late 2017.

Software architecture

Eucalyptus commands can manage either Amazon or Eucalyptus instances. Users can also move instances between a Eucalyptus private cloud and the Amazon Elastic Compute Cloud to create a hybrid cloud. Hardware virtualization isolates applications from computer hardware details.

Eucalyptus uses the terminology:
* ''Images'' – An image is a fixed collection of software modules, system software, application software, and configuration information that is started from a known baseline (immutable/fixed). When bundled and uploaded to the Eucalyptus cloud, this becomes a ''Eucalyptus machine image (EMI)''.
* ''Instances'' – When an image is put to use, it is called an instance. The configuration is executed at runtime, and the Cloud Controller decides where the image will run, and storage and networking is attached to meet resource needs.
* ''IP addressing'' – Eucalyptus instances can have public and private IP addresses. An IP address is assigned to an instance when the instance is created from an image. For instances that require a persistent IP address, such as a web-server, Eucalyptus supplies elastic IP addresses. These are pre-allocated by the Eucalyptus cloud and can be reassigned to a running instance.
* ''Security'' – TCP/IP security groups share a common set of firewall rules. This is a mechanism to firewall off an instance using IP address and port block/allow functionality. Instances are isolated at TCP/IP layer 2. If this were not present, a user could manipulate the networking of instances and gain access to neighboring instances violating the basic cloud tenet of instance isolation and separation.
* ''Networking'' – There are three networking modes. In Managed Mode, Eucalyptus manages a local network of instances, including security groups and IP addresses. In System Mode, Eucalyptus assigns a MAC address and attaches the instance's network interface to the physical network through the Node Controller's bridge. System Mode does not offer elastic IP addresses, security groups, or VM isolation. In Static Mode, Eucalyptus assigns IP addresses to instances. Static Mode does not offer elastic IPs, security groups, or VM isolation.
* ''Access Control'' – A user of Eucalyptus is assigned an identity, and identities can be grouped together for access control.

Components

Eucalyptus has six components:

* The ''Cloud Controller (CLC)'' is a Java program that offers EC2-compatible interfaces, as well as a web interface to the outside world. 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 Eucalyptus User Console and manages the underlying compute, storage, and network resources. Only one CLC can exist per cloud and it handles authentication, accounting, reporting, and quota management.
* ''Walrus'', also written in Java, is the Eucalyptus equivalent to AWS Simple Storage Service (S3). Walrus offers persistent storage to all of the virtual machines in the Eucalyptus cloud and can be used as a simple HTTP put/get storage as a service solution. There are no data type restrictions for Walrus, and it can contain images (i.e., the building blocks used to launch virtual machines), volume snapshots (i.e., point-in-time copies), and application data. Only one Walrus can exist per cloud.
* The ''Cluster Controller (CC)'' is written in C and acts as the front end for a cluster within a Eucalyptus cloud and communicates with the Storage Controller and Node Controller. It manages instance (i.e., virtual machines) execution and Service Level Agreements (SLAs) per cluster.
* The ''Storage Controller (SC)'' is written in Java and is the Eucalyptus equivalent to AWS EBS. It communicates with the Cluster Controller and Node Controller and manages Eucalyptus 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 Walrus, which is available to any instance in any cluster.
* The ''VMware Broker'' is an optional component that provides an AWS-compatible interface for VMware environments and physically runs on the Cluster Controller. The VMware Broker overlays existing ESX/ESXi hosts and transforms Eucalyptus Machine Images (EMIs) to VMware virtual disks. The VMware Broker mediates interactions between the Cluster Controller and VMware and can connect directly to either ESX/ESXi hosts or to vCenter Server.
* The ''Node Controller (NC)'' is written in C and hosts the virtual machine instances and manages the virtual network endpoints. It downloads and caches images from Walrus as well as creates and caches instances. While there is no theoretical limit to the number of Node Controllers per cluster, performance limits do exist.

Amazon Web Services compatibility

Organizations can use or reuse AWS-compatible tools, images, and scripts to manage their own on-premises infrastructure as a service (IaaS) environments. The AWS API is implemented on top of Eucalyptus, so tools in the cloud ecosystem that can communicate with AWS can use the same API with Eucalyptus. In March 2012, Amazon Web Services and Eucalyptus announced details of the compatibility between AWS and Eucalyptus. As part of this agreement, AWS will support Eucalyptus as they continue to extend compatibility with AWS APIs and customer use cases. Customers can run applications in their existing data centers that are compatible with Amazon Web Services such as Amazon Elastic Compute Cloud (EC2) and Amazon Simple Storage Service (S3).

In June, 2013, Eucalyptus 3.3 was released, featuring a new series of AWS-compatible tools. These include:
* ''Autoscaling