Survey Paper

Volume 1 / Issue 1 / 2012

Available Online at
www.lbrce.ac.in/ijcc/

Print-ISSN 2319 8869

Online-ISSN 2319 894X

IJCC Volume I/Issue 1/212

An Empherical Research on Open - Source

IaaS Cloud Framework
K. Phaneendraa, I. Rajendra Kumara, M. Babu Reddy#, G. Rajendraa
a

Department of MCA, LBRCE College/ JNTU Kakinada, India

#Dept. Computer Applications, SCNR Govt. Degree College, India

Abstract
Infrastructure-as-a-Service (IaaS) is the most acceptable Cloud computing delivery model that IT managers are exploring
as they relook at their IT infrastructure. Since the beginning of Cloud computing as a new and emerging paradigm, the
field of Distributed Systems is amidst a stage of redefinition. Due to this, there are a wide variety of Cloud solutions,
ranging from virtualization technologies to internet enabled web services; however a Cloud usually entails the use of
Infrastructure-as-a-Service for many people. Infrastructure level cloud technologies support advanced research in the open
IaaS cloud Frameworks. This paper briefly outlines Open source softwares for connecting a set of virtual machines in
IaaS clouds and the differences between the open-source IaaS Frameworks Openstack and OpenNebula.
Keywords : Cloud, OpenStack, OpenNebula, Vitrual Machine (VM), Infrastructure-as-Service (IaaS), Vitrual LAN (vLAN)

1. Introduction
1.The market for cloud technology and integrated services is currently transforming from the hype cycle to testing, piloting,
and implementation by larger enterprises. Given the potential for significant cost savings, smaller and medium sized
organizations are also becoming early adopters of this technology. The emerging market for cloud services is being driven
by the economic downturn, continuing globalization, government edicts, consumer acceptance of technology, and the
growth of the extended enterprise. Cloud technology enables organizations to limit the large capital expenditures previously
associated with costly data centres and applications and transform these costs into operating expenses paying for technology
resources only as needed. In addition, using the cloud enables end users to accelerate time to market since it uses preexisting virtual technology and infrastructure that can be delivered and accessed globally.
The trend toward cloud computing is also being encouraged by the need for organizations to support collaboration and
group decision-making and focus on core competencies, while transferring commodity Services to external vendors. As a
result, the cloud is changing the way that IT services are being sourced and delivered.
While Cloud computing has been driven from the start predominantly by the industry through Amazon [1], Google [2] and
Microsoft [3], a shift is also occurring within the academic setting as well. Due to the many benefits, Cloud computing is
becoming immersed in the area of High Performance Computing (HPC), specifically with the deployment of scientific
clouds [4] and virtualized clusters [5]. Unlike most users of public clouds, typically have a much larger demand for
computing power, so public cloud deployments, especially at the infrastructure level. This allows to leverage one of the
key aspects of Cloud computing; scalability through economies of scale [6]. The fundamental concept is to provide unified
Infrastructure-as-a-Service deployments to a wide variety of users pooling their resources and providing a near-infinite
view of computing power, metered as a utility. In this paper first the focus is on the cloud computing and its benefits,

Corresponding author : Tel No. +91 9912255533

E-mail address: phanikanakamedala@gmail.com.

International Journal Of Computers & Communications - 23

Survey Paper

Volume 1 / Issue 1 / 2012

K. Phaneendra et.al

