carrier grade requirements for cloud computing: a scope alliance perspective 5.17.2011
Post on 15-Jan-2015
Embed Size (px)
DESCRIPTIONThe 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.
- 1. Telecom Cloud Computing SCOPE Alliance PerspectiveAndrs VajdaWhitepaper Editor, EricssonOpenSAF Conference, May 17th, 2011
2. About Scope Alliance Industry alliance committed toaccelerating the deployment ofcarrier grade base platforms forservice providers Founded in 2006 by leadingnetwork equipment manufacturers Close co-operation with PICMG,SAF, Linux Foundation www.scope-alliance.org2 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 ScopeAlliances 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. 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 Allianceagenda The way forward4 5. Cloud Computing andNetwork Equipment ProvidersBusiness AgilityMeet customer requirementsTelecom vendorsEfficiency of Service deliveryEfficiency of IT INFRASTRUCTURE5 6. Cloud Computing and Operatorsnew business opportunityCAPEX/OPEX reductionOperatorFlexibilityImproved Power efficiency6 7. Telecom Grade Cloud Infrastructure CLOUD Infrastructure Suitable for the deployment ofApplications with stringent Availability, Reliability,QoS, Security requirements telecom grade, real-EnterpriseCloudstime applications etcApplicationProviders&Consumers(Private) ContentStoreAppStore but also guiding ContentStore (ContentAggregation)SecureConnectivityAppStore AppAggregation SecureConnectivity (ContentAggregation)AppAggregation APIServiceOpenprinciple on where IntroductionCapabilitiesNEPs and operators Capabilities Capabilities/SLA Componentscan differentiatethemselves TelecomCloud NetworkResourcePool Connectivity Storage ComputingStorageResourcePoolComputingResourcePool7 8. Four Differentiating Factors Concentration is unrealistic for clouds intelecom networks Locality must be embraced bytelecom clouds transport represents bulk of the cost traffic is set to increase in telecom networks Telecom services have availability, real- SLA Management is key intime, QoS Service Level Agreementstelecom clouds(SLAs) to fulfill Customer data handling (often subject toDaTA Security, trust, iDENTITY,legal requirements), strict identity and trust TRACEABILITY in telecom cloudsmanagement, traceability requirements Interoperability is a key ingredient ofSupport for Inter-Cloudoperator offerings Operations of telecom clouds8 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. Data Centric ComputingFrom a cost perspective, everything is pretty much freecompared to the price of moving bytes around Cost of data transfer is still not optimized Its exacerbated by latency and throughput requirementsspecific to telecom / real-time communication applications Focus shall be on prioritizing networking versus computation10 11. SLA Management (1) Architecture of data-centers shall not be exposed but applications must have standard mechanismsat hand to express their SLA constraints measure the fulfillment of these Standardize on a specification level, differentiate onrealization Improve portability across clouds Support applications with strict requirements11 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. 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. Networking Virtualization exacerbates the scale of networking Number of virtual switches, MACs etc Theres a need to rethink networking in the context oflarge scale, virtualized, distributed data centers Promising approach: Open Networking Foundation OpenFlow based programmable switches Separation of simple packet switching mechanisms andcontrol functions Opportunity for a new way of coupling cloud computing andthe network fabric14 15. Inter-cloud Learn from successful examples: re-use theexperience from Internet for inter-operability ofclouds Need to establish a common set of Inter-CloudProtocols for VM and storage interoperability andmigration We believe OVF is a good foundation to build on forenhanced inter-operability15 16. Security (1) Theres no shortage of security related standards but we lack bundling and profiling of these for the cloudcomputing 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. Security (2) Need for overall security schema that defines security needsand 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 securitycritical industries Telecom Companies have the right trackrecord for achieving this17 18. Conclusions Cloud computing has Unresolved issues related to Networking, security, interoperability, soft real-time Characteristics Support for SLA Management, integrated cloud networking, Securityand cloud interoperability are key from telecom perspectiveTheres a need to address these issues through standardsthat can gain Wide acceptance18 19. Thank YOU! Andrs Vajda Andras.firstname.lastname@example.org Blog: www.a-vajda.eu/blog19