Presentazione di Massimo Ficco, della seconda università di Napoli, al Cloud Camp 2010 di Napoli. Evento organizzato da Vmengine

1. BUILDING A MOSAIC OF
CLOUDS
Second University of Naples, Italy - Coordinator
Beniamino Di Martino beniamino.dimartino@unina.it
Institute e-Austria Timisoara, Romania – Scientific Coordinator
Dana Petcu
European Space Agency, France
Terradue SRL, Italy
AITIA International Inc., Hungary
Fatronik Tecnalia, Spain

2. CONTENT
 SOTA and motivation
 Concepts
 mOSAIC promises
 Architectural details
 Implementation steps
19-20/10/2010IOSCollaborationMeeting

3. HOW WE DEVELOP A CLOUD-BASED
APPLICATION?
 High level
 Google App Engine
 Microsoft Azure Service Platform [or wait for Orleans]
 Manjrasoft Aneka
 Amazon Web Services
 Low level
 APIs offered by IaaS Cloud service providers
 to create and manage cloud resources, including compute,
storage, and networking components
 e.g. Amazon EC2, Eucalyptus, Sun Cloud, ElasticHosts,
FlexiScale, GoGrid, Enomaly, OpenNebula, SliceHost, Nimbus,
AppNexus, F5, Tashi, CohesiveFT, Mosso, Joyent ……
 So many! So different! This are the right APIs for the Cloud
appls?
19-20/10/2010IOSCollaborationMeeting

4. TOWARDS THE USAGE OF MULTIPLE
CLOUDS
 Portability
 At high level? NO!
 At low level? Ongoing task!
 OCCI – January 2010
 UniCluster, OpenStack … from Spring 2010
 Approaches:
 At IaaS level:
 Migration of VMs between Cloud providers (e.g. Reservoir)
 Agreements between Cloud providers
 Communications between Clouds
 At PaaS level:
 Use services from different Clouds
IOSCollaborationMeeting

5. SOTA - RESUME
 Lack of common programming model for Cloud-
oriented applications.
 Lack of tools for easy deployment of scalable
applications and (multi)-Cloud- based service
compositions.
 Lack of widely accepted standard interfaces for
resource virtualisation and management
 Lack of adequate service level agreements and
their dynamic negotiation
 Platform dependability and non-portability due
to different APIs for different types of resources
IOSCollaborationMeeting

6. SKY COMPUTING
 Emerging paradigm dealing with dynamically provisioning
of resources from distributed domains representing several
Cloud computing environments
[Keahey Ket al. Sky Computing. IEEE Internet Computing Sept. 2009]
 Key words: dynamic, several Clouds
 Analogy:
 Cluster computing with Cloud computing
 Grid computing with Sky computing
 Issues:
 Develop Cloud application independent from the IaaS level
 Ensure best offer selection and (re)negotiation
 Implementations?
 Theoretical studies about the offer selections and billing system
IOSCollaborationMeeting

7. REQUIREMENTS
 API at high level independent from the provider
 With implementation in high level languages
 Common representations of resources
 Cloud taxonomy and ontology
 Powerful platform allowing dynamicity and
 Identification of appl’s requirements in terms of resources
 (Re)Negotiation of the offers from different providers
 (Complex) billing component
 Monitoring and benchmarking
 Connectors to different services based on a common
understanding
IOSCollaborationMeeting

8. MOSAIC COMMITMENTS
 Title: Open-Source API and Platform for Multiple Clouds
 An API
 Cloud-based language- and platform-independent API
 Extends the existing language- or platform-dependent API
capabilities with composite features based on patterns
 A framework
 Semantic engine
 Cloud ontology & Semantic representation of Cloud resources
 Applications’s needs in terms of SLAs and QoS requirements
 Cloud agency
 An open-source platform
 a proof-of-the-concept prototype ready to be tested, exploited or
extended by its users
 include instances of the APIs for several programming
languages and application tools
! Proofs of validity through the use cases and applications

9. STARTING FROM CLOUD USE CASES
 Existing use cases
 OCCI use cases with IaaS API requirements
 Cloud Computing Use Case Discussion Group
 Provider’s use cases
 Research use casse
 mOSAIC’s use cases
Type Title
Data intensive Storage and data distribution in Earth Observation
Earth Observation mission reprocessing
Routine production of Earth Observation products
Fast data access for crisis situations
Distributed intelligent maintenance
Compute Cloud-distributed parameter sweep

10. MINIMAL FUNCTIONALITIES EXPOSED BY
API
Level Solution Examples of models
Storage File storage GoogleFS,HadoopFS,Amazon S3
Block storage DRBD
Column database Google BigTable, SimpleDB,
Berkeley DB, HBase
Communi
-cation
Message queues AmazonSQS, AMQP
RPC Web services, REST
Broadcast, multicast Ericsson TIPC
Streams HP SCTP
Synchronization
primitives
Semaphores, mutexes
Monitorin
g
Application status Ganglia framework
Resources Nagios monitoring

11. PLATFORM COMPONENTS

12. TIME LINE
 mOSAIC started on 1st September 2010
 First tasks:
 Architecture details
 Cloud usage patterns
 Own Cloud solution
Month Achievement
February 2011 Architecture and Cloud usage patterns
August 2011 1st API implementation, platform usage cases,
ontologies
February 2012 2nd API implementation and framework
August 2012 Platform available, first application package
February 2013 Full software package and proof-of-the-concept
applications