service models, infrastructure options and characteristics then based upon the concepts of the Infrastructure-as-a-Service
a number of toolkits are available including open-source softwares to build IaaS clouds like Openstack and OpenNebula
are discussed with the differences between them.
2. Cloud Computing
Cloud computing is a model for enabling ubiquitous, convenient, on-demand network access to a shared pool of configurable
computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and
released with minimal management effort or service provider interaction.
2.1 Benefits of cloud computing
Cloud computing [7] is one of the most explosively expanding technologies in the computing industry today. A Cloud
computing implementation typically enables users to migrate their data and computation to a remote location with some
varying impact on system performance [8]. This provides a number of benefits which could not otherwise be achieved. In
addition to lower expenses, enterprises can benefit from many other primary benefits associated with cloud computing.
The benefits can be summarized as follows:
Cost:Companies can save the considerable costs associated with building, maintaining, and operating a data center, especially
power and cooling related expenditures. Additionally, the model allows firms to lower expenditures on support staff,
particularly those providing infrastructure support, systems management, and help desk services. Lastly, cloud computing
enables companies to change what has historically been capital investments (CapEx) to operating expenditures (OpEx).
Scalability:Many organizations have simply run out of existing capacity due to limitations on power consumption. With
the cloud, companies can scale quickly and efficiently added investment. Many cloud providers even offer burstable
infrastructure that automatically expands and contracts to meet peak performance periods.
Green Cloud:Businesses are being pressured to reduce their impact on the environment in the form of greenhouse gases.
As a result, they are now required to report their carbon footprint. Outsourcing via a cloud solution enables companies to
become more environmentally friendly.
Organizational Agility:By eliminating the purchasing of costly hardware and
software and the need to depreciate these assets, organizations are no longer hindered
by infrastructure in terms of global expansion and the ability to adopt the latest
technology. Time to market is also greatly enhanced by empowering departments to
deliver speedy proofs of concept and product demos via the cloud.
Collaboration: The cloud provides an environment that supports global collaboration
and knowledge sharing as well as group decision-making. Shared sites can be easily
set up, replicated, and torn down as needed to meet the collaboration requirements of
a given project.
Focus: Delegating commodity infrastructure and services allows organizations to
focus on their core competencies and further develop capabilities that can differentiate
their organizations in their respective business markets.

Figure 1: Service Models

2.2 Cloud Computing Service Models

The NIST of cloud computing defines three Service models. [9] These service models currently associated with cloud
computing: Cloud Infrastructure-as-a-Service (IaaS), Cloud Software as a Service (SaaS), and Cloud Platform as a
Service (PaaS). The following summarizes the key concepts of each of these three service models.

International Journal Of Computers & Communications - 24

Survey Paper

Volume 1 / Issue 1 / 2012

K. Phaneendra et.al

Software as a Service (SaaS): The consumer uses an application, but does not control the operating system, hardware or
network infrastructure on which its running.
Platform as a Service (PaaS): The consumer uses a hosting environment for their applications. The consumer controls
the applications that run in the environment (and possibly has some control over the hosting environment), but does not
control the operating system, hardware or network infrastructure on which they are running. The platform is typically an
application framework.
Infrastructure-as-a-Service (IaaS): The consumer uses fundamental computing resources such as processing power,
storage, networking components or iddleware. The consumer can control the operating system, storage, deployed applications
and possibly networking. Components such as firewalls and load balancers, but not the cloud infrastructure beneath them.
2.3 Cloud Infrastructure Options
For most businesses, organizations, or governmental agencies, there are four relevant types of clouds: Private (internal or
vendor-hosted), Public (external), Community and Hybrid (mixed).The NIST definition defines four Cloud Infrastructure
Options as.
Public Cloud: Public cloud services are characterized as being available to clients from a third party service provider via
the Internet. The term public does not always mean free, even though it can be free or fairly inexpensive to use. A public
cloud does not mean that a users data is publically visible; public cloud vendors typically provide an access control
mechanism for their users. Public clouds provide an elastic, cost effective means to deploy solutions.
Private Cloud: A private cloud offers many of the benefits of a public cloud computing environment, such as being elastic
and service based. The difference between a private cloud and a public cloud is that in a private cloud-based service, data
and processes are managed within the organization without the restrictions of network bandwidth, security exposures and
legal requirements that using public cloud services might entail. In addition, private cloud services offer the provider and
the user greater control of the cloud infrastructure, improving security and resiliency because user access and the networks
used are restricted and designated.
Community Cloud: A community cloud is controlled and used by a group of organizations that have shared interests,
such as specific security requirements or a common mission. The members of the community share access to the data and
applications in the cloud.
Hybrid Cloud: A hybrid cloud is a combination of a public and private cloud that interoperates. In this model users
typically outsource nonbusiness- critical information and processing to the public cloud, while keeping business-critical
services and data in their control.
2.4 Characteristics of Cloud Computing
According to the National Institute of Standards and Technology Information Technology Laboratory, cloud computing is
a model for enabling convenient, on-demand network access to a shared pool of configurable computer resources that can
be rapidly provisioned and released with minimal management effort or service provider interaction. The characteristics
often associated with cloud computing are as follows:
On-demand self-service by consumers:The technology is available to end users as it is needed without intervention by
internal IT.
Broad access via the network:The technology can be accessed via an enterprise or public network and can be easily
accessed from any location.
Resource pooling of physical and virtual resources:Since the data center and virtual resources are situated in one place,
the technology can be shared and maintained more efficiently.

