This document will be open for review till October 26. Please leave your comment inline. Thanks!
Content:
→ 1. Introduction – why telecom industry needs Cloud Native PaaS
→ 2. PaaS Condition in Network Cloud
→ 3. XGVela Overview
→ 3.1 XGVela High-Level Architecture
→ 3.2 XGVela Project Scope
→ 4. XGVela Technical Insight
→ 4.1 Technical Architecture
→ 4.2 XGVela PaaS Functional Requirements
→ 4.2.1 PaaS Management
→ 4.2.2 General PaaS Requirements
→ 4.2.2.1 General Requirements on General PaaS
→ 4.2.2.2 Functional Requirements on General PaaS
→ 4.2.3 Telco PaaS Requirements
→ 4.2.3.1 General Requirements on Telco PaaS
→ 4.2.3.2 Possible Functional Solution for Telco PaaS
→ 4.2.3.3 Telco PaaS Solution contributed by Mavenir MTCIL
→ 4.2.3.4 Telco PaaS Solution Proposed by Intel
→ 4.2.4 XGVela PaaS Workflow
→ 5. HA (to be added)
1. Introduction – why telecom industry needs Cloud Native PaaS
...
Figure 4-7 shows the basic working principle of NMaaS. NMaaS pod receives a vNIC request from orchestration/management systems or command line through standard NMaaS NBI. NMaaS will convert vNIC request into contents that can be understand by CaaS layer, including vNIC type, amount, configutation, etc. And the converted information will be sent to Multus to setup required underlaying driver/software. Then, NMaaS will trigger K8S create new vNIC for target Pod, and update the traffic and vNIC configuration in Pod.
4.2.4 XGVela PaaS Workflow
After summarizing the technical architecture and functional requirements, XGVela related workflows will be covered in this Chapter. These workflows are applicable to all PaaS platforms, which includes XGVela. In this Chapter, we only cover the simple and general workflows that have no telecom features, while the interaction with NFVO, VNFM and other telecom systems will be considered in future release.
...
The O&M interface, data model, data generation, etc. should be pre-developed based on PaaS Management requirements during design and development stage of PaaS Service.