88 |
A. Govindarajan and Lakshmanan |
5.7 Closing Notes
Standardisation historically has been a challenge. Getting competitors to agree on standards or switch to another vendor’s standards is tough. However, drive by powerful standards, organisations such as DMTF, SNIA, etc., with backing from industry leaders, can definitely make it possible whilst avoiding excessive proliferation. The aim should be to extend the IT standards to address the new scenarios that cloud brings in and not create fresh standards making its definition and adoption tougher.
References
1.IT Cloud Services User Survey by IDC (2009) http://blogs.idc.com/ie/?p=210. Accessed 11 Dec 2009
2.PCI Data Security Standard (2009) https://www.pcisecuritystandards.org/security_standards/ pci_dss.shtml. Accessed 11 Dec 2009
3.Porting on Wikipedia (2009) http://en.wikipedia.org/wiki/Portability_(computer_science). Accessed 11 Dec 2009
4.Sarbanes-Oxley (SOX) on Wikipedia (2009) http://en.wikipedia.org/wiki/ Sarbanes%E2%80%93Oxley_Act. Accessed 11 Dec 2009
5.HIPAA on Wikipedia (2009) http://en.wikipedia.org/wiki/HIPAA. Accessed 11 Dec 2009
6.Unified Cloud Interface (2009) http://code.google.com/p/unifiedcloud/. Accessed 11 Dec 2009
7.CCIF (2009) http://www.cloudforum.org/. Accessed 11 Dec 2009
8.OCCI (2009) http://www.occi-wg.org/doku.php. Accessed 11 Dec 2009
9.OGF (2009) http://www.ogf.org/. Accessed 11 Dec 2009
10. Open Virtualization Format Specification (2009) http://www.dmtf.org/standards/published_ documents/DSP0243_1.0.0 .pdf. Accessed 11 Dec 2009
11. DMTF (2009) http://www.dmtf.org. Accessed 11 Dec 2009
12. Standards and Interoperability of Large Data Clouds (2009). http://opencloudconsortium.org/ working-groups. Accessed 11 Dec 2009
13. Open Cloud Consortium (2009) http://opencloudconsortium.org/. Accessed 11 Dec 2009 14. GoGrid Moves API Specification to Creativecommons (2009) http://www.gogrid.com/com-
pany/press-releases/gogrid-moves-api-specification-to-creativecommons.php. Accessed 11 Dec 2009
15. GoGrid (2009) http://www.gogrid.com/. Accessed 11 Dec 2009
16. Cloudware Open Architecture (2009) http://www.3tera.com/Cloud-computing/. Accessed 11 Dec 2009
17. 3Tera (2009) http://www.3tera.com/. Accessed 11 Dec 2009
18. Gartner Says Cloud Consumers Need Brokerages to Unlock the Potential of Cloud Services (2009) http://www.gartner.com/it/page.jsp?id=1064712. Accessed 11 Dec 2009
19. Cloud Security Alliance Guidelines (2009) http://www.cloudsecurityalliance.org/guidance/ csaguide.pdf. Accessed 11 Dec 2009
20. Cloud Security Alliance (2009) http://www.cloudsecurityalliance.org/. Accessed 11 Dec 2009 21. Amazon VPC (2009) http://aws.amazon.com/vpc/. Accessed 11 Dec 2009
22. Amazon Web Services (2009) http://aws.amazon.com/. Accessed 11 Dec 2009
23. Securing Microsoft Cloud Infrastructure (2009) http://www.globalfoundationservices.com/ security/index.html. Accessed 11 Dec 2009
24. Microsoft Cloud Computing (2009) http://www.microsoft.com/virtualization/cloud-computing/ default.mspx. Accessed 11 Dec 2009
5 Overview of Cloud Standards |
89 |
25. Amazon Web Services: Overview of Security Processes (2009) http://aws.amazon.com/. Accessed 11 Dec 2009
26. Cloud Storage Initiative (2009) http://www.snia.org/forums/csi/. Accessed 11 Dec 2009
27. Storage Networking Industry Assoc (SNIA) (2009) http://www.snia.org/. Accessed 11 Dec 2009
28. Cloud-Ready Server Templates (2009) http://www.rightscale.com/products/advantages/cloud- ready-servertemplates.php. Accessed 11 Dec 2009
29. RightScale website (2009) http://www.rightscale.com/. Accessed 11 Dec 2009
30. Open Cloud Platform (2009) http://www.sun.com/solutions/cloudcomputing/index.jsp. Accessed 11 Dec 2009
31. Sun Microsystems website (2009) http://www.sun.com/. Accessed 11 Dec 2009
32. WebLayers Center 5.0. (2009) http://www.weblayers.com/products/wl-center.shtml. Accessed 11 Dec 2009
33. WebLayers (2009) http://www.weblayers.com/. Accessed 11 Dec 2009
34. Open Cloud Manifesto (2009) http://www.opencloudmanifesto.org/. Accessed 11 Dec 2009 35. J. Nicholas Hoover (2009), Group Seeks Cloud Computing Standards (2009) http://www.
informationweek.com/news/government/cloud-saas/showArticle.jhtml?articleID=218500732. Accessed 11 Dec 2009
36. Object Management Group (OMG) (2009) http://www.omg.org/. Accessed 11 Dec 2009 37. OASIS (2009) http://www.oasis-open.org/. Accessed 11 Dec 2009
Part II
Cloud Seeding
Chapter 6
Open and Interoperable
Clouds: The Cloud@Home Way
Vincenzo D. Cunsolo, Salvatore Distefano, Antonio Puliafito,
and Marco Scarpa
Abstract Cloud computing focuses on the idea of service as the elementary unit for building any application. Even though Cloud computing was originally developed in commercial applications, the paradigm is quickly and widely spreading in open contexts such as scientific and academic communities. Two main research directions can thus be identified: provide an open Cloud infrastructure able to provide and share resources and services to the community; and implement an interoperable framework, allowing commercial and open Cloud infrastructures to interact and interoperate. In this chapter, we present the Cloud@Home paradigm that proposes to merge Volunteer and Cloud computing as an effective and feasible solution for building open and interoperable Clouds. In this new paradigm, users’ hosts are not passive interfaces to Cloud services anymore, but can interact (for free or by charge) with other Clouds, which therefore must be able to interoperate.
6.1 Introduction and Motivation
Cloud computing is a distributed computing paradigm that mixes aspects of Grid computing, Internet computing, Autonomic computing, Utility computing, and Green computing. Cloud computing is derived from the service-centric perspective that is quickly and widely spreading in the IT world. From this perspective, all capabilities and resources of a Cloud (usually geographically distributed) are provided to the users as a service, to be accessed through the Internet without any specific knowledge of, expertise with, or control over the underlying technology infrastructure that supports them.
Cloud computing offers a user-centric interface that acts as a unique, user friendly, point of access for users’ needs and requirements. Moreover, it provides
V.D. Cunsolo (*), S. Distefano, A. Puliafito, and M. Scarpa University of Messina, Contrada di Dio, 98166, S. Agata, Messina, Italy
e-mail: vdcunsolo@unime.it; sdistefano@unime.it; apuliafito@unime.it;mscarpa@unime.it
N. Antonopoulos and L. Gillam (eds.), Cloud Computing: Principles, |
93 |
Systems and Applications, Computer Communications and Networks,
DOI 10.1007/978-1-84996-241-4_6, © Springer-Verlag London Limited 2010
94 |
V.D. Cunsolo et al. |
on-demand service provision, QoS guaranteed offer, and autonomous system for managing hardware, software, and data transparency to the users [25].
In order to achieve such goals, it is necessary to implement a level of abstraction of physical resources, uniforming their interfaces, and providing means for their management, adaptively, to user requirements. This is done through virtualizations, service mashups (Web 2.0), and service-oriented architectures (SOA). These factors make the Kleinrock outlook of computing as the fifth utility [13], following gas, water, electricity, and telephone.
Virtualization [4,23] allows execution of a software version of a hardware machine in a host system in an isolated way. It “homogenizes” resources: problems of compatibility are overcome by providing heterogeneous hosts of a distributed computing environment (the Cloud) using the same virtual machine software.
Web 2.0 [20] provides an interesting way to interface Cloud services, implementing service mashups. It is mainly based on an evolution of JavaScript with improved language constructs (late binding, closures, lambda functions, etc.) and AJAX interactions.
SOA is a paradigm for organizing and utilizing distributed capabilities that may be under the control of different ownership domains [14]. In SOA, services are the mechanism by which needs and capabilities are brought together. SOA defines standard interfaces and protocols that allow developers to encapsulate information tools as services that clients can access without the knowledge of, or control over, their internal workings [8].
An interesting attempt to fix Cloud concepts and ideas is provided in [26] through an ontology that demonstrates a dissection of the Cloud into the five main layers shown in Fig. 6.1. In this, higher layers services can be composed from the services of the underlying layers, which are:
1.Cloud Application Layer: provides interface and access-management tools (Web 2.0, authentication, billing, SLA, etc.), specific application services, services mashup tools, etc. to the Cloud end users. This model is referred to as Software as a Service (SaaS).
Cloud Application
(SaaS)
|
Cloud Sw Environment |
|
|
|
(PaaS) |
Cloud Sw Infrastructure |
||
Computational |
Storage |
Communication |
Resources (IaaS) |
(DaaS) |
(CaaS) |
Sw Kernel
Firmware/Hardware
(HaaS)
Fig. 6.1 The five main layers of Cloud
6 Open and Interoperable Clouds: The Cloud@Home Way |
95 |
2.Cloud Software Environment Layer: providers of the Cloud software environments supply the users and Cloud applications’developers with a programming-language- level environment with a set of well-defined APIs. The services provided by this layer are referred to as Platform as a Service (PaaS).
3.Cloud Software Infrastructure Layer: provides fundamental resources to other higher-level layers. Services can be categorized into:
(a)Computational resources – provides computational resources (VM) to Cloud end users. Often, such services are dubbed Infrastructure as a Service (IaaS).
(b)Data storage – allows users to store their data at remote disks and access them anytime from any place. These services are commonly known as Data-Storage as a Service (DaaS).
(c)Communications – provides some communication capabilities that are service-oriented, configurable, schedulable, predictable, and reliable. The concept of Communication as a Service (CaaS) emerged toward this goal, to support such requirements.
OAP and REST are examples of interface protocols used with some Cloud computational resources.
4.Software Kernel: provides the basic software management for the physical servers that comprise the Cloud. OS kernel, hypervisor, virtual machine monitor, clustering, grid middleware, etc.
5.Hardware and Firmware: form the backbone of the Cloud. End users directly interacting with the Cloud at this layer have huge IT requirements in need of subleasing Hardware as a Service (HaaS).
Great interest in Cloud computing has been manifested from both academic and private research centers, and numerous projects from industry and academia have been proposed. In commercial contexts, among the others, we highlight: Amazon Elastic Compute Cloud, IBM’s Blue Cloud, Sun Microsystems Network.com, Microsoft Azure Services Platform, Dell Cloud computing solutions, etc. There are also several scientific activities driving toward Open Cloud-computing middlewares and infrastructures, such as: Reservoir [18], Nimbus-Stratus-Wispy-Kupa [22], OpenNebula [7], Eucalyptus [17], etc. All of them support and provide an on-demand computing paradigm, in the sense that a user submits his/her requests to the Cloud, which remotely, in a distributed fashion, processes them and gives back the results. This client–server model fits the aims and scope of commercial Clouds: the business. But, on the other hand, it represents a restriction for open/scientific Clouds, requiring great amounts of computing-storage resources usually not available from a single open/scientific community. This suggests the necessity to collect such resources from different providers and/or contributors who could share their resources with the specific community, perhaps by making “symbiotic” federations. In fact, one of the most successful paradigms in such contexts is Volunteer computing.
Volunteer computing (also called Peer-to-Peer computing, Global computing, or Public computing) uses computers volunteered by their owners as a source of computing power and storage to provide distributed scientific computing [2].