International Journal Of Computers & Communications - 25

Survey Paper

Volume 1 / Issue 1 / 2012

K. Phaneendra et.al

Rapid scaling of capacity:The cloud permits the rapid provisioning of end users and shared resources allows for elasticity
of demand and capacity.
Enhanced transparency of usage via metrics: Centralized resources, vendor management, and contractual Service Level
Agreements (SLAs) facilitate increased transparency and meaningful information that can be used by management.
3. Infrastructure-as-a-Service (Iaas)
3.1 IaaS Overview
In order to properly evaluate each IaaS technology, a detailed overview to each major technology is necessary. This
includes OpenStack, and OpenNebula; the two major open IaaS deployments currently available to the broader community.
Infrastructure-as-a-Service (IaaS) means delivering a virtual server, desktop computer or remote storage from the cloud. In
other words, a hosting provider gives you a remote data center where it manages the infrastructure, servers and
virtualization and you access your virtual computers and storage from the internet through a secure virtual private
network (VPN) connection.
An IaaS approach to infrastructure can offer:

Faster responses to changing business conditions or internal customer needs, enabled by rapid system provisioning
and rapid scalability, both up and down, without the long-term lock-in of hardware purchases

Productivity increases resulting from access to your applications and data from anywhere and the reliability that
comes from a distributed computing model

Reduced capital outlay for hardware acquisition, maintenance, data center real estate, and power and cooling,
when using a pay-for-use (public cloud) model

3.2 Future Grid

Future Grid is a national-scale Grid and Cloud test-bed facility that includes a number of computational resources across
many distributed locations. The Future Grid network is unique and can lend itself to a multitude of experiments specifically
for evaluating middleware technologies and experiment management services. This network can be dedicated to conduct
experiments in isolation, using a network impairment device for introducing a variety of predetermined network conditions.
All network links within Future Grid are dedicated 10GbE links with the exception of a shared 10GbE link to TACC over
the TeraGrid [10] network, enabling high-speed data management and transfer between each partner site within Future
Grid. One important feature to note is that most systems can be dynamically provisioned, e.g. these systems can be
reconfigured when needed by special software that is part of Future Grid with proper access control by users and
administrators. Therefore its believed that this hardware infrastructure can fully accommodate the needs of an experiment
management system. The users can use this futureGrid to test these open source like Openstack and OpenNebula to build
IaaS clouds.
3.3 Overview Of Cloud IaaS Frameworks
One fundamental concept in cloud computing is based on providing Infrastructure-as-a-Service (IaaS) to deliver resources
to customers and users instead of purchasing and maintaining compute, storage, and network. Typically this is achieved
through virtual machine offerings. In order to establish such a service, a number of toolkits are available including
OpenNebula, OpenStack. We will provide a short discussion about these toolkits next and outline some major differences
between them.

International Journal Of Computers & Communications - 26

Survey Paper

Volume 1 / Issue 1 / 2012

K. Phaneendra et.al

