- •Cloud Computing
- •Foreword
- •Preface
- •Introduction
- •Expected Audience
- •Book Overview
- •Part 1: Cloud Base
- •Part 2: Cloud Seeding
- •Part 3: Cloud Breaks
- •Part 4: Cloud Feedback
- •Contents
- •1.1 Introduction
- •1.1.1 Cloud Services and Enabling Technologies
- •1.2 Virtualization Technology
- •1.2.1 Virtual Machines
- •1.2.2 Virtualization Platforms
- •1.2.3 Virtual Infrastructure Management
- •1.2.4 Cloud Infrastructure Manager
- •1.3 The MapReduce System
- •1.3.1 Hadoop MapReduce Overview
- •1.4 Web Services
- •1.4.1 RPC (Remote Procedure Call)
- •1.4.2 SOA (Service-Oriented Architecture)
- •1.4.3 REST (Representative State Transfer)
- •1.4.4 Mashup
- •1.4.5 Web Services in Practice
- •1.5 Conclusions
- •References
- •2.1 Introduction
- •2.2 Background and Related Work
- •2.3 Taxonomy of Cloud Computing
- •2.3.1 Cloud Architecture
- •2.3.1.1 Services and Modes of Cloud Computing
- •Software-as-a-Service (SaaS)
- •Platform-as-a-Service (PaaS)
- •Hardware-as-a-Service (HaaS)
- •Infrastructure-as-a-Service (IaaS)
- •2.3.2 Virtualization Management
- •2.3.3 Core Services
- •2.3.3.1 Discovery and Replication
- •2.3.3.2 Load Balancing
- •2.3.3.3 Resource Management
- •2.3.4 Data Governance
- •2.3.4.1 Interoperability
- •2.3.4.2 Data Migration
- •2.3.5 Management Services
- •2.3.5.1 Deployment and Configuration
- •2.3.5.2 Monitoring and Reporting
- •2.3.5.3 Service-Level Agreements (SLAs) Management
- •2.3.5.4 Metering and Billing
- •2.3.5.5 Provisioning
- •2.3.6 Security
- •2.3.6.1 Encryption/Decryption
- •2.3.6.2 Privacy and Federated Identity
- •2.3.6.3 Authorization and Authentication
- •2.3.7 Fault Tolerance
- •2.4 Classification and Comparison between Cloud Computing Ecosystems
- •2.5 Findings
- •2.5.2 Cloud Computing PaaS and SaaS Provider
- •2.5.3 Open Source Based Cloud Computing Services
- •2.6 Comments on Issues and Opportunities
- •2.7 Conclusions
- •References
- •3.1 Introduction
- •3.2 Scientific Workflows and e-Science
- •3.2.1 Scientific Workflows
- •3.2.2 Scientific Workflow Management Systems
- •3.2.3 Important Aspects of In Silico Experiments
- •3.3 A Taxonomy for Cloud Computing
- •3.3.1 Business Model
- •3.3.2 Privacy
- •3.3.3 Pricing
- •3.3.4 Architecture
- •3.3.5 Technology Infrastructure
- •3.3.6 Access
- •3.3.7 Standards
- •3.3.8 Orientation
- •3.5 Taxonomies for Cloud Computing
- •3.6 Conclusions and Final Remarks
- •References
- •4.1 Introduction
- •4.2 Cloud and Grid: A Comparison
- •4.2.1 A Retrospective View
- •4.2.2 Comparison from the Viewpoint of System
- •4.2.3 Comparison from the Viewpoint of Users
- •4.2.4 A Summary
- •4.3 Examining Cloud Computing from the CSCW Perspective
- •4.3.1 CSCW Findings
- •4.3.2 The Anatomy of Cloud Computing
- •4.3.2.1 Security and Privacy
- •4.3.2.2 Data and/or Vendor Lock-In
- •4.3.2.3 Service Availability/Reliability
- •4.4 Conclusions
- •References
- •5.1 Overview – Cloud Standards – What and Why?
- •5.2 Deep Dive: Interoperability Standards
- •5.2.1 Purpose, Expectations and Challenges
- •5.2.2 Initiatives – Focus, Sponsors and Status
- •5.2.3 Market Adoption
- •5.2.4 Gaps/Areas of Improvement
- •5.3 Deep Dive: Security Standards
- •5.3.1 Purpose, Expectations and Challenges
- •5.3.2 Initiatives – Focus, Sponsors and Status
- •5.3.3 Market Adoption
- •5.3.4 Gaps/Areas of Improvement
- •5.4 Deep Dive: Portability Standards
- •5.4.1 Purpose, Expectations and Challenges
- •5.4.2 Initiatives – Focus, Sponsors and Status
- •5.4.3 Market Adoption
- •5.4.4 Gaps/Areas of Improvement
- •5.5.1 Purpose, Expectations and Challenges
- •5.5.2 Initiatives – Focus, Sponsors and Status
- •5.5.3 Market Adoption
- •5.5.4 Gaps/Areas of Improvement
- •5.6 Deep Dive: Other Key Standards
- •5.6.1 Initiatives – Focus, Sponsors and Status
- •5.7 Closing Notes
- •References
- •6.1 Introduction and Motivation
- •6.2 Cloud@Home Overview
- •6.2.1 Issues, Challenges, and Open Problems
- •6.2.2 Basic Architecture
- •6.2.2.1 Software Environment
- •6.2.2.2 Software Infrastructure
- •6.2.2.3 Software Kernel
- •6.2.2.4 Firmware/Hardware
- •6.2.3 Application Scenarios
- •6.3 Cloud@Home Core Structure
- •6.3.1 Management Subsystem
- •6.3.2 Resource Subsystem
- •6.4 Conclusions
- •References
- •7.1 Introduction
- •7.2 MapReduce
- •7.3 P2P-MapReduce
- •7.3.1 Architecture
- •7.3.2 Implementation
- •7.3.2.1 Basic Mechanisms
- •Resource Discovery
- •Network Maintenance
- •Job Submission and Failure Recovery
- •7.3.2.2 State Diagram and Software Modules
- •7.3.3 Evaluation
- •7.4 Conclusions
- •References
- •8.1 Introduction
- •8.2 The Cloud Evolution
- •8.3 Improved Network Support for Cloud Computing
- •8.3.1 Why the Internet is Not Enough?
- •8.3.2 Transparent Optical Networks for Cloud Applications: The Dedicated Bandwidth Paradigm
- •8.4 Architecture and Implementation Details
- •8.4.1 Traffic Management and Control Plane Facilities
- •8.4.2 Service Plane and Interfaces
- •8.4.2.1 Providing Network Services to Cloud-Computing Infrastructures
- •8.4.2.2 The Cloud Operating System–Network Interface
- •8.5.1 The Prototype Details
- •8.5.1.1 The Underlying Network Infrastructure
- •8.5.1.2 The Prototype Cloud Network Control Logic and its Services
- •8.5.2 Performance Evaluation and Results Discussion
- •8.6 Related Work
- •8.7 Conclusions
- •References
- •9.1 Introduction
- •9.2 Overview of YML
- •9.3 Design and Implementation of YML-PC
- •9.3.1 Concept Stack of Cloud Platform
- •9.3.2 Design of YML-PC
- •9.3.3 Core Design and Implementation of YML-PC
- •9.4 Primary Experiments on YML-PC
- •9.4.1 YML-PC Can Be Scaled Up Very Easily
- •9.4.2 Data Persistence in YML-PC
- •9.4.3 Schedule Mechanism in YML-PC
- •9.5 Conclusion and Future Work
- •References
- •10.1 Introduction
- •10.2 Related Work
- •10.2.1 General View of Cloud Computing frameworks
- •10.2.2 Cloud Computing Middleware
- •10.3 Deploying Applications in the Cloud
- •10.3.1 Benchmarking the Cloud
- •10.3.2 The ProActive GCM Deployment
- •10.3.3 Technical Solutions for Deployment over Heterogeneous Infrastructures
- •10.3.3.1 Virtual Private Network (VPN)
- •10.3.3.2 Amazon Virtual Private Cloud (VPC)
- •10.3.3.3 Message Forwarding and Tunneling
- •10.3.4 Conclusion and Motivation for Mixing
- •10.4 Moving HPC Applications from Grids to Clouds
- •10.4.1 HPC on Heterogeneous Multi-Domain Platforms
- •10.4.2 The Hierarchical SPMD Concept and Multi-level Partitioning of Numerical Meshes
- •10.4.3 The GCM/ProActive-Based Lightweight Framework
- •10.4.4 Performance Evaluation
- •10.5 Dynamic Mixing of Clusters, Grids, and Clouds
- •10.5.1 The ProActive Resource Manager
- •10.5.2 Cloud Bursting: Managing Spike Demand
- •10.5.3 Cloud Seeding: Dealing with Heterogeneous Hardware and Private Data
- •10.6 Conclusion
- •References
- •11.1 Introduction
- •11.2 Background
- •11.2.1 ASKALON
- •11.2.2 Cloud Computing
- •11.3 Resource Management Architecture
- •11.3.1 Cloud Management
- •11.3.2 Image Catalog
- •11.3.3 Security
- •11.4 Evaluation
- •11.5 Related Work
- •11.6 Conclusions and Future Work
- •References
- •12.1 Introduction
- •12.2 Layered Peer-to-Peer Cloud Provisioning Architecture
- •12.4.1 Distributed Hash Tables
- •12.4.2 Designing Complex Services over DHTs
- •12.5 Cloud Peer Software Fabric: Design and Implementation
- •12.5.1 Overlay Construction
- •12.5.2 Multidimensional Query Indexing
- •12.5.3 Multidimensional Query Routing
- •12.6 Experiments and Evaluation
- •12.6.1 Cloud Peer Details
- •12.6.3 Test Application
- •12.6.4 Deployment of Test Services on Amazon EC2 Platform
- •12.7 Results and Discussions
- •12.8 Conclusions and Path Forward
- •References
- •13.1 Introduction
- •13.2 High-Throughput Science with the Nimrod Tools
- •13.2.1 The Nimrod Tool Family
- •13.2.2 Nimrod and the Grid
- •13.2.3 Scheduling in Nimrod
- •13.3 Extensions to Support Amazon’s Elastic Compute Cloud
- •13.3.1 The Nimrod Architecture
- •13.3.2 The EC2 Actuator
- •13.3.3 Additions to the Schedulers
- •13.4.1 Introduction and Background
- •13.4.2 Computational Requirements
- •13.4.3 The Experiment
- •13.4.4 Computational and Economic Results
- •13.4.5 Scientific Results
- •13.5 Conclusions
- •References
- •14.1 Using the Cloud
- •14.1.1 Overview
- •14.1.2 Background
- •14.1.3 Requirements and Obligations
- •14.1.3.1 Regional Laws
- •14.1.3.2 Industry Regulations
- •14.2 Cloud Compliance
- •14.2.1 Information Security Organization
- •14.2.2 Data Classification
- •14.2.2.1 Classifying Data and Systems
- •14.2.2.2 Specific Type of Data of Concern
- •14.2.2.3 Labeling
- •14.2.3 Access Control and Connectivity
- •14.2.3.1 Authentication and Authorization
- •14.2.3.2 Accounting and Auditing
- •14.2.3.3 Encrypting Data in Motion
- •14.2.3.4 Encrypting Data at Rest
- •14.2.4 Risk Assessments
- •14.2.4.1 Threat and Risk Assessments
- •14.2.4.2 Business Impact Assessments
- •14.2.4.3 Privacy Impact Assessments
- •14.2.5 Due Diligence and Provider Contract Requirements
- •14.2.5.1 ISO Certification
- •14.2.5.2 SAS 70 Type II
- •14.2.5.3 PCI PA DSS or Service Provider
- •14.2.5.4 Portability and Interoperability
- •14.2.5.5 Right to Audit
- •14.2.5.6 Service Level Agreements
- •14.2.6 Other Considerations
- •14.2.6.1 Disaster Recovery/Business Continuity
- •14.2.6.2 Governance Structure
- •14.2.6.3 Incident Response Plan
- •14.3 Conclusion
- •Bibliography
- •15.1.1 Location of Cloud Data and Applicable Laws
- •15.1.2 Data Concerns Within a European Context
- •15.1.3 Government Data
- •15.1.4 Trust
- •15.1.5 Interoperability and Standardization in Cloud Computing
- •15.1.6 Open Grid Forum’s (OGF) Production Grid Interoperability Working Group (PGI-WG) Charter
- •15.1.7.1 What will OCCI Provide?
- •15.1.7.2 Cloud Data Management Interface (CDMI)
- •15.1.7.3 How it Works
- •15.1.8 SDOs and their Involvement with Clouds
- •15.1.10 A Microsoft Cloud Interoperability Scenario
- •15.1.11 Opportunities for Public Authorities
- •15.1.12 Future Market Drivers and Challenges
- •15.1.13 Priorities Moving Forward
- •15.2 Conclusions
- •References
- •16.1 Introduction
- •16.2 Cloud Computing (‘The Cloud’)
- •16.3 Understanding Risks to Cloud Computing
- •16.3.1 Privacy Issues
- •16.3.2 Data Ownership and Content Disclosure Issues
- •16.3.3 Data Confidentiality
- •16.3.4 Data Location
- •16.3.5 Control Issues
- •16.3.6 Regulatory and Legislative Compliance
- •16.3.7 Forensic Evidence Issues
- •16.3.8 Auditing Issues
- •16.3.9 Business Continuity and Disaster Recovery Issues
- •16.3.10 Trust Issues
- •16.3.11 Security Policy Issues
- •16.3.12 Emerging Threats to Cloud Computing
- •16.4 Cloud Security Relationship Framework
- •16.4.1 Security Requirements in the Clouds
- •16.5 Conclusion
- •References
- •17.1 Introduction
- •17.1.1 What Is Security?
- •17.2 ISO 27002 Gap Analyses
- •17.2.1 Asset Management
- •17.2.2 Communications and Operations Management
- •17.2.4 Information Security Incident Management
- •17.2.5 Compliance
- •17.3 Security Recommendations
- •17.4 Case Studies
- •17.4.1 Private Cloud: Fortune 100 Company
- •17.4.2 Public Cloud: Amazon.com
- •17.5 Summary and Conclusion
- •References
- •18.1 Introduction
- •18.2 Decoupling Policy from Applications
- •18.2.1 Overlap of Concerns Between the PEP and PDP
- •18.2.2 Patterns for Binding PEPs to Services
- •18.2.3 Agents
- •18.2.4 Intermediaries
- •18.3 PEP Deployment Patterns in the Cloud
- •18.3.1 Software-as-a-Service Deployment
- •18.3.2 Platform-as-a-Service Deployment
- •18.3.3 Infrastructure-as-a-Service Deployment
- •18.3.4 Alternative Approaches to IaaS Policy Enforcement
- •18.3.5 Basic Web Application Security
- •18.3.6 VPN-Based Solutions
- •18.4 Challenges to Deploying PEPs in the Cloud
- •18.4.1 Performance Challenges in the Cloud
- •18.4.2 Strategies for Fault Tolerance
- •18.4.3 Strategies for Scalability
- •18.4.4 Clustering
- •18.4.5 Acceleration Strategies
- •18.4.5.1 Accelerating Message Processing
- •18.4.5.2 Acceleration of Cryptographic Operations
- •18.4.6 Transport Content Coding
- •18.4.7 Security Challenges in the Cloud
- •18.4.9 Binding PEPs and Applications
- •18.4.9.1 Intermediary Isolation
- •18.4.9.2 The Protected Application Stack
- •18.4.10 Authentication and Authorization
- •18.4.11 Clock Synchronization
- •18.4.12 Management Challenges in the Cloud
- •18.4.13 Audit, Logging, and Metrics
- •18.4.14 Repositories
- •18.4.15 Provisioning and Distribution
- •18.4.16 Policy Synchronization and Views
- •18.5 Conclusion
- •References
- •19.1 Introduction and Background
- •19.2 A Media Service Cloud for Traditional Broadcasting
- •19.2.1 Gridcast the PRISM Cloud 0.12
- •19.3 An On-demand Digital Media Cloud
- •19.4 PRISM Cloud Implementation
- •19.4.1 Cloud Resources
- •19.4.2 Cloud Service Deployment and Management
- •19.5 The PRISM Deployment
- •19.6 Summary
- •19.7 Content Note
- •References
- •20.1 Cloud Computing Reference Model
- •20.2 Cloud Economics
- •20.2.1 Economic Context
- •20.2.2 Economic Benefits
- •20.2.3 Economic Costs
- •20.2.5 The Economics of Green Clouds
- •20.3 Quality of Experience in the Cloud
- •20.4 Monetization Models in the Cloud
- •20.5 Charging in the Cloud
- •20.5.1 Existing Models of Charging
- •20.5.1.1 On-Demand IaaS Instances
- •20.5.1.2 Reserved IaaS Instances
- •20.5.1.3 PaaS Charging
- •20.5.1.4 Cloud Vendor Pricing Model
- •20.5.1.5 Interprovider Charging
- •20.6 Taxation in the Cloud
- •References
- •21.1 Introduction
- •21.2 Background
- •21.3 Experiment
- •21.3.1 Target Application: Value at Risk
- •21.3.2 Target Systems
- •21.3.2.1 Condor
- •21.3.2.2 Amazon EC2
- •21.3.2.3 Eucalyptus
- •21.3.3 Results
- •21.3.4 Job Completion
- •21.3.5 Cost
- •21.4 Conclusions and Future Work
- •References
- •Index
42 |
B.P. Rimal et al. |
Sun’s open storage provides a unique business model, which provides snapshot, replication, and compression without additional cost for data services. Hybrid cloud architecture is very important. One of the nice mechanisms of it is the open storage model that is provided by Sun Cloud, which is a new and unique business model as well.
SFDC introduces the Force.com metadata-driven, multitenant, internet application platform. In multitenant architecture, a single instance of the hosted application is capable of servicing all customers (tenants). Not all clouds are using virtualization. Clouds like GAE and SFDC use completely different technologies to create multitenancy. From the developer point of view, multitenancy is not the main event.
2.5.3 Open Source Based Cloud Computing Services
The role of open source cloud computing is to build mechanisms around digital identity management [14], and outline technological building blocks that are needed for controllable trust and identity verification. Nimbus supports the OASIS WSRF standard [32] that defines a framework and uses web services to model and access stateful resources. Enomaly cloud is focusing on the issue of interoperability, which is essential for enterprise cloud system. Most of the open source clouds are providing IaaS.
2.6 Comments on Issues and Opportunities
There are some issues related to mechanisms such as security, privacy, (erosion of) data integrity, load balancing, interoperability, and scalable storage. Cloud computing services often provide common business applications online that are accessed from a web browser, while the software and data are stored on the servers. One of the issues is an integration of data and application across clouds. This involves leveraging technology such as EAI (enterprise application integration), EII (enterprise information integration or federated database), and ESB (enterprise service bus). The market prognosis suggests raising the subscription fees as cloud vendors provide higher performance, scalability, availability, better support, and security. Transmitting huge volumes of multimedia data across clouds will continue to be a challenge, and needs further research. Discovery and composition of the services between multiple clouds is also a promising arena for enterprise cloud. Clouds have a different paradigm for resource utilization, so they need a different paradigm for managing these resources. Each previous revolution in computing also revolutionized how resources were managed. Collaborating amongst different technologies, businesses, and people in cloud computing will be an issue that will enable the enterprise to play a role as well. Quality assurance and information security are always challenging. Researchers should leverage identity and security management for business units. Furthermore, there are opportunities for the provision of a new range of privacy services. As the user requirement changes, functionality and
2 A Taxonomy, Survey, and Issues of Cloud Computing Ecosystems |
43 |
privacy requirements may change, and so privacy requirements need to be reassessed at regular intervals [30]. Policy-based dynamic privacy design patterns may be a better technique for cloud computing. Cloud computing brings some novel attacks that have not figured in much of the security discussion to date. We need more research into this. Cloud computing systems for High-Performance Computing (HPC) are also a promising area for future provision. Cloud is not yet mature enough for HPC [31]. However, cloud computing helps save enterprise 30–60% of their technology expenditure, but owing to lack of agreement on common standards, many enterprises are losing opportunities. It is not so easy for cloud computing to achieve its aim of being a universally accessible application that is based on open standards. Amazon AWS Import/Export supports importing and exporting data into and out of Amazon S3 buckets in the USA, but still leaves complications in migration of data between clouds. A major challenge of moving applications to the cloud is the need to master multiple programming languages and operating environments [27]. Special attention is needed for government agencies to integrate their data from traditional to PaaS, a need to learn some new programming models residing in the cloud. Interoperability is another important issue for cloud. There is a need for data access interoperability, which is a unique programming interface to access diverse databases (such as JDBS, ODBC, Ado.NET). There are lots of standardization issues; in the race to standardization, many organizations and forums are working, but need to leverage the collaboration and discussions between them. Cloud Computing Interoperability Forum (CCIF) [16] was formed to define an organization that would enable interoperable enterprise class cloud computing platforms through application integration and stakeholder cooperation. Similarly, Microsoft’s approach to interoperability principles [28] is a good starting point. Other organizations such as Open Cloud Consortium (OCC) [36], Open Grid Forum (OGF) [37], and Distributed Management Task Force (DMTF) [38] are also working on interoperability issues and open formats. Armbrust et al. [15] also identified many issues for future research. There are some complications with current programming frameworks and programming languages for cloud computing such as Google AppEngine with its SQL-like syntax called “GQL.” Select statements in GQL can be performed on one table only. GQL does not support a join statement. The cloud developers will need more flexible query-oriented and API-oriented programming in future. Automated diagnosis is one of the problems in Hadoop. MapReduce is better for limited tasks like text searching or data mining, the things Google does on an epic scale. For tasks that require relational database capabilities at web scale, database sharing has become a favorite practice. The main problem of why several users do not use cloud computing yet is the lack of trust in the cloud itself (services, providers, etc.) and this lack is based on several issues (no acknowledgement of the policies applied for confidentiality of the user’s information, privileges of the users in charge of the data, level of satisfaction in regard to compliance with the contract specifications, if the provider permits audits, technical support offered). The complexity will be there for developers to apply the disciplines of development across multiple platform technologies and computational models. The alignment of user needs with business strategy is also a challenging job for CIOs.
44 |
B.P. Rimal et al. |
2.7 Conclusions
Cloud computing is a promising paradigm for delivering IT services as computing utilities. Clouds are designed to provide services to external users; providers need to be compensated for sharing their resources and capabilities. There are significant challenges and opportunities behind the ecosystem of cloud computing such as resource management, reliability, fault tolerance, security, SLA, utility model, and performance issues. There are many taxonomies, but they are vendor-concern oriented. The proposed taxonomy focused more on engineering approaches such as functional as well as structured aspects of cloud computing systems. We provided a consistent set of guidelines for clarity, and reusability, which is employed to classify a wide range of cloud computing systems. The value of the offered taxonomy lies in that it captures a given system’s scope, scalability, generality, reusability, manageability, and flexibility. This chapter presented a different way of representing a taxonomy to classical approaches. This might be a new way to think about the components of taxonomy as layered services that can give a wide range of spectrum for flexibility and reusability. This taxonomy has been applied to the different cloud systems to find out the technical strengths and weaknesses. A survey of different cloud systems has been presented, and captures the different aspects of the taxonomy that provide an idea about functional and architectural view of the systems that they adopted. We concluded the chapter with a discussion of the considered systems, as well as directions for future research. It is hoped that this can provide stimulus to the researcher and ideas to the developer with respect to current cloud systems, hype, and challenges.
Acknowledgments This research was supported by the MKE (Ministry of Knowledge and Economy), Korea, under the ITRC (Information Technology Research Center) support program supervised by the NIPA (National IT Industry PromotionAgency) (NIPA-2009-C1090-0902-0026), and research program on Kookmin University.
References
1.Dean J, Ghemawat S (January 2008) MapReduce: simplified data processing on large clusters. Commun ACM 51(1):107–113
2.Sun Microsystems (2009). Virtualization for dummies
3.Software and Information Industry Association (2001, February). Software as a service: strategic backgrounder
4.Choudhary V (2009) Software as a service: implications for investment in software development. Proceedings of the 40th Hawaii international conference on system sciences
5.Kolakowski N (2009) Microsoft’s cloud azure service suffers outage. Retrieved from, http:// www.eweekeurope.co.uk/news/microsoft-s-cloud-azure-service-suffers-outage-396
6.Cruz A (2009) Gmail site reliability manager. Update in Gmail. Retrieved from, http://googleblog. blogspot.com/2009/02/update-on-gmail.html
7.Mayer M (2009) Search Products andUser Experience: This site may harm your computer on every search results. Retrieved from, http://googleblog.blogspot.com/2009/01/this-site-may- harm-your-computer-on.html
2 A Taxonomy, Survey, and Issues of Cloud Computing Ecosystems |
45 |
8.Jackson T (2008) Gmail product manager: we feel your pain, and we’re sorry. Retrieved from, http://gmailblog.blogspot.com/2008/08/we-feel-your-pain-and-were-sorry.html
9.Pete, App Engine Team (2008) App engine outage today. Retrieved from, http://groups.
google.com/group/google-appengine/
10. Allen Stern (2008) Update from Amazon Regarding Friday’s S3 Downtime. Retrieved from, http://www.centernetworks.com/amazon-s3-downtime-update
11. AWS Service Health Dashboard (2008, July 20) Amazon S3 availability event. Retrieved from, http: //status.aws.amazon.com/s3-20080720.html
12. Tubanos A (2008) FlexiScale suffers 18-hour outage. Retrieved from, http://www.thewhir. com/
13. Amazon Web Services (AWS) (2008, Sept) Amazon web services: overview of security processes
14. Cavoukian A (2008, May 28) Privacy in the clouds: privacy and digital identity – implications for the Internet. Information and privacy commissioner of Ontario
15. Armbrust M et al (2009, February 10) Above the clouds: a berkeley view of cloud computing. EECS department, University of California, Berkeley, Technical Report No. UCB/EECS- 2009-28
16. The Cloud Computing Interoperability Forum (CCIF) (2009) http://www.cloudforum.org/ 17. Gathering Clouds of XaaS! (2008) Retrieved from, http://www.ibm.com/
18. http://www.roughtype.com (2008)
19. Apache Hadoop project (2009) Available from http://hadoop.apache.org/
20. Amazon Elastic Cloud Computing (EC2) (2009) Available from http://aws.amazon.com/ec2/ 21. Crandell M (2008) Defogging cloud computing: a taxonomy. Available from http://gigaom.
com/2008/06/16/defogging-cloud-computing-a-taxonomy/
22. Laird P (2009) Different strokes for different folks: a taxonomy of cloud offerings. Enterprise cloud submit, INTEROP
23. Cloud Computing Use Case Discussion Group (2009, August) Cloud computing use case. White Paper version 1.0. 5
24. Ried S (2009) Yet another cloud – how many clouds do we need? Retrieved from Forrester Research, http://www.forrester.com/
25. Gammage B, Shiffler III G (2007, August 8) Report highlight for dataquest insight: PC virtualization forecast scenarios. Gartner
26. Dayley A et al (2009, Jan 5) Dataquest insight: virtualization market size driven by cost reduction, resource utilization and management advantages. Gartner
27. Hayes, B (2008, July) Cloud computing. Commun ACM 51(7)
28. Microsoft’s approach to interoperability (2009) Retrieved from, http://www.microsoft.com/ interop/principles/default.mspx. Accessed 25 Sept 2009
29. Gottfrid D (2009) Self-service, prorated super computing fun! Retrieved from http://open. blogs.nytimes.com/
30. Pearson S (2009) Taking account of privacy when designing cloud computing services. Proceedings of the 2009 ICSE workshop on software engineering challenges of cloud computing, IEEE Comp Soc, pp 44–52
31. Napper J, Bientinesi P (2009) Can cloud computing reach the TOP500? Proceeding of the combined workshops on unconventional high performance computing workshop plus memory access workshop, ACM, pp 17–20
32. OASIS (Organization for the Advancement of Structured Information Standards) (2009) http://www.oasis-open.org/
33. GoGrid’s prepaid cloud hosting plans (2009). http://www.gogrid.com/pricing/plans.php
34. Rainge E (2009, May) Worldwide telecom cloud billing 2009–2013 forecast. IDC Doc #217313
35. CFengine (2009) http://www.cfengine.org/
36. The Open Cloud Consortium (OCC) (2009) http://opencloudconsortium.org/
37. The Open Grid Forum (2009) http://www.ogf.org/
38. The Distributed management Task Force (DMTF) (2009) http://www.dmtf.org/about/
46 |
B.P. Rimal et al. |
39. Buco MJ et al (2004, Jan) Utility computing SLA management based upon business objectives. IBM Syst J 43(1):159–178
40. The Official Google Blog (2008, Nov) Sorting 1 PB with MapReduce. Retrieved from http:// googleblog.blogspot.com/
41. rPath (2009) http://www.rpath.com
42. Opscode (2009) http://www.opscode.com/
43. Sheehan M (2009) Message from GoGrid founders regarding denial of service attack. Retrieved from, GoGrid Official Blog, http://blog.gogrid.com/
44. Ristenpart T et al (2009) Hey, you, get off of my cloud: exploring information leakage in third-party compute clouds. Proceeding of ACM conference on computer and communications security
45. Linthicum DS, Morrison KS (2009) Value of SOA for cloud computing. Layer 7 technologies 46. Patterson D (2009) Recovery oriented computing. http://roc.cs.berkeley.edu
47. Ghemawat S, Gobioff H, Leung ST (2003) The google file system. Proceedings of the nine-teenth ACM symposium on operating systems principles, pp 29–43
48. Fielding RT (2000) Architectural styles and the design of network-based software architectures. Dissertation of doctor of philosophy, University of California, Irvine
49. RSA (2009, March) The role of security in trustworthy cloud computing. Continental Automated Building Association (CABA), Information Series, IS 2009-39
50. Thusoo A (2009, June 11) Hive-A petabyte scale data warehouse using hadoop. Retrieved from Facebook Engineering page, http://www.facebook.com
51. Hadoop/Hive (2009) http://wiki.apache.org/hadoop/Hive
52. Palankar M et al (2008) Amazon S3 for science grids: a viable solution? Proceedings of the 2008 international workshop on data-aware distributed computing workshop (DADC), pp 55–64
53. Carriero N, Gelernter D (1989) Linda in the context. Commun ACM 32(4):444–458
54. Gray J et al (1996) The dangers of replication and solution. Proceedings of the 1996 ACM SIGMOD international conference on management of data, pp 173–182