Eucalyptus ,
Nimbus &
Open Nebula
Abstract
Eucalyptus, Nimbus & OpenNebula are major Ope Source
Clou Computing Software Platforms
Manage the provisioning of virtual machines for a cloud
providing IaaS
Commercial cloud services charge, by the hour, for CPU time
It might be more cost effective for the organization to purchase
hardware to create its own private cloud.
These software products are designed to allow an organization
to set up a private group of machines as their own cloud.
These three frameworks represent three different points of
interest in the design space of this particular type of ope -
source cloud.
Analysis
We will discuss how these software frameworks act as
managers that stand in the middle of a number of other
software components.
We will analyze how core decisions in the basic architecture and
overall structure of Eucalyptus, Nimbus and OpenNebula impact
the kind of settings and applications for which each framework
is most suitable.
We will identify several opportunities for improving these
software stacks by identifying some of the challenges that are
common to all three.
The Cloud Computing Stack
A quick overview of entire cloud computing software stack.
In a generic ope source cloud computing system, we can
identify six basic components.
First, we hardware and operating system that are on the various
physical machines in the system.
The second component is the network. This includes the DNS,
DHCP and the subnet organization of the physical machines.
The third component is the virtual machine hypervisor, (also
known as a Virtual Machine Monitor or VMM).
The fourth component is an archive of VM disk images.
The fifth component is the fron end for users.
The last component is the cloud framework itself, where
Eucalyptus, OpenNebula and Nimbus are placed.
Eucalyptus
EUCALYPTUS stands for Elastic Utility Computing Architecture
for Linking Your Program To Useful System.
It is open source software that was developed by University of
Californi Santa Barbara for Cloud Computing to implement
Infrastructure as a Service .
Eucalyptus provide an EC2 compatible cloud Computing
Platform and S3 compatible Cloud Storage thus its services are
available through EC2/S3 compatible APIs.
The Eucalyptus system is composed of 5 main components
interacting together; Client, Cloud Controller, Storage
Controlle (Walrus) Cluster Controller and Node Controller .
Node Controller
• Is installed in each comput
node to control VM activiti
including the execution, in
ction and termination of V
instances.
Cluster Controller
• Runs on 1 machine per clu
works as an intermediar b
een the cloud & node contr
Storage Controller
• Warlus is a component that provides storage services for storing virtual
machine images and user’s data.
Cloud Controller
• It is the user’s entry point into the Eucalyptus system and only one instance
is run on the system. It provides users with a way managing the system.
• Th cloud controller is built using the Enterprise service bu providing
decoupling from the services implementation.
Client
• The client component provides the user with a way to access the
Eucalyptus system (cloud controller).
• Eucalyptu provides two interfaces;
• On is a WDSL which is a SOAP client interface similar to AWS EC2 interface
called euca2ools.
• Anothe interface is a HTTP query based interfac .
Nimbus
Nimbus is another open source IaaS implementation framework
which came online September 2005.
• Nimbus allows a client to lease remote resources by deploying
virtual machines (VMs) on those resources and configuring
them to represent an environment desired by the user.
• It was formerly known as the "Virtual Workspace Service" (VWS)
but the "workspace service" is technically just one the
components in the software collection.
Nimbus was designed with the goal of turning clusters into
clouds mainly to be used in scientific applications.
System Architecture And Design
Th design of Nimbus which consists of a number of components
based on the web servic technology:
1 Workspace ervice
• Allow clients to manage and administer VMs by providing to two interfaces;
1. On interface is based on the web service resource framework (WSRF)
2. Th other is based on EC2 WSDL.
2. Workspace Resource Manager
• Implement VM instance creation on a site and management.
3. Workspace Pilot
• Provide virtualization with significant changes to the site configurations.
4. Workspace Control
• Implement VM instance management such as start, stop and pause VM. It also
provides image management and sets up networks and provides I assignment.
5. Context Broker
• Allow clients coordinate large virtual cluster launches automatically and repeatedly.
6. Workspace Client
• A complex client that provides full access to the workspace service functionality.
7. Cloud Client
• A simpler client providing access to selected functionalities in the workspace service.
8. Storage Service
• Cumulu is a web service providing users with storage capabilities to store images
and works in conjunction with GridFT .
Constructing A Virtual Machine:
1. user uses cloud client to request a VM.
2. Nimbus will SSH into a compute node.
3. The VM template disk image is pushed to
compute node .
4. On the compute node, the disk image is
padded to the correct size and configure
5. Th compute node sets up network bridging
to provide a virtual NIC with a virtual MAC
6. A dhcp server on the compute node is
configured with a MAC/IP pair.
7. VM is spawned on the VMM.
8. Th user can now SSH directly into the VM.
OpenNebula
OpenNebula tends to a greater level of centralization and
customizability (especially for end user ).
Th idea of OpenNebula is a pure private cloud, in which users
actually log into the head node to access cloud function .
OpenNebula, by default, uses a shared file system, typically NFS, for
all disk images files and all files for actually running the OpenNebula
function .
In order to spawn a VM, the user provides a configuration file
containing parameters which would be fed into the VMM command
line. This allows for memory, processor, network and disk resources
to be requested for essentially an configuration.
OpenNebula is also very centralized, especially in its default
Constructing A Virtual Machine
1. user uses ssh to login to the head node.
2. Th user uses the onevm command to reques
3. Th VM template disk image is copied and a c
i padded to the correct size and configurati
the NFS directory on th head node.
4. The on process on the head node uses ssh t
compute node.
5. Th compute node sets up network bridging t
virtua NIC with a virtua MAC.
6. File needed by the VMM on the compute nod
pulled to the compute node via the NFS.
7. VM is spawned on th VMM.
8. Th user can now SSH directly into the V .
SUMMARY
Eucalyptus OpenNebula Nimbus
Philosophy Mimic Amazon EC2 Private, highly Cloud resources
customizable cloud
tailored to scientific
Customizability Some for admin, researchers
Basically everything Many parts except
less for user for image storage
and globus
credentials
DHCP On cluster controller Variable On individual
compute node
Internal Security Tight. Root required Looser, but can be Fairly tight, unless
for many things. made more tight if deploying a fully
needed. private cloud.
User Security Users are given User logs into head Users x509
custom credentials credential is
via a web interface registered with
cloud
THANK YOU