3.3.1 Openstack
Openstack has been introduced by Rackspace and NASA in July 2010. The project is trying to build an open source
community spanning technologists, developers, researchers, and industry to share resources and technologies with the
goal to create a massively scalable and secure cloud infrastructure. In tradition with other open source projects the entire
software is open sources and limited to just open source APIs such as Amazon. Currently, OpenStack focuses on the
development of two aspects of cloud computing to address compute and storage aspects with their OpenStack Compute
and OpenStack Storage solutions. According to the documentation OpenStack Compute is the internal fabric of the cloud
creating and managing large groups of virtual private servers and OpenStack Object Storage is software for creating
redundant, scalable object storage using clusters of commodity servers to store Terabytes or even petabytes of data.
Recently, an image repository has been prototyped. The image repository contains an image registration and discovery
service and an image delivery service. Together they deliver images to the compute service while obtaining them from the
storage service. This development gives an indication that the project is striving to integrate more services into their
portfolio.
OpenStack Compute. As part of its computing support efforts OpenStack [11] is developing a cloud computing fabric
controller, a component of an IaaS system, known under the name Nova. The architecture for Nova is built on the concepts
of shared-nothing and messaging-based information exchange. Hence most communication in Nova are facilitated by
message queues. To prevent blocking components while waiting for a response from others, deferred objects are introduced.
Such objects include callback that gets triggered when responses received. This is very similar to established concepts
from parallel computing such as futures which have been successfully utilized in the Grid community by projects such
as the CoG Kit.
To achieve the shared-nothing paradigm, the overall system state is kept in a distributed data system. State updates are
made consistent through atomic transactions. Nova it implemented in python while utilizing a number of externally supported
libraries, and components. This includes boto an Amazon API provided in python [12], and Tornado a fast HTTP server
used to implement the S3 capabilities in Open- Stack. Figure OS.1 shows the main architecture of Openstack Compute. In
this architecture the API Server receives http requests from boto, converts the commands to and from the API format while
forwarding requests to the cloud controller. The cloud controller maintains the global state of system, assures authorization
while interacting with the User Manager via LDAP, interacts with the S3 service and manages nodes, as well as storage
workers through a queue. Additionally Nova integrates networking components to manage private networks, public IP
addressing, VPN connectivity, and firewall rules. They include the following types:

Network Controller, that manages address and vLAN allocations,

Routing Node, that governs the NATs public IPs to private IPs, and enforces firewall rules,

Addressing Node, that runs DHCP services for private networks, and

Tunnelling Node, that provides VPN connectivity.

The network state (managed in the distributed object store) allows the following:

vLAN assignment,

Private Subnet assignment to a security group in a vLAN,

Private IP assignments to running instances,

Public IP allocations, and

Public IP associations to a private IP / running instance.

OpenStack Storage. The OpenStack storage solution is build around a number of interacting components and concepts
including a Proxy Server, a Ring, Object Server, a Container Server, an Account Server, Replication, Updaters, and Auditors.
The role of the Proxy Server is to enable of look ups to the location of the accounts, containers, or objects in OpenStack
International Journal Of Computers & Communications - 27

Survey Paper

Volume 1 / Issue 1 / 2012

K. Phaneendra et.al

storage rings and route the request. Thus any object is streamed to or from an object server directly through the proxy
server to or from the user. A ring represents a mapping between the names of entities stored on disk and their physical
location. Separate rings for accounts, containers, and objects exist. A ring includes the concepts of using zones, devices,
partitions, and replicas.
Hence it allows dealing with failures, and isolation of zones representing a drive, a server, a cabinet, a switch, or even a
datacenter. Weights can be used to balance the distribution of partitions on drives across the cluster allowing to support
heterogeneous storage resources. According to the documentation, the Object Server is a very simple blob storage server
that can store, retrieve and delete objects stored on local devices. Objects are stored as binaryfiles with metadata stored in
the files extended attributes.
This requires that the underlying filesystem choice for object servers support which is often not the case for standard Linux
installations. To list objects, a Container Server can be utilized. Listing of containers is handled by the Account Server. At
this time the documentation of OpenStack indicates that the software is not yet ready for production services. The project
has achieved a significant amount of publication and support. However the documentation of the project has at this time
just started and is improved by its partners.
3.3.2 Open Nebula
OpenNebula [13], [14] is an open-source toolkit which allows transforming existing infrastructure into an Infrastructureas-a-Service (IaaS) cloud with cloud-like interfaces.

Figure 2 shows the OpenNebula architecture and their main components.

