- •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
324 |
K.W.S. Morrison |
18.5 Conclusion
Too often, technological trends focus on what is new and fail to learn the lessons of the past. In the cloud community today, there is a misperception that SOA largely failed and that cloud will be the approach that successfully drives down IT costs and increases agility in the enterprise. In truth, cloud advocates can – and should
– learn from the lessons of SOA. There is much to gain from recognizing cloud computing as an evolutionary step and a logical deployment model for services developed under the principles and guidance of SOA.
The adherents of SOA are careful to promote the discipline not as technology, but as an architectural approach. Technology may not be a perfect realization of the philosophical goals of SOA; however, it is a pragmatic lens through which one can explore the more practical aspects of the discipline, especially when applied to an emerging sector like cloud computing. This chapter was about such a technology.
This chapter proposed the use of SOA PEPs, a security technology with proven value in on-premise SOA, as a means to secure and manage application services residing in the cloud. We found that a number of new challenges arise from the changes in control and operating environment that is inherent to cloud computing. The approach shows promise, though there remain open areas for research, particularly around cloud-based policy repositories and provisioning of PEP instances. Nevertheless, a run time, cloud governance architecture, based on the existing virtualized PEP infrastructure, is a practical and pragmatic approach.
Acknowledgments This author acknowledges the many valuable discussions with Jay Thorne, Director of Development, Tactical Team at Layer 7 technologies.
References
1.Armburst M et al (2009) Above the clouds: a Berkeley view of cloud computing. Electrical Engineering and Computer Sciences University of California at Berkeley. Technical Report No. UCB/EECS-2009-28. 10 Feb 2009
2.Berners-Lee T, Fielding R, Masinter L (2005) RFC 3986 Uniform Resource Identifier (URI): Generic Syntax. IETF
3.Brodie S (2008) Barriers to cloud computing adoption. http://blog.skytap.com/2008/06/barri- ers-to-cloud-computing-adoption/. Accessed 20 June 2010
4.Brunette G et al (2009) Security guidance for critical areas of focus in cloud computing V2.1. Cloud Security Alliance
5.Cameron R, Herdy K, Ehsan A (2009) Parallel bit stream technology as a foundation for XML parsing performance. In: Proceedings of the international symposium on processing XML efficiently: overcoming limits on space, time, or bandwidth. Balisage Series on Markup Technologies, vol. 4 (2009), Montreal, Canada
6.Dierks T, Allen C (1999) The TLS Protocol version 1.0. RFC 2446
7.Fickes M (2005) Validating DOD. Government Security Magazine. http://govtsecurity.com/ mag/validating_dod/. Accessed 20 June 2010
8.Fielding R, Getty J, Mogul J, Frystyk H, Masinter L, Leach P, Berners-Lee T (1999) Hypertext transfer protocol – HTTP/1.1, IETF
18 Technologies for Enforcement and Distribution of Policy in Cloud Architectures |
325 |
9.Fielding RT (2000) Architectural styles and the design of network-based software architectures. Ph.D. thesis, University of California, Irvine
10. Frier A, Karlton P, Kocher P (1996) The SSL 3.0 Protocol, Netscape Communications Corp. 11. Hollis C (2009) Barriers to private cloud adoption. http://chucksblog.emc.com/chucks_
blog/2009/06/barriers-to-private-cloud-adoption.html/.Accessed 20 June 2010
12. Langley K (2008) Cloud computing: get your head in the clouds. http://www.productionscale. com/home/2008/4/24/cloud-computing-get-your-head-in-the-clouds.html/. Accessed 20 June 2010
13. Leventhal M, Lemoine M (2009). The XML chip at 6 years. In: Proceedings of the international symposium on processing XML efficiently: overcoming limits on space, time, or bandwidth. Balisage Series on Markup Technologies, vol. 4 (2009), Montreal, Canada
14. Linthicum D (2009) Cloud computing and SOA convergence in your enterprise: a step-by- step guide. Addison–Wesley, Reading, MA
15.Lingyu W et al (2007) A logic-based framework for attribute based access control. In: Proceedings of the 2004 ACM workshop on formal methods in security engineering, Washington DC, USA
16. Maler E et al (2003) Assertions and protocols for the OASIS security assertion markup language (SAML) V1.1. OASIS Standard, September 2003
17. McIntosh M et al (2009) Basic Security Profile V1.1 Web Service Interoperability Organization
18. Mell P et al (2009) NIST Definition of Cloud Computing. NIST Computer Security Division. http://csrc.nist.gov/groups/SNS/cloud-computing/. Accessed 20 June 2010
19. Monzillo R et al (2006) Web services security: SAML token profile 1.1. OASIS Standard Specification
20. Morrison KS (2009) Steer safely into the clouds: why you must have cloud governance before you move your apps. Layer 7 Technologies
21. Moses T (2005) eXtensible access control markup language (XACML) version 2.0. OASIS Standard
22. Nadalin A et al (2006) Web services security: username token profile 1.1. OASIS Standard Specification
23. Nadalin A et al (2006) Web services security: Kerberos token profile 1.1. OASIS Standard Specification
24. Ness G (2009) The 3 major technology barriers to cloud computing. http://seekingalpha.com/ instablog/275505-gregory-ness/3681-the-3-major-technology-barriers-to-cloud-computing/. Accessed 20 June 2010
25. Reese G (2009) Cloud tips: sending email from an EC2 instance. http://broadcast.oreilly. com/2009/01/sending-email-from-ec2.html/. Accessed 20 June 2010
26. Salz R, Achilles H, Maze D (2009) Hardware and software trade-offs in the IBM DataPower XML XG4 processor card. In: Proceedings of the international symposium on processing XML efficiently: overcoming limits on space, time, or bandwidth. Balisage Series on Markup Technologies, vol. 4 (2009), Montreal, Canada
27. Van Cleave D (2003) MITRE helps the air force implement PKI. The Mitre Digest May 2003 28. ZDnet Interviews (2009) Experts highlight barriers to cloud adoption. http://news.zdnet.co.uk/
internet/0,1000000097,39661584,00.htm/. Accessed 20 June 2010
29. Service-Oriented Architecture (2009) http://en.wikipedia.org/wiki/Service-oriented_architecture Role-based Access Control. http://en.wikipedia.org/wiki/Role-based_access_control. Accessed 20 June 2010
30. Yavatkar R et al (2000) A framework for policy-based admission control RFC2753 Internet engineering task force
Chapter 19
The PRISM On-demand Digital Media Cloud
Terry Harmer, Ron Perrott, and Rhys Lewis
Abstract Over the last 5 years, the digital media sector has undergone a radical change in its business model. An industry once focused on broadcasting to a fixed published schedule must now support an on-demand usage model across a wide range of fixed and network devices using a variety of content formats. This media revolution has brought significant changes to user viewing patterns and demanded significant changes in the broadcaster’s business model. In turn, this has resulted in significant changes to the content creation workflow and radical changes in the infrastructure that is used to support digital media creation, distribution, delivery and archive. For the last 7 years, the Belfast e-Science Centre (BeSC) has worked with the British Broadcasting Corporation (BBC) to research emerging networkcentric technology and their applications within the broadcasting sector. This work pioneered the use of grid technology within the broadcasting sector and evolved, over the last 4 years (the PeRvasive Infrastructure of Services for Media (PRISM) project), into piloting a cloud-based media infrastructure that supports traditional and network-centric access to BBC content. The PRISM media cloud has services and test users across the United Kingdom and brings together owned and on-demand resources to support its user content access services. The service cloud is deployed on demand using owned and on-demand resources, and operates as a dynamic market selecting services based on need and usage criteria. In this chapter, we describe the PRISM cloud and the market ideas that underpin its operation.
T. Harmer (*)
Belfast e-Science Centre, the Queen’s, University of Belfast, Belfast, UK. e-mail: t.harmer@besc.ac.uk
N. Antonopoulos and L. Gillam (eds.), Cloud Computing: Principles, |
327 |
Systems and Applications, Computer Communications and Networks,
DOI 10.1007/978-1-84996-241-4_19, © Springer-Verlag London Limited 2010
328 |
T. Harmer et al. |
19.1 Introduction and Background
Digital media has become a pervasive part of people’s lives. Once video was transmitted to the home and viewed on a television. The focus for the broadcaster was on creating programmes to be broadcast according to a well-defined broadcasting schedule; creating an attractive schedule was an important part of the broadcaster’s business model to ensure success. There were generally few television stations and each targeted a broad audience with peak adult viewing and targeted programmes for children. There has been a rapid expansion in the number of television channels, such as CBeebies children’s channel or the Science Fiction channel, which target increasingly narrower audiences.
In addition, it is now the norm for video to be available on-demand from a range of content providers such as established television broadcasters, offering for example new catch-up services such as the British Broadcasting Corporation’s (BBC’s) iPlayer [6], or newer content providers such as YouTube [14]. This on-demand content is available at home using set-top boxes from cable or satellite providers, and via broadband network connections directly to network enabled in-home devices. It is commonplace that media is downloaded on-demand to a networked device at home or on the move when required; or it might be downloaded to a device and stored for future use. New companies and a new economy have been established that sell and deliver content directly to a user for use on their networked device using the network as the sales and delivery platform, such as Apple’s iTunes Store or Amazon’s Download service.
This media revolution has led to significant changes in the way the industry operates and the resulting workflows. A traditional broadcaster, such as the BBC, must now support a range of user access mechanisms, or platforms, in their day-to- day operation. Their traditionally small number of (schedule-driven) linear broadcasting channels has increased rapidly, from two channels 5 years ago to seven channels today, and they sit alongside cable, satellite, online news services and content on-demand services, and support conventional and high-resolution material. Each of these platforms requires content and metadata management, and they often have different content control access rights. For example, online content from the BBC’s iPlayer is available for 7 days after transmission and only within the UK. A broadcasting infrastructure must manage these platforms efficiently and costeffectively in the cost-sensitive media domain.
What makes digital media an interesting domain to work in is that it is a golden example that combines large-scale data requirements, millisecond-based quality of service (QoS) requirements and high security needs because (to the broadcaster) digital content is its lifeblood. Thus, for example, digital media combines data needs that are currently larger (and rising faster) than that projected for the Large Hadron Collider [1] and must support many millions of users all with high degree of reliability. For any new technology, the digital media domain is a demanding one.
The Belfast e-Science Centre has been working with the BBC for 7 years, researching the use of emerging technology within the broadcasting domain. Initially, BeSC and the BBC pioneered the use of grid technology [2] within the broadcasting
