0% found this document useful (0 votes)
52 views

Assignment On Cloud OS

The document contains short reports on three open-source cloud platforms: Nimbus, Eucalyptus, and OpenNebula. Nimbus allows deploying virtual clusters via contextualization and supports Xen and KVM. Eucalyptus implements IaaS in private clouds using five components. OpenNebula provides efficient management of interconnected VMs and exhibits an open architecture that integrates with any virtualization platform or cloud offering.

Uploaded by

Shantanu
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
52 views

Assignment On Cloud OS

The document contains short reports on three open-source cloud platforms: Nimbus, Eucalyptus, and OpenNebula. Nimbus allows deploying virtual clusters via contextualization and supports Xen and KVM. Eucalyptus implements IaaS in private clouds using five components. OpenNebula provides efficient management of interconnected VMs and exhibits an open architecture that integrates with any virtualization platform or cloud offering.

Uploaded by

Shantanu
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 7

Jahangirnagar University

Department of Computer Science

Assignment No: 02
Course Name Cloud Computing
Assignment Title Cloud OS
Course Number PMSCS 651 Assignment No. 02
Issue Date 29 May 2021 Submission Date 02 June 2021

Name: Shantanu Mazumder

Roll No : CSE202101154
Prof. Dr. Mohammad Zahidur Rahman
Dept. of CSE.
Session: 2021-22 Jahangirnagar University
Semester: Spring-2021

Batch No: 25

Submitted By Submitted To
Short Report On Nimbus:

Nimbus is an open-source toolkit that, once installed on a cluster, provides an infrastructure as a service
cloud to its client via WSRF-based or Amazon EC2 WSDL web service APIs. It allows a client to hire
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 of the components in the software collection.

Nimbus supports the Xen hypervisor or KVM and virtual machine schedulers PBS and SGE. It allows the
deployment of self-configured virtual clusters via contextualization. It is configurable concerning
scheduling, networking leases, and usage accounting.

Nimbus was designed to turn clusters into clouds mainly to be used in scientific applications.

Nimbus is comprised of two products:


i. Nimbus Infrastructure: Nimmmbus infrastructure is an open-source EC2/S3-compatible
Infrastructure-as-a-Service implementation specifically targeting features of interest to the
scientific community such as support for proxy credentials, batch schedulers, best-effort
allocations, and others.
ii. Nimbus Platform: Nimbus Platform is an integrated set of tools, operating in a multi-cloud
environment, that deliver the power and versatility of infrastructure clouds to scientific users.
Nimbus Platform allows you to reliably deploy, scale, and manage cloud resources.

System Architecture And Design:

The design of Nimbus consists of several components based on the web service technology:
1. Workspace Service:
 Allows clients to manage and administer VMs by providing two interfaces;
i. One interface is based on the web service resource framework (WSRF)
ii. The other is based on EC2 WSDL

2. Workspace Resource Manager


 Implements VM instance creation on a site and management.

3. Workspace Pilot:
 Provides virtualization with significant changes to the site configurations.

4. Workspace Control:
 Implements VM instance management such as start, stop and pause VM. It also
provides image management and sets up networks and provides IP assignment.

5. Context Broker:
 Allows clients to 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:
 Cumulus is a web service providing users with storage capabilities to store images
and works in conjunction with GridFTP

Nimbus-supported Science Clouds have two objectives:


• To make it easy for scientific and educational projects to experiment with cloud computing, and
• To learn how to make cloud computing a useful tool for the scientific community.
.Short Report On Eucalyptus:

EUCALYPTUS stands for Elastic Utility Computing Architecture for Linking Your Program To Useful
System. Eucalyptus in cloud computing is an open-source software platform for carrying out IaaS or
Infrastructure-as-a-Service in a hybrid cloud computing or private cloud computing environment.

It is also known as an open-source Linux-based software architecture that provides an EC2-compatible


cloud computing platform and S3-compatible cloud storage platform. It implements scalable, efficient-
enhancing, and private and hybrid clouds within and the organization’s IT infrastructure. It gives an
Infrastructure as a Service (IaaS) solution. Users can use commodity hardware.

Eucalyptus was developed by the University of California-Santa Barbara for Cloud Computing to
implement Infrastructure as a Service. It was developed to support high-performance computing (HPC).
Eucalyptus can be deployed without modification on all major Linux OS distributions, including Ubuntu,
RHEL/CentOS, OpenSUSE, and Debian.

Eucalyptus Features:

 SSH Key Management


 Image Management
 Linux-based VM Management
 IP Address Management
 Security Group Management
 Volume and Snapshot Management

The Eucalyptus system is composed of 5 main components interacting together:


