DOCSLIB.ORG

Experiences in Building a Mosaic of Clouds

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Experiences in Building a Mosaic of Clouds CORE Metadata, citation and similar papers at core.ac.uk Provided by Springer - Publisher Connector Petcu et al. Journal of Cloud Computing: Advances, Systems and Applications 2013, 2:12 http://www.journalofcloudcomputing.com/content/2/1/12 RESEARCH Open Access Experiences in building a mOSAIC of clouds Dana Petcu1*, Beniamino Di Martino2, Salvatore Venticinque2, Massimiliano Rak2, Tamás Máhr3, Gorka Esnal Lopez4,FabriceBrito5, Roberto Cossu6, Miha Stopar7, Svatopluk Šperka8 and Vlado Stankovski9 Abstract The diversity of Cloud computing services is challenging the application developers as various and non-standard interfaces are provided for these services. Few middleware solutions were developed until now to support the design, deployment and execution of service-independent applications as well as the management of resources from multiple Clouds. This paper focuses on one of these advanced middleware solutions, called mOSAIC. Written after the completion of its development, this paper presents an integrated overview of the mOSAIC approach and the use of its various software prototypes in a Cloud application development process. We are starting from the design concepts and arrive to various applications, as well as to the position versus similar initiatives. Introduction 2. Design a generic agent skeleton for representing The story of mOSAIC (Open-source API and Platform various stakeholders, e.g. Cloud vendors and their for Multiple Clouds) starts in Spring 2009 when its idea resources, Cloud users of various types, and a emerged. The main challenges for Cloud Computing iden- collection of modules that can be used to adapt agent tified to that moment, as shown in [1,2], were application skeleton to support needed functionalities. and data interoperability and portability, governance and 3. Design user-centric service level agreements, a Cloud management, metering and monitoring, as well as secu- ontology, and mechanisms for dynamic negotiation rity. In the meanwhile some partial solutions addressing of resources based on multi-agent technologies and these challenges have proposed, however, according to a semantic data processing. recent report [3], these challenges still exist. The key goal 4. Build an open-source and portable platform for using of mOSAIC is to offer a solution for application portability Cloud services based on the proposed API and Cloud and interoperability across multiple Clouds. However, the usage patterns. complete mOSAIC’ solution addresses partially also the 5. Build proof-of-concept applications with a special other challenges, management, governance, and security, emphasis on data intensive applications. as will be revealed in what follows. The mOSAIC’ solution is a result of a multi-national These scientific and technical goals were related with the team effort as part of a grant agreement with the European time’s lack of (a) common programming model for Cloud- Commission in the frame of FP7-ICT programme [4] oriented applications, (b) of tools for easy deployment (details on the project web site [5]). The implementation of scalable applications and (multi)-Cloud-based services, has started in September 2010 and the final software was (c) of standard representation for Cloud resources, (d) released in March 2013. The promises made in the early of adequate service level agreements and their dynamic stage of development were described in the position paper negotiation, (e) of application portability due to different ’Building a mOSAIC of Clouds’ [6]: APIs for Cloud services from different providers. A variety of reports on mOSAIC’s particular software 1. Design a language- and vendor-agnostic application solutions have been presented at recent scientific confer- programming interface for using multi-Cloud ences and in journal papers. The current paper intends resources and Cloud usage patterns. to provide an overview of the full and integrated solution with exhaustive references to literature where details can *Correspondence: [email protected] 1Institute e-Austria Timi¸soara and West University of Timi¸soara, Timi¸soara, be found. Therefore the main contribution of this paper Romania consists in the high-level description of the mOSAIC’s Full list of author information is available at the end of the article approach and the answers to the current challenges in © 2013 Petcu et al.; licensee Springer. This is an Open Access article distributed under the terms of the Creative Commons Attribution License (http://creativecommons.org/licenses/by/2.0), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited. Petcu et al. Journal of Cloud Computing: Advances, Systems and Applications 2013, 2:12 Page 2 of 22 http://www.journalofcloudcomputing.com/content/2/1/12 the Cloud computing domain by the mOSAIC’s technical on the number of its instances at run-time (has a degree solutions. of autonomy). The Cloudlets can get automatic support The paper is organized as follows. The first part is a for their life-cycle from the mOSAIC’s platform including description of the overall mOSAIC’s approach for solv- initialization, configuration and bindings to the needed ing the current problems of using multiple Clouds. The hardware and software resources. Moreover, Cloudlets second part concerns the mOSAIC’s positioning in the should be able to run in a Cloud environment indepen- landscape of Cloud computing services. The third part is dently from other components. Furthermore, Cloudlets dedicated to a discussion of the possible future develop- are started, stopped, replaced, or multiplied at run-time ments and improvements. for the application performance improvement. Multiple instances of the same Cloudlet are therefore expected to The mOSAIC’s approach be supported by an application. Consequently, the elastic- This section explains in details how the mOSAIC solution ity concept, specific for Cloud computing, is applied at the matches the key scientific and technical goals that were level of application in the mOSAIC approach. outlined in the introduction. The Cloudlets are able to access Cloud services through Connectors. The concept of Connector is introduced to APIs and patterns ensure the independence from the Cloud service inter- Several open API are already available (like jclouds, lib- faces. A Connector is a concrete class that abstract the cloud, OpenStack, most of them develop in parallel with access to Cloud resources and defines the set of events to mOSAIC) offering a management layer for the resources which the Cloudlet should react; its behavior is similar to of same type from multiple Clouds (based on a com- a remote procedure call, and it offers the functionality of mon denominator of their APIs). However the services the common denominator of a certain type of Cloud ser- are restricted to a specific language (like Java), a specific vice. For example, in the mOSAIC library for Java there is architectural style (like REST oriented) or specific type of only one Connector for key-value stores. resources (like virtual machines). The Connectors access Cloud services using Drivers. The Drivers are implementing the Cloud services inter- Component-based programming faces. They can be interpreted as wrappers of native The component model provides a natural abstraction for resource APIs or uniform APIs, like OpenStack. These programming and execution of Cloud applications, since wrappers are able to send and receive messages from the is lightweight and flexible in terms of APIs, according mOSAIC’s message queues. [7]. However, component frameworks that are expected The components of a mOSAIC application can be writ- to provide design-time and run-time infrastructures in ten in several different languages (Java, Python, Erlang, Clouds are few. A short preliminary analysis of the existing Node.js) and are able to communicate with each other solutions was done for mOSAIC positioning purpose and using a component bus (similar to CORBA’s one) and is reported in [8]. This analysis revealed that a proof-of- asynchronous communications (as being loosely coupled). concept implementation of a component framework for In particular, Connectors and Drivers can be written Clouds only for Java [9] was developed in parallel with in different languages. However, the Cloudlets that are mOSAIC. expressing the behavior of the applications are calling the ThemOSAIC’sAPIoffersasimplewaytodevelop Connectors – therefore the Connectors are expected to components which run on the top of its platform. The pro- be written in the same language as the Cloudlets (further gramming model of mOSAIC is based on using loosely details are provided in [13]). coupled components. A mOSAIC component represents an entity controlled by the user: the entity is configurable, A simple example exhibits a well defined behavior, implements application We assume that a software developer intends to built an dependent functionalities and exposes them to other com- application which is able to receive requests from the Web ponents. When an instance of a mOSAIC component runs (e.g. an XML file) to perform an analysis of the document in a Cloud environment, it consumes hardware or soft- (e.g. XML parsing) and to store the results in a Cloud ware resources, e.g. state-full resources hosted by Cloud storage. service provider and accessible through dedicated APIs. Such an application will be built easily using a pre- The communication among moSAIC components takes defined mOSAIC component which
Load more