The architecture of OpenNebula has been designed to be flexible and modular to allow its integration with different
storage and network infrastructure configurations, and hypervisor technologies. Here, the core is a centralized component
that manage the virtual machines (VM) full life cycle, including setting up networks dynamically for groups of VMs and
managing their storage requirements, such as VM disk image deployment or on-the-fly software environment creation.
Other important component is the capacity manager or scheduler. It governs the functionality provided by the core. The
default capacity scheduler is a requirement/rank matchmaker. However, it is also possible to develop more complex
scheduling policies, through a lease model and advance reservations like Haizea [15]. The last main components are the
access drivers. They provide an abstraction of the underlying infrastructure to expose the basic functionality of the monitoring,
storage and virtualization services available in the cluster. Therefore, OpenNebula is not tied to any specific environment
and can provide a uniform management layer regardless of the virtualization platform.
Additionally, OpenNebula offers management interfaces to integrate the cores functionality within other data center
management tools, such as accounting or monitoring frameworks. To this end, OpenNebula implements the libvirt API
International Journal Of Computers & Communications - 28

Survey Paper

Volume 1 / Issue 1 / 2012

K. Phaneendra et.al

[16], anopen interface for VM management, as well as a command line interface (CLI). A subset of this functionality is
exposed to external users through a cloud interface. Due to its architecture, OpenNebula is able to adapt to organizations
with changing resource needs, including the addition or failure of physical resources [17]. Some essential features to
support changing environments are the live migration and the snapshotting of VMs. Furthermore, when the local resources
are insufficient, OpenNebula can support a hybrid cloud model by using cloud drivers to interface with external clouds.
This lets organizations supplement the local infrastructure with computing capacity from a public cloud to meet peak
demands, or implement high availability strategies.
OpenNebula currently includes an EC2 driver, which can submit requests to Amazon EC2 and Eucalyptus, as well as an
ElasticHosts driver [18]. Regarding the storage, an Image Repository allows users to easily specify disk images from a
catalogue without worrying about low-level disk configuration attributes or block device mapping. Also, image access
control is applied to the images registered in the repository, hence simplifying multi-user environments and image sharing.
Nevertheless, users can also set up their own images.
4. Comparison Of The Iaas Framework
All these IaaS frameworks have been designed to allow users to create and manage their own virtual infrastructures.
However, these frameworks have differences that need to be considered when choosing a framework. Thus, we are going
to provide a comparison of a selected number of essential features supported by each one. We summarized our findings in
Table 1.
Openstack

OpenNebula

Interfaces

EC2nand S3, rest Interface.

Working on OCCI

Native XML/RPC,EC2andS3,OCCI,
Rest Interface.

Hypervisor

KVM,XEN, VMware
Vsphere, LXC,UML and
Microsofts Hyper V

KVM, XEN and VMware

Networking

-Two modes:
(a)Flat Networking
(b)LAN Networking
-Creates bridge automatically
-Uses IP forwarding for public IP
-VMs only have Private IPs

- Networks can be defined to support Ebtable,

Open vSwitch and 802.1Q tagging
-Bridges must exists in the compute nodes
-IP are setup inside VM

Software deployment

- Software is composed by different

component that can be distributed in
different machines.
- Compute nodes need to install
OpenStack software

Software is installed in frontend

DevOps deployment

Chef, Crowbar , Puppet

Chef ,Puppet

Storage(Image
Transference)

- Swift (http/s)
- Unix filesystem (ssh)

Unix Filesystem (ssh, shared filesystem

or LVM with CoW)

Authentication

X509 credentials, LDAP

X509 credential, ssh rsa keypair,

password, LDAP

Table 1: Summery of Comparison

International Journal Of Computers & Communications - 29

Survey Paper

Volume 1 / Issue 1 / 2012

K. Phaneendra et.al

