Carrier Grade Requirements for Cloud Computing: A SCOPE Alliance Perspective 5.17.2011

4,740 views

Published on

The mission of Scope Alliance is to advance the objective of a vibrant and diverse ecosystem of COTS (commercial off-the-shelf): carrier-grade platform components utilizing open standards. Cloud Computing has the common goal of reducing the platform costs while continuing the direction of increased openness of the architecture.

Cloud providers have succeeded in pushing the cost of computation and storage down by concentration, virtualization and economies of scale; by doing so, they had to compromise on some fundamental issues, such as networking, security and real-time characteristics. In this session, we will define the differentiating factors that can enable the usability of cloud computing for telecom and real-time services. In this context, we will include the role and importance of inter-cloud architectures as well as the usage of private, public and hybrid architectures for real-time and telecom services. These aspects form the technical foundation for standardization efforts in the area of cloud computing, as well as the work agenda for the SCOPE Alliance in its relationship with various standardization bodies.

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
4,740
On SlideShare
0
From Embeds
0
Number of Embeds
1,903
Actions
Shares
0
Downloads
121
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Carrier Grade Requirements for Cloud Computing: A SCOPE Alliance Perspective 5.17.2011

  1. 1. Telecom Cloud Computing SCOPE Alliance Perspective András Vajda Whitepaper Editor, EricssonOpenSAF Conference, May 17th, 2011
  2. 2. About Scope Alliance  Industry alliance committed to accelerating the deployment of carrier grade base platforms for service providers  Founded in 2006 by leading network equipment manufacturers  Close co-operation with PICMG, SAF, Linux Foundation www.scope-alliance.org2
  3. 3. Cloud Computing – a telecom perspective Based on a successful Scope Alliance workshop in May 2010 Whitepaper focus is on issues relevant for the telecom industry and Scope Alliance’s goals  Define and publicize the differentiating factors  Telecom perspective for standardization efforts  Define a common work agenda for the Scope Alliance  Available at  http://scope-alliance.org/sites/default/files/documents/CloudComputing_Scope_1.0.pdf Editorial team  Ericsson (coordinator)  Alcatel-Lucent  Huawei  NEC  Nokia Siemens Networks3
  4. 4. Outline  Cloud computing and the telecom industry  Telecom grade cloud computing infrastructure  Differentiating factors for telecom grade cloud infrastructure  Principles for telecom grade cloud infrastructure  Foundation for standardization efforts– Scope Alliance agenda  The way forward4
  5. 5. Cloud Computing andNetwork Equipment ProvidersBusiness AgilityMeet customer requirements Telecom vendorsEfficiency of Service deliveryEfficiency of IT INFRASTRUCTURE5
  6. 6. Cloud Computing and Operatorsnew business opportunityCAPEX/OPEX reduction OperatorFlexibilityImproved Power efficiency6
  7. 7. Telecom Grade Cloud Infrastructure CLOUD Infrastructure Suitable for the deployment of Applications with stringent Availability, Reliability, QoS, Security requirements telecom grade, real- Enterprise Clouds  time applications etc Application Providers & Consumers  (Private) Content Store App Store … but also guiding Content Store (Content Aggregation) Secure Connectivity App Store (App Aggregation) Secure Connectivity (Content Aggregation) (App Aggregation) API Service  Open  principle on where Introduction Capabilities NEPs and operators Capabilities  Capabilities/SLA  Components can differentiate themselves Telecom Cloud Network Resource Pool Connectivity Storage Computing Storage Resource Pool Computing Resource Pool7
  8. 8. Four Differentiating Factors Concentration is unrealistic for clouds in telecom networks Locality must be embraced by telecom clouds  transport represents bulk of the cost  traffic is set to increase in telecom networks Telecom services have availability, real- SLA Management is key in time, QoS Service Level Agreements telecom clouds (SLAs) to fulfill Customer data handling (often subject to DaTA Security, trust, iDENTITY, legal requirements), strict identity and trust TRACEABILITY in telecom clouds management, traceability requirements Interoperability is a key ingredient of Support for Inter-Cloud operator offerings Operations of telecom clouds8
  9. 9. Six Principles of Telecom Clouds1. Data-centric computing - place data where it is used2. Data-centric computing - place computation where the data is3. Networking, computing and storage managed as one integrated resource – including the last mile4. Make the SLA definition and enforcement framework the center-piece of telecom cloud infrastructure5. Enforce security: tamper-resistant computing environment, data security mechanisms, tamper-resistant networking6. Seamless VM and data inter-operability between clouds9
  10. 10. Data Centric Computing “From a cost perspective, everything is pretty much free compared to the price of moving bytes around” Cost of data transfer is still not optimized It’s exacerbated by latency and throughput requirements specific to telecom / real-time communication applications Focus shall be on prioritizing networking versus computation10
  11. 11. SLA Management (1) Architecture of data-centers shall not be exposed… … but applications must have standard mechanisms at hand to  express their SLA constraints  measure the fulfillment of these Standardize on a specification level, differentiate on realization Improve portability across clouds Support applications with strict requirements11
  12. 12. SLA Management (2) Standard SLA specification language  Physical and logical affinity attributes  Compute and storage relationships that define the dependencies between applications (compute) and data  Performance metrics  requirements in terms of network or storage bandwidth resources  Quality-of-service metrics  requirements in terms of end-to-end latency, jitter both for network and storage connectivity  Availability metrics  requirements in terms of availability of connectivity between compute resources and end-users or within individual data centers  High availability installations  will automatically protect applications with redundant compute and storage resources12
  13. 13. SLA Management (3)Standard SLA fulfillment monitoring metrics  End-to-end bandwidth allocation  Latency and jitter encountered by a particular application  spanning both compute and network resources  Computational load as seen by hypervisors  Storage load as seen by storage devices and/or dedicated storage networks  Faults in compute, storage or network infrastructure components13
  14. 14. Networking Virtualization exacerbates the scale of networking Number of virtual switches, MACs etc There’s a need to rethink networking in the context of large scale, virtualized, distributed data centers Promising approach: Open Networking Foundation  OpenFlow based programmable switches  Separation of simple packet switching mechanisms and control functions  Opportunity for a new way of coupling cloud computing and the network fabric14
  15. 15. Inter-cloud Learn from successful examples: re-use the experience from Internet for inter-operability of clouds Need to establish a common set of Inter-Cloud Protocols for VM and storage interoperability and migration We believe OVF is a good foundation to build on for enhanced inter-operability15
  16. 16. Security (1) There’s no shortage of security related standards … but we lack bundling and profiling of these for the cloud computing context  Secure data management  Data lifecycle  Enforcement and tracking of data placement  Data partitioning within the cloud and outside of it  Compliance with legal requirements, specific to the telecom sector  Integration of security SLAs with the rest of the SLA framework16
  17. 17. Security (2) Need for overall security schema that defines security needs and requirements at different layers  Network, hardware, hypervisor, VMs, OS, middleware Standards for secure management of cloud infrastructures Standards for auditing of cloud operations  E.g. based on ISO 27001 Security attestation framework – similar to other security critical industries Telecom Companies have the right track record for achieving this17
  18. 18. Conclusions Cloud computing has Unresolved issues related to Networking, security, interoperability, soft real-time Characteristics Support for SLA Management, integrated cloud networking, Security and cloud interoperability are key from telecom perspective There’s a need to address these issues through standards that can gain Wide acceptance18
  19. 19. Thank YOU! András Vajda Andras.vajda@ericsson.com Blog: www.a-vajda.eu/blog19

×