Eucalyptus is open source software for building AWS-compatible private and hybrid clouds. As an Infrastructure as a Service product, Eucalyptus allows you to flexibly provision your own collections of resources (both compute and storage), on an as-needed basis. It provides many AWS-compatible services including EC2, S3, IAM, ELB, Auto Scaling and CloudWatch. In this series of exercises you will use the User Console to gain familiarity and basic experience using many of these services.
A Eucalyptus cloud is very similar to the AWS cloud you are already working with. You can easily launch instances within customized security groups. You can create and attach storage volumes and make snapshots of volumes for backup or reuse. The most significant difference from AWS is Eucalyptus runs on your own equipment and can be customized to suit your unique needs.
Eucalyptus often makes use of AWS terminology and service names, but there are a few key differences worth noting:
- A Eucalyptus Cloud is equivalent to an AWS Region. Your company may deploy as many Eucalyptus Clouds as desired.
- A Eucalyptus Cluster is equivalent to an AWS Availability Zone. Each cloud may be configured to have one or more Clusters. It is common to have two Clusters per cloud; one Cluster for development and a second for test or staging.
- The Eucalyptus Storage Controller provides functionality similar to that of AWS EBS (Elastic Block Store).
- The public IP assigned to each instance is not visible to the Internet unless you have specifically deployed Eucalyptus this way. With Eucalyptus you can choose to make your cloud visible to the Internet, or just clients within your company's network as shown above.
The exercise begins with setting up basic security then launching a Eucalyptus instance store backed machine image (see below for more info). We will then create and attach an additional Eucalyptus volume. To complete this exercise, you will perform the following tasks:
- Setup security
- Launch a Eucalyptus Instance
- Add a volume to your Instance
- Clean up your instance and volume
Instance Store & EBS Backed Instances
Instance store images the root (/) disk of the instance is a copy of the Eucalyptus Machine Image. This instance type is recommended for stateless VMs because changes made the instance are not retained when the instance is terminated. EBS backed images, by contrast, are persistent. You can stop the instance when you are not using it and start it again without losing changes. You can also take a snapshot of the root volume and register it as a new image.
Readers already familiar with AWS may also want to try the optional tasks, which include connecting to an instance and mounting a volume. These tasks are not required to successfully complete this exercise.