Software deployment.[19] This is the first obstacle that is found to deploy our own infrastructure. The easiest way to
deploy is OpenNebula because we only have to install a single service in the frontend for a basic configuration while no
OpenNebula software is installed in the compute nodes. On the other hand, OpenStack deployments are quite difficult to
achieve due to the entire different components that need to configure and the different configuration possibilities that they
provide. From the release notes and announcements of the framework we observe that major updates happen on a 4 or 6
month schedule, with many release candidates that fix also intermediate issues. Furthermore it is observed that the installation
deployment depends on scalability requirements and that it is important to note that a deployment lets say for a 4 node
OpenStack environment may look quite different from a 60 node installation. Hence, it is important that toolkits providing
IaaS can be deployed through configuration management toolkits in order to minimize the effort of repetitive tasks to
deploy them on the resources once new versions com out or if a different configuration is set up. Tools such as chef and
puppet provide a considerable value add in this regards. Furthermore, they serve as a repeatable template to install the
services in case version dependent performance comparisons or feature comparisons are conducted by the users.
Interfaces. Since Amazon EC2 is a standard de-facto, all of them support the basic functionality of this interface, namely:
image upload and registration, and the VM run, describe and terminate operations. However, the OpenStack project noticed
disadvantages due to features that EC2 is not exposing. Thus OpenStack is considering providing interfaces that diverge
from the original EC2 standard.
Storage: Storage is very important in cloud because we have to manage many images and they must be available for users
anytime. Therefore, most of the IaaS frameworks decided to provide a cloud storage system that can be used not only for
internal purposed, but also as an independent product. In case of OpenStack, a more sophisticated storage system called
Swift and Walrus, respectively. It is designed to provide good fault tolerant and scalability. In the case of OpenStack, the
images can be stored in the posixfilesystem or in Swift. In the first case, images are transferred using Ssh while in the
second one are transferred using http/s. Finally, OpenNebula does not provide a cloud storage product, but its internal
storage system can be configuring in different ways. Thus, we can have a shared filesystem between frontend and compute
nodes; we can transfer the images using Ssh; or we can use LVM with CoW to copy the images to the compute nodes.
Networking: The network is managed differently for each IaaS framework while providing various options in each of
them.
OpenStack support two modes of managing networks for virtual machines: flat networking and vLAN networking. vLAN
based networking requires that you have a vLAN capable managed switch that you can use to setup vLANs for your
systems. Flat Networking uses Linux Ethernet bridging to connect multiple compute hosts together.
OpenNebula network contains the following options: host-managed vLANs where the network access is restricted through
vLAN tagging, which also requires support from the hardware switches; Ebtables to restrict the network access through
Ebtables rules; and Open vSwitch to restrict network access with Open vSwitch Virtual Switch.
Hypervisors. All of the IaaS frameworks do support KVM and XEN and cover therefore the most popular hypervisors.
VMware is also supported OpenNebula and Openstack. Additionally, OpenStack also supports LXC, UML and Microsofts
HyperV. This makes OpenStack a quite attractive choice for experimenting with different hypervisors environments.
Authentication. All of the IaaS frameworks support X509 credentials as authentication method for users. OpenStack and
OpenNebula also support authentication via LDAP, although is quite basic. OpenNebula also support Sshrsakeypair and
password authentication.
OpenNebula and OpenStack as open cloud managers addressing different types of cloud needs, and implementing different
distribution models and interoperability strategies. Both, OpenNebula and OpenStack, deliver fully open-source software
to build IaaS clouds, released under Apache license, and developed with an open and transparent process over the Internet.
However, the report highlights relevant differences between both projects:
While OpenNebula offers a comprehensive solution for data center virtualization management, enabling the users to easily
build their own private and hybrid clouds, OpenStack mainly serves the needs of public service providers, focusing on
AWS-like public cloud features.
International Journal Of Computers & Communications - 30

Survey Paper

Volume 1 / Issue 1 / 2012

K. Phaneendra et.al

OpenNebula is delivered as a single integrated package comprising key functionalities for cloud computing with a single
install, whereas OpenStack delivers a set of products for individual functionalities and capabilities.
OpenNebula is committed to implementing major de-facto and de-jure standards, such as Amazon APIs, or the specifications
by OGF, DMTF and SNIA. OpenStack builds loosely up on AWS, but primarily incorporates its own standardization
working group, trying to incorporate the requirements from the participating companies.
Clearly, different open-source cloud management tools will coexist and fit together in a broader cloud ecosystem.
5. Related Work
Open Cloud Computing Interface Working Group (OCCI-WG) from Open Grid Forum is developing a practical solution
which covers the provisioning, monitoring and definition of IaaS [20]. The work on OCCI specification is still ongoing,
and it requires service provider to adopt OCCI standard. RightScale is focusing on the deployments of multiple servers and
the connections between them across one or more clouds. Cloudkick provides very nice monitoring and visualization for
users IaaS resources.
6. Conclusion
Building and operating a private cloud ourselves is simple Private cloud isnt so different from running our own virtual
machine environment. Cloud Management Software is the layer that provisions cloud guests and sits between the API and
the hypervisor. It explains the differences between the major cloud management software options OpenStack, OpenNebula,
and then it is difficult to have an expertise to choose the right one for your needs. The above four aspects are critical for
successfully building and operating your own private cloud. Generic service models for IaaS by abstracting the commonly
used operations from leading IaaS providers, and make our models with full coverage of functionalities to satisfy IaaS
users requirements. There are other success factors know your strategy, know your business model, and use effective
project management that are part of any successful technological change.
References
[1]
[2]
[3]
[4]
[5]
[6]
[7]
[8]

