1 / 23

NaaS and IaaS Functional Requirements

ITU Workshop on “Cloud Computing Standards – Today and the Future” (Geneva, Switzerland 14 November 2014). NaaS and IaaS Functional Requirements. Ying Cheng China Unicom chengying10@chinaunicom.cn. Nan Chen China Te lecom chenn@gsta.com. Contents.

rrobles
Download Presentation

NaaS and IaaS Functional Requirements

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. ITU Workshop on “Cloud Computing Standards – Today and the Future” (Geneva, Switzerland 14 November 2014) NaaS and IaaS Functional Requirements Ying Cheng China Unicom chengying10@chinaunicom.cn Nan Chen China Telecom chenn@gsta.com

  2. Contents • Part I: Functional Requirements of Network as a Service • Based on Recommendation ITU-T Y.3512 (Cloud computing - Functional requirements of Network as a Service) • Part II: Functional Requirements of Infrastructure as a Service • Based on Recommendation ITU-T Y.3513 (Cloud computing - Functional requirements of Infrastructure as a Service)

  3. Contents • Part I: Functional Requirements of Network as a Service • Based on Recommendation ITU-T Y.3512 (Cloud computing - Functional requirements of Network as a Service)

  4. Summary of Y.3512 • Scope • High level concept of NaaS; • Functional requirements of NaaS application, NaaS platform and NaaS connectivity; • Typical NaaS use cases of NaaS application, NaaS platform and NaaS connectivity. • Statistics • 61 contributions from 8 sector members: China Unicom, Orange Polska SA, Orange, ETRI, ZTE, Microsoft, Huawei, Alcatel-Lucent Shanghai Bell • 8 meetings: 7 physical meetings and 1 e-meeting • 13 use cases: 3 in general and 10 in detail • 26 functional reqts: 4 for NaaS application, 5 for NaaS platform, and 17 for NaaS connectivity • Editors • Ying Cheng (China Unicom) and Emil Kowalczyk (Orange Polska SA)

  5. NaaS concept • Network as a Service (NaaS) [Y.3500]:cloud service category in which the capability provided to the cloud service customer is transport connectivity and related network capabilities • NaaS services are divided into network application service, network platform service, and network connectivity service. In particular, NaaS connectivity service is an “infrastructure capabilities type” service (limited to networking resources). NOTE – NaaS can provide any of the three cloud capabilities types.

  6. NaaS concept (2) NaaS Application: application capabilities type of service where NaaS CSC can use network applications provided by CSP. Examples of NaaS applications include virtual router, virtual content delivery network (vCDN), virtualised evolved packet core (vEPC) and virtual firewall (vFW). NaaS Connectivity: infrastructure capabilities type of service where NaaS CSC can provision and use networking connectivity resources provided by NaaS CSP. This includes for example flexible and extended virtual private network (VPN), bandwidth on demand (BoD), etc. In this category, CSP offers network connections between two or more endpoints, which may include additional network functionalities. NaaS Platform: platform capabilities type of service where NaaS CSC can use the network platform provided by NaaS CSP. The NaaS platform offers one or more software execution environments and one or more programming languages to deploy, manage and run customer-created or customer-acquired network applications. High level concept of NaaS using the layering framework defined in [ITU-T Y.3502]

  7. Development methodology of NaaS related WIs Use Cases Functional Requirements Functional Architecture Y.3512 Y.CCNaaS-arch • Considering the standardization methodology and conventional study sequence, the abstractions of functional entities and their mutual interactions are based on the functional requirements and the corresponding use cases analysis, which form a standardization body together. Therefore, it is required to progress NaaS functional requirements and architecture according to the following steps and priorities. • Additionally, it is needed to align with the high level requirements of NaaS described in the latest edition of Y.3501 (Cloud computing framework and high-level requirements), whose most recent edition is ITU-T Y.3501 (2013). Source: Appendix I of Y.3512

  8. Milestones of NaaS related WIs

  9. Detailed use cases and functional reqts of NaaS application

  10. Detailed use cases and functional reqts of NaaS platform

  11. Detailed use cases and functional reqts of NaaS connectivity (1)

  12. Detailed use cases and functional reqts of NaaS connectivity (2)

  13. Contents • Part II: Functional Requirements of Infrastructure as a Service • Based on Recommendation ITU-T Y.3513 (Cloud computing - Functional requirements of Infrastructure as a Service)

  14. Y.CCIaaS in Summary • Scope of Y.CCIaaS • General description of IaaS • Functional requirements of IaaS • Typical IaaS use cases • 41 related contributions from 7 sector members in 9 meetings • Editors • CHEN Nan (China Telecom) • Peter Tomsu (Cisco)

  15. Milestones of Y.3513

  16. The definition of IaaS • Infrastructure as a Service [ITU-T Y.3500] • cloud service category in which the cloud capabilities type provided to the cloud service customer is an infrastructure capabilities type NOTE – The cloud service customer does not manage or control the underlying physical and virtual resources, but does have control over operating systems, storage, and deployed applications that use the physical and virtual resources. The cloud service customer may also have limited ability to control certain networking components (e.g. host firewalls).

  17. High level concept of IaaS

  18. IaaS service functions computing service functionsallow CSC to provision and use processing resources. CSC can perform operations relevant to processing resources including machine (physical or virtual machine) lifecycle operations and functions such as VM migration, backup, snapshot, clone and reservation. storage service functionsallow CSC to use storage resources. CSC can perform operations relevant to storage resources including lifecycle operations and functions such as snapshot, backup, I/O performance, load balance and reservation. network service functionsallow CSC to use networking resources. CSC can integrate infrastructure resources using network relevant functions such as IP address, network isolation (e.g. VLAN), virtual networking (e.g. virtual switch), load balance and firewall.

  19. Computing service functions • migration • scaling • snapshot • clone • backup • time synchronization • reservation • image • template • Physical machine Computing Service • Virtual machine

  20. Storage service functions Storagemigration Storageresourcereservation Storage snapshot Storageservice I/Operformance Storagebackup

  21. Network service functions • Network policy migration • Network QoS • IP address • Network Isolation • Virtual networking • Network configuration • Load balance • Firewall • Gateway Network Service

  22. The relationship between IaaS and NaaS • Regarding the network connectivity, one important difference between IaaS and NaaS is that IaaS is a cloud service category that is offered in only one flavour of cloud capability type, and that is infrastructure capabilities type [ITU-T Y.3500]. However, NaaS is a cloud service category that can be offered in all three cloud capabilities types.

  23. Thanks for your attention！

More Related