Recommended publications
  • Security in Cloud Computing a Security Assessment of Cloud Computing Providers for an Online Receipt Storage
    Security in Cloud Computing A Security Assessment of Cloud Computing Providers for an Online Receipt Storage Mats Andreassen Kåre Marius Blakstad Master of Science in Computer Science Submission date: June 2010 Supervisor: Lillian Røstad, IDI Norwegian University of Science and Technology Department of Computer and Information Science Problem Description We will survey some current cloud computing vendors and compare them to find patterns in how their feature sets are evolving. The start-up firm dSafe intends to exploit the promises of cloud computing in order to launch their business idea with only marginal hardware and licensing costs. We must define the criteria for how dSafe's application can be sufficiently secure in the cloud as well as how dSafe can get there. Assignment given: 14. January 2010 Supervisor: Lillian Røstad, IDI Abstract Considerations with regards to security issues and demands must be addressed before migrating an application into a cloud computing environment. Different vendors, Microsoft Azure, Amazon Web Services and Google AppEngine, provide different capabilities and solutions to the individual areas of concern presented by each application. Through a case study of an online receipt storage application from the company dSafe, a basis is formed for the evaluation. The three cloud computing vendors are assessed with regards to a security assessment framework provided by the Cloud Security Alliance and the application of this on the case study. Finally, the study is concluded with a set of general recommendations and the recommendation of a cloud vendor. This is based on a number of security as- pects related to the case study’s existence in the cloud.
    [Show full text]
  • Google Is a Strong Performer in Enterprise Public Cloud Platforms Excerpted from the Forrester Wave™: Enterprise Public Cloud Platforms, Q4 2014 by John R
    FOR CIOS DECEMBER 29, 2014 Google Is A Strong Performer In Enterprise Public Cloud Platforms Excerpted From The Forrester Wave™: Enterprise Public Cloud Platforms, Q4 2014 by John R. Rymer and James Staten with Peter Burris, Christopher Mines, and Dominique Whittaker GOOGLE, NOW A FULL-SERVICE PLATFORM, IS RUNNING TO CATCH THE LEADERS Since our last analysis, Google has made significant improvements to its cloud platform — adding an IaaS service, innovated with new big data solutions (based on its homegrown dremel architecture), and added partners. Google is popular among web developers — we estimate that it has between 10,000 and 99,000 customers. But Google Cloud Platform lacks several key certifications, monitoring and security controls, and application services important to CIOs and provided by AWS and Microsoft.1 Google has also been slow to position its cloud platform as the home for applications that want to leverage the broad set of Google services such as Android, AdSense, Search, Maps, and so many other technologies. Look for that to be a key focus in 2015, and for a faster cadence of new features. Forrester Wave™: Enterprise Public Cloud Forrester Wave™: Enterprise Public Cloud Platforms For CIOs, Q4 ‘14 Platforms For Rapid Developers, Q4 ‘14 Risky Strong Risky Strong Bets Contenders Performers Leaders Bets Contenders Performers Leaders Strong Strong Amazon Web Services MIOsoft Microsoft Salesforce Cordys* Mendix MIOsoft Salesforce (Q2 2013) OutSystems OutSystems Google Mendix Acquia Current Rackspace* IBM Current offering (Q2 2013) offering Cordys* (Q2 2013) Engine Yard Acquia CenturyLink Google, with a Forrester score of 2.35, is a Strong Performer in this Dimension Data GoGrid Forrester Wave.
    [Show full text]
  • Open Cloud Computing with the Simple Cloud API and Apache Libcloud Doug Tidwell Cloud Computing Evangelist, IBM [email protected]
    Open Cloud Computing with the Simple Cloud API and Apache libcloud Doug Tidwell Cloud Computing Evangelist, IBM [email protected] Session 7665 Agenda • Portability and interoperability • A few words about APIs • The Simple Cloud API • Storage • Queues • Documents • Controlling VMs with Apache libcloud • Resources / Next steps The problem Vendor lock-in • If there’s a new technology, any talented programmer will want to use it. • Maybe the shiny new thing is appropriate for what we’re doing. • Maybe not. • We’re probably going to use it anyway. • The challenge is to walk the line between using the newest, coolest thing and avoiding vendor lock-in. Portability and Interoperability • In writing flexible code for the cloud, there are two key concepts: • Portability is the ability to run components or systems written for one cloud provider in another cloud provider’s environment. • Interoperability is the ability to write one piece of code that works with multiple cloud providers, regardless of the differences between them. How standards work • For a standards effort to work, three things have to happen: • The standard has to solve a common problem in an elegant way. • The standard has to be implemented consistently by vendors. • Users have to insist that the products they use implement the standard. How standards work • All three things have to happen. • If the standard doesn't solve a common problem, or if it solves it in an awkward way, the standard fails. • If the standard isn't implemented by anyone, the standard fails. • If customers buy and use products even though they don't implement the standard, the standard fails.
    [Show full text]
  • Software As a Service
    Software as a Service Haojie Hang Ogheneovo Dibie Executive Summary • In this presentation, we go through the Software as a Service Methodology, examine its benefits and drawbacks and talk about two state-of-art SaaS systems– Amazon Web Service and Google App Engine • We also look into Service Oriented Architecture powering SaaS applications and its impact on modern web 2.0 applications • Finally, we examine hybrids of traditional and SaaS applications Overview • What is Software as a Service (SaaS) • Background o Brief history o Concept o Big picture o Related terms • Computing Today o SasS is everywhere o The SaaS Market • Benefits of SaaS • Drawbacks of SaaS o Robustness o Privacy o Security o Reliability • Service Oriented Architectures (SOA) o Guiding principles of SOA • Case studies o Amazon Web Services (AWS) o Google App Engine • Influence of SOA on Web 2.0 development o Zend Framework • Hybrids of Traditional and SaaS applications o Dropbox o Microsoft Office • Summary • References What is SaaS? • Definition: Software as a Service (SaaS), a.k.a. on- demand software, is a software delivery model in which software and its associated data are hosted centrally and accessed using a thin-client, usually a web browser over the internet. – Wikipedia • Simply put, SaaS is a method for delivering software that provides remote access to software as a web- based service. The software service can be purchased with a monthly fee and pay as you go. What is SaaS? • Where does the term SaaS come from? o The SAAS acronym allegedly first appeared
    [Show full text]
  • Deliverable No. 5.3 Techniques to Build the Cloud Infrastructure Available to the Community
    Deliverable No. 5.3 Techniques to build the cloud infrastructure available to the community Grant Agreement No.: 600841 Deliverable No.: D5.3 Deliverable Name: Techniques to build the cloud infrastructure available to the community Contractual Submission Date: 31/03/2015 Actual Submission Date: 31/03/2015 Dissemination Level PU Public X PP Restricted to other programme participants (including the Commission Services) RE Restricted to a group specified by the consortium (including the Commission Services) CO Confidential, only for members of the consortium (including the Commission Services) Grant Agreement no. 600841 D5.3 – Techniques to build the cloud infrastructure available to the community COVER AND CONTROL PAGE OF DOCUMENT Project Acronym: CHIC Project Full Name: Computational Horizons In Cancer (CHIC): Developing Meta- and Hyper-Multiscale Models and Repositories for In Silico Oncology Deliverable No.: D5.3 Document name: Techniques to build the cloud infrastructure available to the community Nature (R, P, D, O)1 R Dissemination Level (PU, PP, PU RE, CO)2 Version: 1.0 Actual Submission Date: 31/03/2015 Editor: Manolis Tsiknakis Institution: FORTH E-Mail: [email protected] ABSTRACT: This deliverable reports on the technologies, techniques and configuration needed to install, configure, maintain and run a private cloud infrastructure for productive usage. KEYWORD LIST: Cloud infrastructure, OpenStack, Eucalyptus, CloudStack, VMware vSphere, virtualization, computation, storage, security, architecture. The research leading to these results has received funding from the European Community's Seventh Framework Programme (FP7/2007-2013) under grant agreement no 600841. The author is solely responsible for its content, it does not represent the opinion of the European Community and the Community is not responsible for any use that might be made of data appearing therein.
    [Show full text]
  • Dell Openstack Cloud Solution
    Dell OpenStack Cloud Solution Peter Jung Senior Solutions Architect & Business Developer Fast. Easy. Now. Dell.com/OpenStack Dell.com/Crowbar Cloud expectations and promises Support the mobile & social marketplace Innovate and grow and workforce Anytime, anywhere, on any device access and Speed time to market when introducing new engagement. (BYOD) increases productivity and goods and services job satisfaction Apps Revenue Data “The Business” BI Cost Speed Efficiency Attract & retain new customers Reduce IT cost, deliver operational results On-demand, self-service and automated access Connect customer data, gain intelligence on lowers costs and decreases demands on IT customers to better target, nurture and solidify leads Cloud - Challenges for SP and Enterprise Service provider challenges Enterprise challenges • Cost-effectively scaling, and competing in the • Lack of infrastructure standardization and emerging public cloud ecosystem automation leading to poor resource utilization, cost escalation, slow application delivery • Ability to quickly launch new cloud services • Locked-in to proprietary vendors and • Keeping license costs down on traditional technologies – increasing license costs with virtualization solutions – costs increase linearly growth and scale with scale (often per node) • Poor understanding of cost allocations • Keeping maintenance costs down on home- grown components that have been built • Long resource provisioning cycle times haphazardly over time • Inflexible and non-adaptive infrastructure • Flexibility to rapidly add/change features in response to customer needs –commercial • Building a cloud is too complex and takes too solutions lack features they need long • Lack of availability and support of the entire end-to-end solution Cloud Taxonomy – Complex? Cloud service PaaS/SaaS management PaaS/SaaS services sit on top of this stack along with other any specific vertical solutions such as VDI, HPC, CDN etc.
    [Show full text]
  • D1.5 Final Business Models
    ITEA 2 Project 10014 EASI-CLOUDS - Extended Architecture and Service Infrastructure for Cloud-Aware Software Deliverable D1.5 – Final Business Models for EASI-CLOUDS Task 1.3: Business model(s) for the EASI-CLOUDS eco-system Editor: Atos, Gearshift Security public Version 1.0 Melanie Jekal, Alexander Krebs, Markku Authors Nurmela, Juhana Peltonen, Florian Röhr, Jan-Frédéric Plogmeier, Jörn Altmann, (alphabetically) Maurice Gagnaire, Mario Lopez-Ramos Pages 95 Deliverable 1.5 – Final Business Models for EASI-CLOUDS v1.0 Abstract The purpose of the business working group within the EASI-CLOUDS project is to investigate the commercial potential of the EASI-CLOUDS platform, and the brokerage and federation- based business models that it would help to enable. Our described approach is both ‘top down’ and ‘bottom up’; we begin by summarizing existing studies on the cloud market, and review how the EASI-CLOUDS project partners are positioned on the cloud value chain. We review emerging trends, concepts, business models and value drivers in the cloud market, and present results from a survey targeted at top cloud bloggers and cloud professionals. We then review how the EASI-CLOUDS infrastructure components create value both directly and by facilitating brokerage and federation. We then examine how cloud market opportunities can be grasped through different business models. Specifically, we examine value creation and value capture in different generic business models that may benefit from the EASI-CLOUDS infrastructure. We conclude by providing recommendations on how the different EASI-CLOUDS demonstrators may be commercialized through different business models. © EASI-CLOUDS Consortium. 2 Deliverable 1.5 – Final Business Models for EASI-CLOUDS v1.0 Table of contents Table of contents ...........................................................................................................................
    [Show full text]
  • Cloud Computing: a Taxonomy of Platform and Infrastructure-Level Offerings David Hilley College of Computing Georgia Institute of Technology
    Cloud Computing: A Taxonomy of Platform and Infrastructure-level Offerings David Hilley College of Computing Georgia Institute of Technology April 2009 Cloud Computing: A Taxonomy of Platform and Infrastructure-level Offerings David Hilley 1 Introduction Cloud computing is a buzzword and umbrella term applied to several nascent trends in the turbulent landscape of information technology. Computing in the “cloud” alludes to ubiquitous and inexhaustible on-demand IT resources accessible through the Internet. Practically every new Internet-based service from Gmail [1] to Amazon Web Services [2] to Microsoft Online Services [3] to even Facebook [4] have been labeled “cloud” offerings, either officially or externally. Although cloud computing has garnered significant interest, factors such as unclear terminology, non-existent product “paper launches”, and opportunistic marketing have led to a significant lack of clarity surrounding discussions of cloud computing technology and products. The need for clarity is well-recognized within the industry [5] and by industry observers [6]. Perhaps more importantly, due to the relative infancy of the industry, currently-available product offerings are not standardized. Neither providers nor potential consumers really know what a “good” cloud computing product offering should look like and what classes of products are appropriate. Consequently, products are not easily comparable. The scope of various product offerings differ and overlap in complicated ways – for example, Ama- zon’s EC2 service [7] and Google’s App Engine [8] partially overlap in scope and applicability. EC2 is more flexible but also lower-level, while App Engine subsumes some functionality in Amazon Web Services suite of offerings [2] external to EC2.
    [Show full text]
  • Cutter IT Journal
    Cutter The Journal of IT Journal Information Technology Management Vol. 26, No. 3 March 2013 “Cloud service providers, the IT industry, professional The Emerging Cloud Ecosystem: and industry associations, governments, and IT pro- Innovative New Services and fessionals all have a role to Business Models play in shaping, fostering, and harnessing the full potential of the emerging cloud ecosystem.” Opening Statement — San Murugesan, by San Murugesan . 3 Guest Editor Merging IaaS with PaaS to Deliver Robust Development Tools by Beth Cohen . 6 Intrusion Detection as a Service (IDaaS) in an Open Source Cloud Infrastructure by John Prakash Veigas and K Chandra Sekaran . 12 Cloud Ecology: Surviving in the Jungle by Claude R. Baudoin . 19 The Promise of a Diverse, Interoperable Cloud Ecosystem — And Recommendations for Realizing It by Kathy L. Grise . 26 NOT FOR DISTRIBUTION For authorized use, contact Cutter Consortium: +1 781 648 8700 [email protected] Cutter IT Journal About Cutter IT Journal Cutter IT Journal® Cutter Business Technology Council: Part of Cutter Consortium’s mission is to Cutter IT Journal subscribers consider the Rob Austin, Ron Blitstein, Tom DeMarco, Lynne Ellyn, Israel Gat, Vince Kellen, foster debate and dialogue on the business Journal a “consultancy in print” and liken Tim Lister, Lou Mazzucchelli, technology issues challenging enterprises each month’s issue to the impassioned Ken Orr, and Robert D. Scott today, helping organizations leverage IT for debates they participate in at the end of Editor Emeritus: Ed Yourdon competitive advantage and business success. a day at a conference. Publisher: Karen Fine Coburn Cutter’s philosophy is that most of the issues Group Publisher: Chris Generali that managers face are complex enough to Every facet of IT — application integration, Managing Editor: Karen Pasley merit examination that goes beyond simple security, portfolio management, and testing, Production Editor: Linda M.
    [Show full text]
  • Cloud Computing Bible Is a Wide-Ranging and Complete Reference
    A thorough, down-to-earth look Barrie Sosinsky Cloud Computing Barrie Sosinsky is a veteran computer book writer at cloud computing specializing in network systems, databases, design, development, The chance to lower IT costs makes cloud computing a and testing. Among his 35 technical books have been Wiley’s Networking hot topic, and it’s getting hotter all the time. If you want Bible and many others on operating a terra firma take on everything you should know about systems, Web topics, storage, and the cloud, this book is it. Starting with a clear definition of application software. He has written nearly 500 articles for computer what cloud computing is, why it is, and its pros and cons, magazines and Web sites. Cloud Cloud Computing Bible is a wide-ranging and complete reference. You’ll get thoroughly up to speed on cloud platforms, infrastructure, services and applications, security, and much more. Computing • Learn what cloud computing is and what it is not • Assess the value of cloud computing, including licensing models, ROI, and more • Understand abstraction, partitioning, virtualization, capacity planning, and various programming solutions • See how to use Google®, Amazon®, and Microsoft® Web services effectively ® ™ • Explore cloud communication methods — IM, Twitter , Google Buzz , Explore the cloud with Facebook®, and others • Discover how cloud services are changing mobile phones — and vice versa this complete guide Understand all platforms and technologies www.wiley.com/compbooks Shelving Category: Use Google, Amazon, or
    [Show full text]
  • An Lc-Tools Tutirial
    An lc-tools Tutirial Roman Bogorodskiy [email protected] May 30, 2011 Contents 0.1 Introduction An lc-tools is a set of command line tools to manage various Cloud (aka IaaS) Providers. It’s written in Python and uses libcloud to interact with provider’s API.xx 0.2 Getting Started 0.2.1 Installing Dependencies The only external dependency is libcloud. Please visit libcloud download page to get information how to download and install it. Installing from PyPI Latest stable version of lc-tools could be installed from PyPI: easy_install lctools Installing from source To get latest development version you can checkout sources from project’s github page: git clone https://github.com/novel/lc-tools.git Now you should have all the sources and should be ready to proceed to installation. As lc-tools use setuptools installation process is fairly simple: $ cd lc-tools $ sudo python setup.py install This will install all the tools and you will be able to use them after configu- ration (you will know how to configure lc-tools in the next section: ??). However, there are some additional tools available in lc-tools that’s not installed by default – it’s various provider specific tools. 1 What are provider specific tools, you might ask. You see, libcloud is de- signed to provide an unified API to the cloud, so its model is almost an inter- section of APIs of various cloud providers. However, various provider can have its specific API calls, for example, provider Foo might have a call to return information how many servers could be created in your current account or, say, what’s the maximum allowed rate of requests to the API per minute.
    [Show full text]
  • Understanding the Cloud Computing Landscape
    Chapter 1 Understanding the Cloud Computing Landscape Lamia Youseff, Dilma M. Da Silva, Maria Butrico, and Jonathan Appavoo Contents 1.1 Introduction .................................................................................................2 1.2 Cloud Systems Classifications ......................................................................2 1.3 SPI Cloud Classification ...............................................................................2 1.3.1 Cloud Software Systems ...................................................................3 1.3.2 Cloud Platform Systems ....................................................................3 1.3.3 Cloud Infrastructure Systems ...........................................................4 1.4 UCSB-IBM Cloud Ontology .......................................................................4 1.4.1 Applications (SaaS) ...........................................................................5 1.4.2 Cloud Software Environment (PaaS) ................................................7 1.4.3 Cloud Software Infrastructure ..........................................................8 1.4.4 Software Kernel Layer .......................................................................9 1.4.5 Cloud Hardware/Firmware ...............................................................9 1.5 Jackson’s Expansion on the UCSB-IBM Ontology .....................................10 1.6 Hoff’s Cloud Model ...................................................................................11 1.7 Discussion ..................................................................................................13
    [Show full text]