1 / 16

Report from the Cloud Services Forum

Report from the Cloud Services Forum. Andrew White , CSF Chair Nokia Siemens Networks October 17, 2011. Outline. CSF Background CSF Principles CDN-I Release 1 completed CDN-I Release 2 in progress Inter-carrier t elepresence launch Cloud L ifecycle Checklist

rue
Download Presentation

Report from the Cloud Services Forum

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Report from the Cloud Services Forum Andrew White, CSF Chair Nokia Siemens Networks October 17, 2011

  2. Outline • CSF Background • CSF Principles • CDN-I Release 1 completed • CDN-I Release 2 in progress • Inter-carrier telepresence launch • Cloud Lifecycle Checklist • Status of other priority initiatives • CSF end-to-end process perspective

  3. Background • CSF launched mid-February 2011. • The committee includes the concepts of the previous SON Forum with a broader scope. • Initial set of deliverables identified during inaugural meeting focused on inter-provider telepresence, content distribution and VPNs. • Subsequently, it was agreed that the primary focus would be to complete Content Delivery Network Interconnection (CDN-I) work in a short time interval. • Additional information can be found at the following link • http://www.atis.org/Cloud/index.asp

  4. CSF Principles User End Users End users interact with the business application oblivious of the component parts. Subscriber Service Applications Service Interaction Management is used to blend service enablers into a business application. Service Interaction Reuse Service Enablers Service Resource Applications Storage and Computing Networks App App App The Service Enablers exposes resources (applications, data, and connectivity) through a defined, reusable interface. Data Data Data Access & Transport

  5. Service Creation in the Cloud Service Enabler Characterization provides key non-functional data to populate Service Catalog Service Catalog Core Competency Service Interaction Management Partner Enablers Service enablers come from many places and are combined into finished services through a common framework.

  6. CDN-I Release 1 • CDN Interconnection Use Case Specification and High Level Requirements, (ATIS-0200003), published June 2011 • Develops use cases and requirements for CDN-I structured by phase in the interconnect lifecycle • Provides focused interconnection model that addresses • Software Download • Cached Delivery • Peer to Peer Interconnection

  7. Inter-connected CDN Delivery Model CDN Provider-2 Network & CDN CDN Provider-1 Network & CDN Content Delivery Node. Content Delivery Node. Routing, Back-office Routing, Back-office Network Peering Storage, Origin Storage, Origin Content Delivery Node. Content Delivery Node. Note: only data path is shown for clarity. Request & back-office path not shown. User Content Data Path Node Cache Fill Data Path Cache Based Delivery

  8. Use Case Areas Content Types and characteristics Off-peak – Software download Peak & on-demand – Web, LFD, VOD, etc Real-time - Events Delivery types & protocols Unicast, Multicast: different protocols Customer Life-cycle Pre-sale Post-sale Content Delivery End Contract Postmortem Additional & on-demand capabilities, operational management, Performance Capabilities, reservation, trial Root cause, audit Purge, etc. On-boarding, Testing Peer-Peer Interconnection Life-cycle Active/interconnected Environment Termination On Boarding Purge, settlements

  9. CDN-I Interface Domains Bi-Lateral Agreement Between Two Carrier CDNs. Assume that each carrier peers with another carrier at the CDN Level Operations & Customer Care Operations & Customer Care SLA/outages/ticketing, Special customer requests Back-Office Back-Office Provisioning, Logs, settlement Routing Routing Traffic distribution, load management, AMT Relay addresses Delivery Delivery Features, Capacity reservation, Origin access, multicast sources/groups Network Interconnection Network Interconnection Access, Security CDN Provider-2 CDN Provider-1

  10. CDN-I Release 2 • CDNI-I Release 2, targeted for completion by the end of 2011, will develop use cases and requirements for: • Multicast-based content delivery with applicable content types (e.g., live streaming) • Federated CDN-Interconnect • Cloud services charging (generic function driven by CDN Use Cases) • Other Release 2 objectives: • Group comprehensive requirements per applicable interconnection domain • Develop reference architecture for CDN-I NNI with other impacted ATIS Committees • Evaluate protocols including the output of the IETF CDNi Working Group (when available) to support use cases and requirements

  11. CDN Federation Model Interface Domains Federation exchange: There is a trusted 3rd party for facilitating federation Third Party Functions Operations & Customer Care Operations & Customer Care SLA/outages/ticketing, special customer requests Back-Office Back-Office Provisioning, logs, settlement 3rd Party Traffic distribution, load management, AMT relay addresses Routing Routing Delivery Delivery Features, capacity reservation, multicast sources/groups Origin access Network Interconnection Network Interconnection Access, Security Carrier-1 Carrier-2

  12. Inter-Carrier Telepresence • Objective is to develop, by year-end, an ATIS specification describing the high-level, end-to-end message flow diagrams for access-agnostic, inter-provider telepresence • Both private and public cloud domains will be considered • End user may access these cloud domains by using wired or wireless devices • The focus is to use functional service enablers as defined by ATIS CSF • Abstracted messages between the functional elements will be used rather than specific network elements and protocol messages • This output is expected to be the basis of subsequent ATIS CSF service architecture specifications

  13. Cloud Lifecycle Checklist The checklist is being developed to facilitate the following six functions from a cloud provider: • Assessmentand acceptance(i.e. build) of services onto the cloud platform/infrastructure • Ongoing audit(i.e. capture) of services on the cloud platform/infrastructure • Augmentation, abridging, and annulmentof services within the cloud platform/infrastructure

  14. Virtual desktop infrastructure (VDI) • An initial baseline document was developed mid-year to describe the virtual desktop client requirements for CSF-defined services, to include both enterprise and consumer domains. • The scope of the initiative was recently revised to limit context to enterprise services (and related network architecture) only.

  15. Virtual Private Network (VPN)-Oriented Data Center Services (VDCS) • Initial baseline document created in support of VDCS - a generic framework to provide virtual private cloud services. • Objective is to develop use case specification for using the VPN network as the common control point for end–to-end services on interconnected data center resources.

  16. In Summary • CSF continues on a fast track as it focuses on the next priorities. • CDN-I • Telepresence • Cloud Lifecycle Checklist • Virtual desktop infrastructure (VDI) • Virtual Private Network (VPN)-Oriented Data Center Services (VDCS) • Important synergies exist with the work on • Framework Development, • Service Enabler Definition, and • Vertical Service Creation. • The Cloud Services Forum looks forward to continued interaction with ITU-T SG13 on these important topics.

More Related