[9]
[10]
[11]

Amazon, Elastic Compute Cloud. [Online]. Available: http://aws.amazon.com/ec2/

E. Ciurana, Developing with Google App Engine. Springer, 2009.
D. Chappell, Introducing windows azure, Microsoft, Inc, Tech. Rep.,2009.
K. Keahey, R. Figueiredo, J. Fortes, T. Freeman, and M. Tsugawa, Science clouds: Early experiences in cloud
computing for scientific applications, Cloud Computing and Applications, vol. 2008, 2008.
I. Foster, T. Freeman, K. Keahy, D. Scheftner, B. Sotomayer, and X. Zhang, Virtual clusters for grid communities,
Cluster Computing and the Grid, IEEE International Symposium on, vol. 0, pp. 513520, 2006.
G. Stigler, Economies of Scale, The, JL& Econ., vol. 1, p. 54, 1958.
M. Armbrust, A. Fox, R. Griffith, A. Joseph, R. Katz, A. Konwinski, G. Lee, D. Patterson, A. Rabkin, I. Stoica et
al., A view of cloud computing, Communications of the ACM, vol. 53, no. 4, pp. 5058, 2010.
L. Wang, G. von Laszewski, A. J. Younge, X. He, M. Kunze, and J. Tao, Cloud Computing: a Perspective Study,
New Generation Computing, vol. 28, pp. 6369, Mar 2010. [Online]. Available: http: /cyberaide.googlecode.com/
svn/trunk/papers/08-lizhe-ngc/08-ngc.pdf
A white paper produced by the Cloud Computing Use Case Discussion Group, Cloud Computing Use Cases,
Version 2.0, 30 October 2009.
F. Berman, From TeraGrid to knowledge grid, Communications of the ACM, vol. 44, no. 11, pp. 2728, 2001.
Openstack. cloud software, http://openstack.org, Last Access Mar. 2011.

International Journal Of Computers & Communications - 31

Survey Paper
[12]
[13]
[14]
[15]
[16]
[17]
[18]
[19]
[20]

Volume 1 / Issue 1 / 2012

K. Phaneendra et.al

Boto project, http://code.google.com/p/boto. Last Access Mar. 2011.

Opennebula project, http://www.opennebula.org. Last access Mar. 2011.
I. M. Llorente, R. Moreno-Vozmediano, and R. S. Montero, Cloud computing for on-demand grid resource
provisioning, Advances in Parallel Computing, vol. 18, no. 5, pp. 177191, 2009.
B. Sotomayor, R. S. Montero, I. M. Llorente, and I. Foster, Capacity leasing in cloud systems using the opennebula
engine, Cloud Computing and its Applications, 2008.
Libvirt API webpage, http:// libvirt.org. Last access Mar. 2011.
B. Sotomayor, R. S. Montero, I. M. Llorente, and I. Foster, Virtual infrastructure management in private and
hybrid clouds, IEEE Internet Computing, vol. 13, no. 5, pp. 1422, 2009.
Elastichosts webpage, http://www.elastichosts.com. Last Access Mar. 2011.
Javier Diaz, Gregor von Laszewski, Fugang Wang, Geoffrey C. Fox, Towards Cloud Deployments using
FutureGrid,
Open Cloud Computing Interface Specification, Open Cloud Computing Interface Working Group. [Online].
Available:http://www.occiwg.org/

International Journal Of Computers & Communications - 32