Components of Eucalyptus:

 Cluster Controller (CC): It is a C program that is the front end for a Eucalyptus cloud cluster. It
can communicate with the Storage controller and Node controller. It manages the instance
execution in the cloud.
 Cloud Controller (CLC): This is the controller that manages virtual resources like servers,
networks, and storage. It is at the highest level in the hierarchy. It is a Java program with a web
interface for the outside world. It can do resource scheduling as well as system accounting. There
is only one CLC per cloud. It can handle authentication, accounting, reporting, and quota
management in the cloud.
 Node Controller (NC): It is the basic component for Nodes. Node controller maintains the life
cycle of the instances running on each node. Node Controller interacts with the OS, hypervisor,
and the Cluster Controller simultaneously.
 Walrus Storage Controller (WS3): This is another Java program in Eucalyptus that is equivalent
to AWS S3 storage. It provides persistent storage. It also contains images, volumes, and
snapshots similar to AWS. There is only one Walrus in a cloud.
 Storage Controller (SC): It is a Java program equivalent to EBS in AWS. It can interface with
Cluster Controller and Node Controller to manage persistent data via Walrus.

It is utilized to assemble hybrid, public and private cloud. It can likewise deliver your data center into a
private cloud and permit you to stretch out the usefulness to numerous different organizations.

Eucalyptus in cloud computing is open-source programming that carries out an AWS viable cloud, which
is financially savvy, secure, and flexible. It tends to be effectively sent in existing IT frameworks to
appreciate both private and public cloud models’ advantages.

Short Report On OpenNebula:

The OpenNebula virtual infrastructure engine provides efficient, dynamic, and scalable management of
groups of interconnected VMs within datacenters involving a large amount of virtual and physical servers.
OpenNebula tends to a greater level of centralization and customizability (especially for end-users). The
idea of OpenNebula is a pure private cloud, in which users log into the head node to access cloud
functions.
OpenNebula also exhibits an open and flexible architecture that allows the definition of new algorithms
for virtual machine placement, and its integration with any virtualization platform, infrastructure cloud
offering, and third-party components in the cloud ecosystem, such as cloud-like remote interfaces, virtual
image managers, and service managers.
OpenNebula is one of the components being enhanced in the context of the European Union’s Reservoir
Project, which aims to develop the open-source technology to enable deployment and management of
complex IT services across different administrative domains.

To spawn a VM, the user provides a configuration file containing parameters that would be fed into the
VMM command line. This allows for memory, processor, network, and disk resources to be requested for
essentially any configuration.
OpenNebula is also very centralized, especially in its default configuration with an NFS filesystem
The main difference between OpenNebula and other commercial cloud solutions is that its truly open
source blood guarantees users complete interoperability with every existing infrastructure component
already available. Thus, it avoids vendor lock-in using common open industry standards, such as EC2
API and Open Cloud Computing Interface (OCCI).

The core features:


The first steps with OpenNebula are towards the realization of a private cloud. A private cloud does not
expose any API, and every resource is used for internal purposes only. When cloud resources are
available, whether exclusively or not, to third-party users through a predefined set of APIs, it is named a
public cloud. When you use external resources to improve your cloud, or you expose to third-party users
your own local resources or both, it is called a hybrid cloud.

Figure: Features Of Opennebula

OpenNebula architecture:
To control a VM’s life cycle, the OpenNebula core coordinates with the following three areas of
management:
1) Image and storage technologies — to prepare disk images
2) The network fabric — to provide the virtual network environment
3) Hypervisors — to create and control VMs

Figure: Architecture of OpenNebula


Through pluggable drivers, the OpenNebula core can perform the above operations. It also supports the
deployment of services. VM placement decisions are taken by a separate scheduler component. It follows the rank
scheduling policy, which makes place for VMs on a physical host according to the rank given by the scheduler.
These ranks are decided by the scheduler, using a ranking algorithm. OpenNebula uses cloud drivers to interact
with external clouds, and also integrates the core with other management tools by using management interfaces.

Components of OpenNebula:

Figure:

Based on the existing infrastructure, OpenNebula provides various services and resources.

APIs and interfaces: These are used to manage and monitor OpenNebula components. To manage physical and
virtual resources, they work as an interface.

Users and groups: These support authentication and authorize individual users and groups with individual
permissions.

Hosts and VM resources: These are key aspects of a heterogeneous cloud that is managed and monitored, e.g.,
Xen, VMware.

Storage components: These are the basis for centralized or decentralized template repositories.

Network components: These can be managed flexibly. Naturally, there is support for VLANs and Open vSwitch.

ebula is also very centr an NFS filesystem

You might also like